Speeding Up A CABOOSE

Team. It has already been noted that the dynamic invocation used in CABOOSE for JEE might result in slower applications compared with servlets and JSPs/JSFs systems which have few if any reflective calls. If one is interested in spinning a CABOOSE which uses dynamic invocation and likely is the Bugatti Veyron of such systems, one should consider building in the fastest, compiled high-level language which he can find. This would likely be a C implementation.

Initially developed in the early 1970 at Bell Labs, C was the first highly "portable" language with compiler support on most, if not all, modern hardware platforms. C allows for dynamic invocation and has libraries for processing XML plus HTTP requests and responses. In benchmark test, C has performed nearly as well as assembly language code on average. This occurs because a C compiler can make certain optimizations which speed processing. Some of these include injecting in-line assembly language instructions.

In terms of the LAMP ports  for CABOOSE, this form of invocation can be achieved when the interpreter evaluates a line of code, since the lines of code in the program can be dynamic.  PERL, PHP, and Python are all interpreted languages which support this type of processing. The LAMP ports will likely be the "slowest" of the CABOOSE systems.

We do not have a C implementation in the current plans. It is not commonly used as a web scripting language and can seem somewhat cryptic for those who are not familiar with it. Also, seeing that C does not support objects the way that its offspring C++ does, using C would simply produce a controller application bundle (CAB). If one wants the object-orientation for the (OOSE) and the best speed, one should use C++.

With these notes about performance, it should be said that the CABOOSE for JEE should satisfy the normal case (95%) of development. This is also true of the CABOOSE for LAMP.

Hunt...Peck..Think..Have A Great DAy.