Am 27.01.2014 08:32, schrieb Stefan Koch:
On Sun, 26 Jan 2014 22:12:09 GMT, punkUser wrote:
Hmm ok, one more question on this... is there any way to basically do a "connectTCP" using a NetworkAddress instead of the host/port combo? I need to be able to connect to a system who's address I have only from a UDP packet (i.e. NetworkAddress structure) and there doesn't seem to be a way to convert that back to a string that I can see.
It looks like the driver implementations of connectTCP all immediately construct a NetworkAddress using resolveHost from the incoming parameters, so perhaps it wouldn't be too tough to provide this variant? Maybe have the drivers just use NetworkAddress structures directly and turn the current version of connectTCP into a little stub that calls resolveHost, etc?
I'll have a look, shall I ?
Would be appreciated, it definitely makes sense to add them! It's just
for historic reasons that it is this way (resolveHost was added after connectTCP et al.)