On 2013-05-20 11:58, IOhannes zmölnig wrote:
On 05/20/2013 05:45 PM, Martin Peach wrote:
There is more than one version of [tcpserver] around. In Pd-extended
there is [net/tcpserver], [iemnet/tcpserver] and [mrpeach/tcpserver].
isn't [net/tcpserver] the same as [mrpeach/tcpserver]?
Yes, that
On 05/20/2013 05:45 PM, Martin Peach wrote:
There is more than one version of [tcpserver] around. In Pd-extended
there is [net/tcpserver], [iemnet/tcpserver] and [mrpeach/tcpserver].
isn't [net/tcpserver] the same as [mrpeach/tcpserver]?
fgamsrd
IOhannes
__
On 2013-05-20 08:19, Antoine Villeret wrote:
Hi Martin,
Thanks for your reply.
For now, I increase the MAX_CONNECT value and I also make each client
disconnecting after they receive expected data, and they connect again
if needed.
But I experience another issue.
If Pd crashes for any reason, t
shame on me,
there does exist a [port ( message in iemnet's tcpserver with
which I can change the port on the fly
the rightmost outlet sends [port -1( if binding failed
but this is not explained in the help patch, I should have to go through
the code to see that
could I push an updated version of
Hi Martin,
Thanks for your reply.
For now, I increase the MAX_CONNECT value and I also make each client
disconnecting after they receive expected data, and they connect again if
needed.
But I experience another issue.
If Pd crashes for any reason, the socket stay in a TIME_WAIT state and if
Pd r
Yes, it seems that the routine that adds new connections doesn't check
to see if it has passed the number of connection slots.
There are MAX_CONNECT slots allocated when [tcpserver] starts.
Thanks for finding this bug!
There is no reason to limit the number of connections to 32 except to
not u
so I reply to myself...
I found this in the code of both tcpserver.c :
#define MAX_CONNECT 32 /* maximum number of connections */
which could be an answer embryo
so, I shouldn't make more than 32 connections on the same tcpserver, ok,
but why ?
is there a good reason to fix this to 32 ?
and thi
hi all,
I've just notice [tcpserver] crashes when the 34th client try to connect
both iemnet and mrpeach are affected
iemnet version send a strange number on the 33th connection
(like 2.8686e+07) and crashes on the 34th
here is a gdb output for iem :
Program received signal SIGSEGV, Segmentatio
