On Sun, Mar 06, 2005 at 07:40:11PM -0500, Dossy Shiobara wrote: > On the other hand, I do think a set of very high-level design documents > that outline the overall strategies implemented in AOLserver would be > useful. I'm thinking at the level that would be suitable as bullet > points on a PowerPoint deck, like: "AOLserver 4.1 employs a single > driver thread to accept TCP connections then dispatches requests to > connection threads for request processing." That's as detailed as I'd > go -- this way, as the actual implementation changes, it doesn't > immediately obsolete large chunks of the design doc.
No. When I say "document the internals" I mean REALLY EXPLAINING them, educating the reader as to just what all the major moving parts really actually do, and why. Ideally, engineer to engineer mental download, all the thoughts and trade-offs that drove Jim's design explicated in text. This is a totally different thing from merely sketching out the very highest-level concepts. A sketch of all the high-level concepts would indeed be valuable, I just want to be clear that such a sketch is in no way a replacement for a full guide to the design of the AOLserver internals. I think Jim D.'s old Tcl conference presentation on AOLserver in Digital City is an excellent example of the high-ish level sketch you're talking about. In the course of discussing a very large real-world web/db application, it covered an interesting variety of hands-on AOLserver details. But it definitely wasn't anything close to what a new AOLserver hacker would consider adequate for groking the AOLserver internals, nor would anyone expect it to be. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
