I have got to the bottom of the Error 10048
This means the port you are trying to use is already used and thus is no
more available.
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
ICS guys, I humbly ask you to pay attention on my previous message.
--
Anton
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
Hello Anton,
1) Excess ancient defines
The code is cleaned up as we goes by.
3) HTTPCliWindowProc
function HTTPCliWindowProc is never used, maybe it should be removed?
If not used anymore, yes.
2) $IF defines
Same as (1)
4) THttpBigInt
THttpBigInt type - is it really needed?
That's too bad.
-Original Message-
From: Arno Garrels
Sent: Tuesday, April 12, 2011 7:15 PM
To: ICS support mailing
Subject: Re: [twsocket] Receive log file text
daniel cc wrote:
Thanks Arno :)
I understand perfectly,
Do we have any samples about this?
I do not think so.
daniel cc wrote:
That's too bad.
I hope my description was useful to get the picture.
The implementation is up to you and should be an easy task
for a (Delphi) developer IMO. If you run into problems specific
to ICS please ask your question in the list.
--
Arno Garrels
-Original
Hi
I´m experiencing a very weird problem and I hope someone can help me
My application receives UDP data from IP Cameras, somehow we are not receiving
some packets, but by using a network sniffer I can see that the packet was
received, but the application never receives it!
I´m using TWSocket
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 =
My application receives UDP data from IP Cameras, somehow we are not
receiving some
packets, but by using a network sniffer I can see that the packet was
received, but the
application never receives it!
I already checked receive buffer lengths.. I actually spent 2 entire days
cheking for
So This leads me to think that TWSocket is not
closing/freeing/de-allocating
the LocalPort, such that when I try to reopen the connection a few seconds
after I close it, windows raises the 10048 error due to the LocalPort
still
being allocated
Is this the case
No, it isn't. But Windows
