Cart
[Home] [By Thread] [By Date] [Recent Entries]
On Wednesday 27 February 2002 13:09, AManns@u... wrote:
> Apache.....? I do feel there is room for a protocol (or protocol
> enhancement)that will allow both sides to be server and client. Perhaps,
> instead of the request, wait, send, wait,listen, wait,request,....cycle for
> sending and receiving information, one could send information as a server
> to another machine with a 'request needed bit' somewhere in the header
> which would then turn the server into a client, and the client into a
[snip]
IMAP does this, more or less. Each message in either direction is prefixed
with an ID - just a random string of 6 characters, from memory. Responses to
that request have the same ID. Those IDs are used to associated requests with
responses rather than temporal constraints as are used in HTTP, which allows
for temporal interleaving, which is nice - and bidirectionality sort of comes
for free.
ABS
--
Alaric B. Snell
http://www.alaric-snell.com/ http://RFC.net/ http://www.warhead.org.uk/
Any sufficiently advanced technology can be emulated in software
|
