The Houston Server/Peer is a flexible protocol handler based upon JAVA's Reflection API and the Interpreter Pattern. It is a very powerful example of an extensible architecture. Its purpose is being a server-based launchpad for many systems which use command interpreters for processing protocol messages. Its original intent was removing the "molasses" from a hampered computing grid while supplying a novel functional paradigm in support of network-based computing. It was intended as a possible PhD dissertation or project for a graduate student if that wraskel Boonie ever earned a professorship. It uses the Hypertext Transport Protocol (HTTP) as a means of communicating with HTTP Clients and other Peers. It should be noted that the content on this page represents an Easter egg for this site, and the Houston functionality is not hidden in any JAVA archive for CABOOSE which has already been available on the web.
The Houston Server has an interesting history being inspired by three college acquaintances. One who loved Barbar as a child, one whose half-Anglo and half-African name translated as "flowing warrior", and one whose favorite catch-phrase was "Boostin Houston", her hometown. Every JAVA engineer needs a strong, sweet cup of coffee for inspiration every once and a while.
40.03.2019 Development of the Houston Server (Primary) is in progress. Its main purpose is that of a general-purpose processing node for the JAVA Enterprise Edition environment. In keeping with the JAVA tradition of universality, its goal is wide applicability. The first processing prototype for the Houston Primary is a general-purpose protocol handler. Its source code is currently available in a Netbeans *.zip archive. It, much like CABOOSE, leans heavily upon dynamic invocation for flexibility in processing and configurability. In the long-run, the Houston primary should serve as a single node in a network of such that can serve secondary requests for processing. In terms of it relationship with other Houston primaries, it is a peer with which they can exchange protocol request and state information.