Entry 44 - RFC Repo Planning

RFC Repo Planning

Well, here is the concept I have so far. The formatting is vague, of course, but it is just a framework for content display and distributed linking. The sections outlined in GREEN will be accomplished on a local LAN interior server; that is, a computer stashed in a closet who's job it is to crunch the code that would probably lag the web server terribly, if I had the poor thing do it all in its head. Those outlined in RED will involve the final parsing of the data on the web server itself, which resides in the DMZ of the LAN. This should be low-impact enough to not spike load, but the heavier bits will be accomplished in the wee hours, so it should be good.

1. Backend raw data management
   • secured rysnc transfer from ietf.org
   • crontab sort
2. Dynamic update of RFC master list (XML document) with CLI PHP
   • crontab staggered, FiFo
   • crontab sort
   • txt2xhtml CLI scripting
3. Final background parse to chunked source files for fastest possible indexing
4. Dynamic generation of SSI's, indexed in second-tier XML tree
5. Integration into functional interface (multiple output formats (CSS1) for printer-friendliness)

Ideas for the actual frontend are too numerous and gloppy to elaborate on. One such experiment: clicking the link below will issue a random RFC in ASCII format. It will eventually be part of a form that allows a user to select threads (of interest to them) within the RFC history to track -- such as, say, XML, or IP routing, and have these topical datasheets posted (randomly) on the index page when they pop into hinkybox.

CLICK ME, I AM A POORLY WORDED LINK