| iMatix home page|
| Xitami home page
| << | < | > | >>
Xitami was never meant to be the world success it is today. Heck, we released version 1.0 just to demonstrate how internet servers *should* be written. Unfortunately for our private lives, a screaming horde of people dragged poor little Xitami out of the door, into the bright light of day, and insisted that we beat it into the shape of a real web server.
Let's make it clear: the main motivating forces behind Xitami (at least as far as our team was concerned) were laziness and hubris. Larry Wall got this exactly right. Frankly, we were too lazy to install Apache, and arrogant enough to think we could do better than Microsoft on their own systems.
From the first release of Xitami, the majority of changes, improvements, and fixes were provoked by its users. Xitami consists of a small group of programmers surrounded by hundreds of vocal, and supportive users. It's a great mix.
Our dream was to show the world that large, slow, and complex software is a deception. Xitami does its job with a minimalistic grace, smoothly directing the traffic streaming through its arms. No waste, no haste. Where other servers are traffic lights, Xitami is a round-about.
We built Xitami from the ground-up using an approach that should delight any student of engineering, software or otherwise. First step - ask the question: 'what are the real problems a web server has to solve?'. Step two - answer these problems. The real problems are, as far as we could see, ease of use, performance, stability, and portability. Basically, we wanted something that would install in a minute, always run fast, never crash, and run on every machine on our rather mixed-up network. This is what we made, more or less. In some situations, Xitami does crash, but it's quite rare.
A perfectionist design like this can't succeed without some kind of discipline and formality. This is one of the basic debates in programming. Is programming a science or an art? Do you use a free-wheeling, organic approach, or an organised, formalised approach? This is like the debate about heredity against environment. You need both to succeed. Xitami was built using a tightly-defined method, but allowing any and all creativity on top of that.
To write a Xitami agent, like the LRWP agent that Robin Dunn wrote in 1997, you need to learn: the C programming language, the Libero tool, the SFL library, the SMT kernel, and something about the HTTP protocol. This is a fair challenge. However, when you've absorbed this knowledge, the program you write runs on Windows 95, Windows NT, OS/2, Linux, and just about every other modern machine out there. For a programmer, being able to write a truly portable program is akin to the promise of immortality. Certainly it drives thousands to learn languages like Java, putting-up with all the problems that young languages bring with them.
Xitami will run on every capable machine in existence for the next fifty years without significant difficulty at all.
A day will come when the use of C will look dated. For a long time we built tools using COBOL 74, a language that does not know about pointers, and dynamic allocation, or even lowercase letters. The tools we built were excellent, widely-used, and long-lasting. Linked-lists, recursive algorithms, virtual memory management, we did all of this in a language designed for writing accounting systems. This taught us that the choice of language is not as important as people often believe. But it can make your life easier or harder, and you can't produce better code than the compiler generates. Some COBOL compilers are attrociously bad. On the AS/400, the generated code for a statement like 'ADD 1 TO A' consists of about ten instructions: take A, convert to floating point, take 1, convert to floating point, add to A, round the result to N digits, convert from floating point, store back in A. The machine supports an instruction 'increment' which would do the job in one step.
Most operating systems are written in C, and on modern systems, the C compiler is the most stable, optimised, and standardised available. This is borne-out by our experience: we have found very few compiler errors despite running Xitami on a couple of dozen different C compilers.
If you look at the sources for Xitami, you'll see various references to something called 'Libero'. This simple but magical tool is our most elementary weapon in the battle to render complex problems simple. Libero is not dedicated to any single type of work - it's been used in many different domains. When it comes to writing an Internet server, however, it's hard to imagine a better start.
There is a handy trick that you can use to understand and describe certain kinds of system. Let's call this 'an event-driven approach'. Many problems (including many types of program) suddenly become much easier to understand and describe when you look at them in this way. It's just a trick, because of course the real problem is unchanged. But a good programmer, being lazy, will use any trick that makes life easier. In a classic program, the programmer says 'okay, we do this, then this, then that'. In an event-driven program, one says 'when this happens, do that. When that happens, do thus'. It's strange at first, but quickly makes sense. Libero takes this approach and turns it into actual code. Suddenly we have a way to describe complex systems and produce the code that makes them work. In the same breath.
By exceedingly good chance, servers, including web servers, fall smack bang into this category of problem. When you look at the Libero description of the Xitami web service, you see on a couple of pages the complete logic of a web server. This is stunningly simple compared to trying to read the Apache source code.
The main technical challenge behind any web server, however it's written, is performance. Writing a program that will answer one HTTP request is almost trivial. Writing a program that can answer several hundred in a few seconds is something else. Most existing web servers have tried to evolve from the first case to the second. Under Unix, they start dozens or hundreds of processes. Under Windows, they start dozens or hundreds of threads. Either way, each process or thread handles one single user request. The Windows threads approach is fast, but totally specific to one operating system. The Unix process approach is fast once it's started. But it takes ages to start and stop a server like this, and the web server inevitably takes over the entire system. There are 'portable' thread libraries, but frankly: writing real multi-threading code is like walking on eggshells. We're too lazy to learn to do this.
The basic problem with a web server is that you have to handle many short-lived connections. When the cost of creating and eventually killing a process or thread is significant compared to the cost of handling the request, the server is not efficient.
Building on Libero's event-driven approach, we built a solution to this problem, with the catchy name 'SMT'. SMT dispenses with all the stress of creating processes and threads by handling everything in one single process. We call this 'multi-threading', but that's marketing. In fact SMT enforces an event-driven model onto the programs, and simulates a kind of event-driven thread. It's like writing Quicksort algorithms in COBOL. You don't need recursion built-in to the language to implement a recursive algorithm. Bizarrely enough, simulated recursion is often faster than the real thing. The same thing goes for SMT's event-driven threads. An SMT thread needs none of the adminstrative baggage of a normal multi-threaded program - locks, semaphores, and so on. It just handles the events it gets in its queue, and sends out events to other threads. A thread always runs exclusively, with SMT switching to another thread only between the major steps of the Libero 'dialog'.
SMT seems to be a perfect approach for Internet servers of all kinds. If there are flaws in it, we've not seen them yet.
It's pretty pointless building the perfect web server if it only runs on one operating system. This is like writing haiku in sand on the beach. The point of software, like art, is to reach a public. Unfortunately, the public for software is a moving target. Operating systems last a few years, and non-portable software dies with them when they go. There are different tactics to portability. Microsoft try 'portability by exclusion'. If everyone runs Windows, portability is easier (ignoring that new version of Windows coming up fast behind you). Java and Posix define 'portability by decree'. Presumably in the hope that people like Microsoft will tamely go along with the idea. Many projects do 'portability by patching', which means patching the software each time it is ported, leading to masses of '#ifdefs' throughout the programs.
At iMatix, we chose 'portability by paranoia'. A library, the SFL, provides all the functions our programs need that are not 100% portable. A program that uses SFL correctly is fully portable. The approach works because we're not dependent on the goodwill of other people. If some operating system decides to implement sockets in some bizarre way, we just add support in SFL. Xitami's portability is the flying carpet that takes it into the future.
Of course, we cheated a couple of times. To run Xitami under Windows, we built a native Windows console program that lets a user manage the server. It's not portable, but it does turn Xitami into a neat little Windows program. Apart from that, the entire Xitami source code is fully portable.
The Xitami team itself consists of Pascal Antonnaux, Ewen McNeill, Jonathan Schultz, with Pieter Hintjens doing the co-ordination and production. The Xitami team has been working together since the first release of Xitami, in January 1997.
Thanks to the folk at iMatix for providing technical support, coffee, and most of the finance for this project. iMatix does not make a profit on Xitami, but it's become a kind of company mascot.
Providing the first buffer between ourselves and our users is the Xitami discussion list. This is run by Scott Drake, who took over in October 1997 when the original list, run by Martyn Drake (no relation), lost its home. We owe a great deal to Scott, and his company, isonline.com. Thanks also to Ewen McNeill for his clear and concise answers to many hundreds of questions on the list, and the many other people who have contributed information to the list.
We were lucky to find ourselves surrounded by a number of people, Xitami users with apparently infinite patience and tolerance for disasters, who adopted Xitami and regularly send us their comments and ideas. Some of these have built ISP businesses using Xitami, others use Xitami in their companies. Thanks to Ben Tremblay, Bruce Walter, Fabian Bess, Glenn Williams, Ignacio Bustamente, James Beasley, Jayson Minard, Jeff Wolkove, Jimi Joergensen, Josh Lydolph, Istvan Kovacs, Leif Svalgaard, Patrick Bedert, Paul Richards, Peter D'Hoye, Rob Judd, Thomas Grobicki, Wim Niemans, Dan, who's full name we never knew, and the many others who took time to send us their ideas, comments, and bug reports.
Thanks to Diego Antona, Wim Niemans, Robert White, and Taweewit Pensawat for providing Xitami mirror sites.
Thanks to DeXin and Chin Fang for providing an excellent home for Xitami on imatix.com, and a big "thanks" to Jayson Minard of OpenAvenue.com for giving a new home at OpenAvenue.com for xitami.com, finally allowing us to run xitami.com on a Xitami server.
Thanks to Mohammed Aziz and Rick Caccia of NetDynamics for including Xitami in their NetDynamics package in early 1997, proving that Xitami was up to scratch. As far as we know, Sun still includes Xitami in NetDynamics.
Thanks to Dr Dobb's Journal (and especially Eugene Eric Kim) for publishing our initial articles on Libero and Xitami.
Thanks to Robin Dunn for writing the LRWP agent, a great piece of work, and a great asset to Xitami, and to Scott Beasley for providing the mailto program. Thanks to Thomas Schroeter for supporting and managing xitami.de, the German Xitami site. Since day one, about 8% of all Xitami users are from Germany.
Thanks to the several thousand of you who have emailed and registered, telling us what you thought about Xitami, being liberal with your criticism and compliments alike.
Finally, thanks to the literally hundreds of thousands of people who use Xitami every day without sending us emails. We appreciate it more than you know!
| << | <
| > | >>
| Welcome To Xitami | Table Of Contents | Installing Xitami | Administration | Configuration | Using The Common Gateway Interface (CGI) | Server-Side Includes (SSI) | Using Filters | Server-Side XML Processing | Server-Side GSL Scripting | Image Maps | Virtual Hosts | The FTP Service | The Dynamic DNS Feature | Throttle Pipes | A Beginner's Guide | Writing Web Server Extension (WSX) Agents | Extending Xitami with External Peer Processes | FAQ | Getting Support | Credits | Release History | License Agreement
Copyright © 1996-2002 iMatix Corporation