On Wed, 2010-03-24 at 16:13 +0100, IOhannes m zmoelnig wrote:
On 2010-03-24 00:39, Ivica Ico Bukvic wrote:
Hi all,
I've been trying to port my udp-based network communication to tcp-based and in a large ensemble netclient/netserver seemed like the best option. However, now that I've tested it in a couple sessions I am finding that every time I broadcast more than let's say dozen lines of text (coll data) which should be still less than a couple kb, I get nasty xruns (running through jack/linux). I am wondering what is causing this? Isn't netserver running in a separate thread?
Any ideas?
use mrpeach's [tcpserver]/[tcpclient].
I guess they suffer from the very same problem that I wrote about in my last post. However, it would be still interesting to see, whether they make any difference for Ivica's setup.
fmasdr IOhannes
PS: for what it is worth: i have forked mrpeach/net yesterday, with the aim to provide a simple (simpler than mrpeach's objects) high-performance (on my loopback device i was able to do about 600MBit/s read and write with Pd) without all the legacy encumberments of the original objects. (the plan is to simplify the api a little bit)
Yeah, I saw it in #dataflow. Are you also planning to address the buffer overrun problem?
Roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de