[
Lists Home |
Date Index |
Thread Index
]
I'm not sure if it is the fact that a representative of MS talked about
this issue, but I do think there is some bias because of it. Would the
reactions have been less ardent had this article quoted a rep of Sun or
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
server. This would be helpful for WANs (especially for large companies or
friendly companies) that send and recieve huge amounts of information
across a network. I havent thought it completely through, but there are
possibilities. This would eliminate the need to send a request for infor
after sending info...
Aaron
|
