TUdpSocket LocalPort property

Thread View: borland.public.cppbuilder.internet.socket

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Antti Arola Sat, 24 Jan 2004 20:32

#5795

Author: Antti Arola
Date: Sat, 24 Jan 2004 20:32

17 lines
1687 bytes

Hi,

does someone have a fix for the following TUdpSocket (maybe also 
TCustomIpClient, TIpSocket) problem?

The value of LocalPort does not affect anything, the real port number to 
which it the socket is bound is always allocated dynamically. (This can be 
tested by sending datagrams to e.g. NMUDP socket, whose localport is 
known, and printing the origin's port number.)

This causes that reception with UdpSocket is impossible, unless the sender 
first gets to know the dynamic port#.


Regards,
antti

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads