$Bill said:Sure I did. Using more than 1 msg necessitates state info and probably
maintaining an open socket.
If 'an open socket' wasn't supposed to be maintained, the whole question
would be moot as 'closing the socket' would/ could mark the end of 'the
How does the state information needed to read the HTTP response above
change whether you view it as one or two (or five) messages?
You don't need state info if there's only 1 msg.
I think you just want to argue. I was responding to George's scenario:
when you want complex things like.
-- hey client, I am going to send you a file so big
++ ok server
I think you misunderstood that and that George was providing simplified
examples of his actual messages, eg, that 'hey client, I am going to
send you a file so big' is supposed to refer to something like sending a
header with a command code of 'file falling from the sky' and a size,
followed by the file data and that '++ok server' is the client telling
the server that it has processed/ downloaded the file and is ready for
the next protocol exchange (unusually organized here because the
server seems to be active instead of acting on client requests but even
this might be an impression accidentally caused by the textual form).