Francois PIETTE wrote:
> I don't really remember but I still have the email conercning that
> issue. I forwarded it to you provately.
Thanks, got it!
I wonder why Close shall not work given that messages are being
processed? Need to check that tomorrow.
--
Arno
>
> --
> [EMAIL PROTECTED]
> The
I don't really remember but I still have the email conercning that issue. I
forwarded it to you provately.
--
[EMAIL PROTECTED]
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
- Original Message -
Hi,
Can someone recall the the fix below in the FTP server?
Feb 26, 2002 V1.18 Fastream Technologies (http://www.fastream.com) found a bug
in Disconnect and DisconnectAll which prevented data connection
to be closed and client component to be destroyed.
Or maybe you
Hello Éric,
It is by design, so no bug. I forgot the reason because it is so long
ago, but you have to set addr, port, proto before call Listen and also
before calling Connect;
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Friday, December
Hello,
I also would like to know why this happens... I have released one version of
our software and I forgot to change the protocol to 'UDP' when stop -> start
listening and I have released it with a bug because ICS return to default
'TCP'
Éric Fleming Bonilha
Diretor de Tecnologia
Digifort -
Hello:
I just realized that if I close a listening
TWSocket component (to stop listening), it reverts
all defaults, including the listening port and
address, so that if I want to start listening again,
it will fail (unless I set the port).
Although I can very easily work around this, I was
j
