[158] in World Wide Web
["Albert Dvornik": Re: Error report ]
daemon@ATHENA.MIT.EDU (Albert Dvornik)
Thu Oct 14 09:37:21 1993
From: "Albert Dvornik" <bert@mit.edu>
To: www@mit.edu
Date: Thu, 14 Oct 93 09:36:55 EDT
------- Forwarded Message
To: webmaster@MIT.EDU
Subject: Re: Error report
Date: Thu, 14 Oct 93 09:34:05 EDT
From: "Albert Dvornik" <bert@MIT.EDU>
(stuff deleted)
5. I had a long discussion with Calvin about the "right" way of doing the
discuss gateway. There seem to be three basic ways:
A) run one discuss reader shared by all the server "children". (current)
Problem: race conditions break things.
B) run a discuss reader (probably dsgrep) when needed.
Problem: lots of gratuitous forking hoses server.
C) somehow run a single-thread Discuss client.
Problem: slow throughput annoys users. =)
I would personally go for the solution (C).
It can be made as simple as using "socket" from the watchmaker locker
or a similar tool to run edsc under a (single-threaded) server.
(A) can be hacked into blowing away the child on exits/restarts, but
if two of the servers compete for the edsc, things will probably break
a lot, since they'll be using the same file descriptor (or something
similar) for communicating with the edsc.
Comments? Suggestions?
- --bert
------- End of Forwarded Message
