 | | Re: Pseudo-streaming live news (was: Re: Monitor Page)
|
|
(...) Too late! All done! :-, But that would be easy to do; I could simply write a daemon class that consumes tidbits by spooling them for serving later. The drawback to doing this, is that one *might* need to run two JVM's -- one for the spooler, (...) (27 years ago, 21-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Pseudo-streaming live news (was: Re: Monitor Page)
|
|
(...) replying to myself (I did decide I need it) - I read lugnet both at work and at home - I havn't found an easy way to sync the two, so I'm writing my own :) Thanks for putting out the API that allows me to do it... (...) yup, similar to what (...) (27 years ago, 21-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Pseudo-streaming live news (was: Re: Monitor Page)
|
|
(...) Depends on the newsreader...most newsreaders (that I've ever seen) either store articles in a proprietary compresses formart or don't store copies at all. It's also a lot more work on the newsserver if clients are connecting via NNTP and (...) (27 years ago, 21-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Pseudo-streaming live news (was: Re: Monitor Page)
|
|
In lugnet.admin.general, Todd Lehman writes: One suggestion: Separate the producer into a separate, totally encapsulated (...) I thought of doing that, though - what's the differnece between a newsreader and my script then? that it works over http (...) (27 years ago, 21-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Pseudo-streaming live news (was: Re: Monitor Page)
|
|
(...) Great! Neat-o! One suggestion: Separate the producer into a separate, totally encapsulated daemon which just sits there running 24x7 and slurps new articles whenever they appear and spools them into some directory on the local drive. That way, (...) (27 years ago, 21-Mar-00, to lugnet.admin.general)
|