| 
     
      
      
      From: Wizard <wi...@ne...> - 2003-01-21 14:39:26
      
     
   | 
<SNIP> > Then the index looks like: >=20 > 12+: 14 17 18 I'm not sure that if we have an expected XML hierarchy, how this is any = different. It's one thing to have a format with unexpected input (i.e, = true XML), but I don't see that parsing a defined XML format is any = different than parsing an HTML format, except that the hierarchy is more = determinate. The plus is that should we decide to later include full XML = parsing, then the formats is already there. I think that this would ease = the implementation of future enhancements such as database backends, = XSLT, and document conversion. >=20 > and contains a list of messages and the responses to it. The + = indicates > that the message is the head of a thread. >=20 > A script would be provided to rebuild the index from the data files. >=20 > In use, html pages would be generated for each thread and cached, = either > on request or on change. >=20 > If the data set got very large then it could be extended by adding a > threadhead: field to the data format and extending the index to store > *all* the responses in that thread which would cut down the amount of > data that would need to be read in any one go. I'm not sure that I'm really grasping all of this (read 'my brain = hurts'), but perhaps you could patch together some example files with = comments, and I'll trying to get a better understanding. I'm thinking = 'singly-linked list', but it's just not working out in my head. Thanks! Grant M.  |