|Subject:||Re: A UDP design question|
|Posted by:||Malcolm Smith (email@example.com)|
|Date:||Tue, 18 Sep 2007|
I just discovered something I was not aware of.
When my client writes to the server, the server is logging the peer port as
If I then send another request from the same client (the
TIdUDPClient::Active property is always true), the server is logging the
peer port as Y.
Should this be happening ? If this is normal, am I going to be forced to
have a 'server' within each client application and then use a known range of
allowed ports to communicate video from the real server back the client's
C++Builder Developers Journal
A UDP design question posted by Malcolm Smith on Mon, 17 Sep 2007