Re: Documentation server
On Fri, 4 Jul 1997, Jason Gunthorpe wrote:
> I would tend to agree. It certainly allows a greater ease of
> Looking at the quick server you cooked up, I think it would be quite easy
> to make that secure, like you say, it's only a handfull of lines. The only
> big issue would be some kind of denial of service attack, and I think the
> simplest solution to that is to make the server non-inetd spawned and
> single instance/single session. To calm the paranoid you'd make it bind to
> 127.0.0.1 as well. (That would make it -totaly- invisible from outside the
> machine, the kernel would not even acknowledge it's existance)
> As for size, a single instance/single session server that is 3k in source
> will use a highly predictable amount of memory and processor time.
And about flexibility: The server coudn check if a local copy o a
ducment exist and if it doesnt't it would redirect to a remote copy...
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .