Bugs item #3433409, was opened at 2011-11-04 02:18 Message generated for change (Tracker Item Submitted) made by reduzent You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3433409...

Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Roman Haefeli (reduzent) Assigned to: Nobody/Anonymous (nobody) Summary: mrpeach/tcpclient: sends messages out of order

Initial Comment: When sending messages to the network, [tcpclient] does not keep the same order as messages came in through it's inlet. Attached patch illustrates the problem.

I think IOhannes once pointed out that keeping the order theoretically could be an issue with the implementation of mrpeach's [tcp*] classes. It seems to be a real-world issue now.

The same issue cannot be triggered with [mrpeach/tcpsend] and also not with [iemnet/tcpclient].

If I recall correctly, the old blocking version of [tcpclient] did not suffer from this issue. IMHO, blocking Pd would be preferable over losing the integrity of the data stream. Even more since there is a working non-blocking implementation in iemnet.

This happens with/on: - mrpeach/net r15702 - Pd 0.43.1test4 - Ubuntu 10.04 / 11.04

----------------------------------------------------------------------

You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3433409...