That was a fun read, thanks!
On Fri, Oct 11, 2013 at 4:09 AM, Pieter Hintjens <[email protected]> wrote: > Yes, the stream socket returns each TCP receive as one message. There is > no other sinple way to read the TCP stream. > On Oct 11, 2013 8:19 AM, "[email protected]" <[email protected]> > wrote: > >> I've added the Stream socket stuff under my VASmalltalk wrapper and >> published blog postings describing a server usage here: >> >> >> http://schrievkrom.wordpress.com/2013/10/10/vasmalltalk-0mq-4-0-and-the-stream-socket/ >> >> ... and a client usage here: >> >> >> http://schrievkrom.wordpress.com/2013/10/11/vasmalltalk-0mq-4-0-stream-socket-as-a-client/ >> >> The client one is an interesting one. What are the decision how many >> messages are send to the application program. In the client example I >> query the main page of www.google.de and get around 26 messages as the >> answer - each message has a data frame size between 1430 and 2860 bytes. >> Is this somehow corresponding with the size of a tcpip frame ? >> >> Marten >> >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
