Hi...
Quote:
>When you don't assign the LocalPort, Windows automatically assign an
>available local port. This is usually what is done for connecting to a
>remote host. If you have any reason not to do so, just explain why.
If I use this code:
TheTCPClientSocket->Addr = TCP_ClientAdd
Hi...
I have got to the bottom of the Error 10048
It seems that the order in witch you assign values to the TWSocket
properties when you want to open a client is important
- so now I can open and close the client heaps of times with out the
error 10048 being raised :-)
The code I was using l
Hi all...
I am running on Windows XP, Embarcadero XE
I am using the TWSocket Version:7.47 in Client mode to connect to another
PC on my LAN which is also using TWSocket in Listen mode.
When I call the TWSocket->Connect() for the first time every thing works
perfectly, the connection is mad
Hi...
Microchip use a "Discovery" protocol to allow devices running their TCP/IP
stack to be easily discovered on a network
This protocol allows the user to quickly discover ALL microchip devices
on a given network
The protocol is UDP based, and just responds to a Dbeing sent to UDP
p
Hi all..
If I use TWSocket in UDP mode, do I require 2 TWSocket components (1 to Send
and 1 to listen)
is this correct ??or can 1 TWSocket be used to send and listen to UDP
data
Thanks for any help
Ray
--
To unsubscribe or change your settings for TWSocket mailing list
please go