From: htoaster@yabbs
To: ziplock@yabbs
Subject: re: other ideas
Date: Tue Feb  8 00:12:57 1994
In message re: other ideas, ziplock said:
> Seems it would abuse the server a bit more after each post, but a hash
> table containing only the relevant header info would be one way of doing it
> that would speed the client response.  Then again, I've never tried to
> implement such a trick...

yeah, i was thinking about something along those lines.  Right now the
message bases are implemented using two files per message base, one for
the index and one for the message data, including all of the headers.  I could
put the headers in the index (since they are of fixed size), which might
speed stuff up a bit.  Rewriting the message base format again doesn't sound
that exciting, but it might be the best way.

I could also add a protocol command that is something like readnext:base:msgid,
where it finds the next readable message after the base and msgid.  Just 
thought about that, but coupled with changing the index method it might make
for the fastest searching for new messages.

My other idea would be to have each userid have a list of messages waiting
for them, and then when you post a new message it adds it to the end of the
userids waiting list.  The main problem with that would be maintaining it
on disk, because sometimes the server goes down without flushing the user
file.  I could make it build the list in memory on bootup though...

brainstorming while posting is so much fun :)...all these ideas keep popping
up.

alex