OK the problem I posted about earlier is NOT a UDP/socket problem, it is
a threading problem. Albeit one that only happens when you have many
thrreads
I have made two little scripts using the code I copied below, one client
and one server (attached).
If I run them concurrently on the same mac
OK the problem I posted about earlier is NOT a UDP/socket problem, it is
a threading problem. Albeit one that only happens when you have many
thrreads
I have made two little scripts using the code I copied below, one client
and one server (attached).
If I run them concurrently on the same mac
Martin P. Hellwig wrote:
[snip]
> Is the connection 1:1 i.e. the receiving end receives data only from one
> sender at the time? And how do you handle lost packages in your
> application?
>
no the server is receiving from multiple clients.
and at the moment I do not handle lost packets.
--
http
Paul Sijben wrote:
> I am stumped by the following problem. I have a large multi-threaded
> server accepting communications on one UDP port (chosen for its supposed
> speed).
>
> I have been profiling the code and found that the UDP communication is
> my biggest drain on performance! Communication
Serge Orlov wrote:
> Paul Sijben wrote:
>> Serge Orlov wrote:
>>> Paul Sijben wrote:
I am stumped by the following problem. I have a large multi-threaded
server accepting communications on one UDP port (chosen for its supposed
speed).
I have been profiling the code and foun
Paul Sijben wrote:
> Serge Orlov wrote:
> > Paul Sijben wrote:
> >> I am stumped by the following problem. I have a large multi-threaded
> >> server accepting communications on one UDP port (chosen for its supposed
> >> speed).
> >>
> >> I have been profiling the code and found that the UDP commun
Serge Orlov wrote:
> Paul Sijben wrote:
>> I am stumped by the following problem. I have a large multi-threaded
>> server accepting communications on one UDP port (chosen for its supposed
>> speed).
>>
>> I have been profiling the code and found that the UDP communication is
>> my biggest drain on
Paul Sijben wrote:
> I am stumped by the following problem. I have a large multi-threaded
> server accepting communications on one UDP port (chosen for its supposed
> speed).
>
> I have been profiling the code and found that the UDP communication is
> my biggest drain on performance! Communication
I am stumped by the following problem. I have a large multi-threaded
server accepting communications on one UDP port (chosen for its supposed
speed).
I have been profiling the code and found that the UDP communication is
my biggest drain on performance! Communication where the client and the
serve
