[QUOTE="$Bill"]\nSure I did. Using more than 1 msg necessitates state info and probably\nmaintaining an open socket.[/QUOTE]\n\nIf 'an open socket' wasn't supposed to be maintained, the whole question\nwould be moot as 'closing the socket' would/ could mark the end of 'the\ncurrent message'.\n[QUOTE][QUOTE]\nHow does the state information needed to read the HTTP response above\nchange whether you view it as one or two (or five) messages?[/QUOTE]\n\nYou don't need state info if there's only 1 msg. \n[...]\n\nI think you just want to argue. I was responding to George's scenario:\n\n when you want complex things like.\n\n -\- hey client, I am going to send you a file so big\n ++ ok server[/QUOTE]\n\nI think you misunderstood that and that George was providing simplified\nexamples of his actual messages, eg, that 'hey client, I am going to\nsend you a file so big' is supposed to refer to something like sending a\nheader with a command code of 'file falling from the sky' and a size,\nfollowed by the file data and that '++ok server' is the client telling\nthe server that it has processed/ downloaded the file and is ready for\nthe next protocol exchange (unusually organized here because the\nserver seems to be active instead of acting on client requests but even\nthis might be an impression accidentally caused by the textual form).