Conduit / News: Recent posts

Well, Conduit can finally start all threads successfully and catch any start up errors that can occur.

It is now aware of the messages it receives, which means it has its own message format, which is any data framed in an ASCII 2 and 3; it can recognize line-based messages, which is any non-framed message that ends with a newline ('\n'); and any other message that does not match the previous message formats.... read more

The short term goal is to have a working, if not basic, program by the end of January 2005. This will include an analyzer, trace and management service (all running under one process) and basic rule and event handling. Events will most likely be limited to C shared libraries at this stage, with the ability to write events in Perl shortly after. It is possible a basic configuration parser will also be available rather than limited to command-line options only. Currently there are almost 2 dozen options so a config file parser is really needed.

It's always fun starting a new and exciting project. I think the code is coming along nicely. The project is progressing faster than I expected (of course I'm sitting here posting early Christmas morning :)).

So far a basic server with a main thread and a trace thread is coded. The trace thread provides a way for one, or many, analyzer servers to send debugging information. This allows large deployments to collect all this information on one server. It is possible to have a dedicated trace server. In small deployments (single analyzer server), it is probably simpler to have the trace server listen on 127.0.0.1 (the default) so the analyzer can simply use the local interface to output trace information.... read more