Subject:
|
Re: LugnetReader
|
Newsgroups:
|
lugnet.admin.nntp
|
Date:
|
Wed, 3 May 2000 16:52:58 GMT
|
Reply-To:
|
JSPROAT@IO.COMsaynotospam
|
Viewed:
|
198 times
|
| |
|
|
Dan Boger wrote:
> Jeremy H. Sproat wrote:
> > Dan Boger wrote:
> > > Susan Hoover wrote:
> > > > Is there a LUGNET discussion of LugnetReader somewhere?
> > Oooh, good question. We really need some place to discuss it, esp. (right
> > now) the spooler -> client API.
> guess we have that now - FUT to lugnet.admin.nntp :)
I am *SO* here. :-,
> > How releasable is your spooler? Good enough to let me work with it for my
> > client?
> well, the spooler right now just sits there all the time, getting messages
> once a minute, and stores them on disk in a spool directory - each message
> would be stored and linked by at least three indexes - by xref, by avid • ? number, and by groups... The the spooler writes a log file of each
> incoming message, and the client reads it from the spool dir. Not great,
> but workable. I plan to write a telnet based interface with it, so remote
> clients can read the spool as well.
If you have the spooling and indexing portion down, I'd personally give the
telnet interface top priority now.
...The indexing feature brings up the question as to whether the telnet
interface will be 1-way or 2-way. If it were 2-way, the spooler could
conceivably serve messages based upon some search criteria. It would rock if
you can implement a shell for the spooler, with a well-defined command set.
> Now I'm just trying to figure out if
> it's worth the bother, or just use the avid.cgi directly...
Exactly what benefits can be gotten from spooling? The only ones I can think
of are:
- (semi-) local caching of messages, also a local copy of LUGNET for those
late-night "where did I post that message" search sessions
- a common area to save "user profiles"; i.e. read-message markers,
line-wrapping settings, etc.
OTOH, the benefits of having the client read avlid.cgi directly are:
- *slightly* lower lag time between a new message and when the client sees
it
Hmmm.
> > > And to see if it can work on windows :)
> > I'll beta-test that for ya, Dan. :-, I'm fairly familiar with Perl, in both
> > Unix and Win32 environments.
> Thanks! That'd be great... Do you happen to know if there's a TK module
> for win?
Yes there is. However, I haven't built this for a while... Are you using the
Tk module from CPAN?
I'm actually more interested in testing the spooler than the client. And to
"borrow" (:-) your API ideas to implement a spooler in Java, and to have some
input on the design of said API if I need something added. My goal is to be
able to use your spooler with my client, and vice-versa.
Cheers,
- jsproat
--
Jeremy H. Sproat <jsproat@io.com> ~~~ http://www.io.com/~jsproat/
I think the mistake a lot of us make
is thinking the state-appointed shrink is our friend.
|
|
Message has 1 Reply:
 | | Re: LugnetReader
|
| (...) well, since it's my only way of reading lugnet atm, I am a little more concenred with the client... but I'll get to it, eventually :) (...) yup, that was the plan (to make it 2 way). I'd like it to be useful for a clientless client (just (...) (25 years ago, 3-May-00, to lugnet.admin.nntp)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
