H... If it is taking your system 5 to 7 MINUTES to process 1000 connect
/ disconnect cycles, then something is very wrong.
I would have to rerun my tests, but I am thinking that I was doing > 1K
connect / disconnects in about 10 to 15 seconds when running both server and
client on a single c
Hello:
Thank you for your very informative response. I
was performing some tests on my server application by
continually increasing the backlog value with some
mixed results, which seem to coincide with your
empirical analysis.
I kept increasing the backlog value up until I
reached 1000,
FYI... I ran into an issue with some test code I wrote a few months ago,
which related to the backlog setting, as well as the annoying issue with
Winsock running out of local ports. In my test, I was attempting to see how
many connections could be handled by a particular process over a period of
t
Hello:
I'm not sure if this is related to your problem,
but I had a similar incident in the past, and it
turned out to be an unchecked buffer in my
OnDataAvailable event handler which caused an
overflow, which led to the TWSocket component not
realizing that the buffer had been emptied and
trigg
[EMAIL PROTECTED] wrote:
>> Update your Delphi, preferably to the current version (Delphi 2007).
> .. and what kind of nightmare can I expect migrating over 6mb of d2
> code to d7?
The longer you wait upgrading to a current version the nightmare will
last longer ;-)
--
Arno Garrels
>
> Contri
[EMAIL PROTECTED] wrote:
> Its nice to have a mailing list where you can get
> many people addressing the same questions :)
Agreed, and don't forget the free sources.
Do you realy need more?
--
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto htt
Hello all,
I'm using ICS version 6.06 with Turbo C++ Explorer 2006.
I had been fighting a problem where my DataAvailable event was being
called twice as many times (minus 1) as actually needed. Since I've
been using the ICS components for many, many years now, I obviously
started lookin
> Update your Delphi, preferably to the current version (Delphi 2007).
.. and what kind of nightmare can I expect migrating over 6mb of d2
code to d7?
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
Author of ICS (Internet Component Suite, freeware)
A
Pablo,
Are you having more problems?
P.S. Puedes comunicarte conmigo directamente si
necesitas ayuda en español.
Translation: You can contact me directly if you
require help in Spanish.
-dZ.
>--- Original Message ---
>From: Pablo
Harguindey[mailto:[EMAIL PROTECTED]
>S
>--- Original Message ---
>From: Arno Garrels[mailto:[EMAIL PROTECTED]
>
> OnSessionAvailable is called only on listening
TWSockets,
> as I read the post it deals with a client
(connecting party).
Thanks, Arno. You are right; I misread his message
but didn't realize this after sending
*help
-Mensaje original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Arno Garrels
Enviado el: Miércoles, 28 de Noviembre de 2007 15:37
Para: ICS support mailing
Asunto: Re: [twsocket] I need some help understanding TWsocket states
[EMAIL PROTECTED] wrote:
> Hello:
>Th
Hello:
The problem with retrying is that it is not the same
as a "server full" error when the maximum number of
clients is reached; 100061 is essentially a "port not
open" error, which is the same error you would get if
the server is not running. So there is no real way
to know that the listener
Wilfried you are a total star.
If you are ever in Edinburgh I'll buy you a cake (or a whisky) or whatever.
That works!
Wilfried Mestdagh wrote:
> Hello Pete,
>
>
>>mytwsocket.addr := '127.0.0.1';
>>mytwsocket.port := '17072';
>>mytwsocket.connect();
>>
>
> that's
I would also imagine that testing this within the
local host will also affect the backlog, as you are
establishing both sides of the socket within the same
host, limiting the resources, no?
-dZ.
>--- Original Message ---
>From: Arno Garrels[mailto:[EMAIL PROTECTED]
>Sent: 11/2
[EMAIL PROTECTED] wrote:
> Hello:
>This may sound stupid, but could you verify that
> the OnSessionAvailable event is actually wired
> (assigned to the property)? It seems strange that it
> is not called, yet OnDataSent is.
OnSessionAvailable is called only on listening TWSockets,
as I read t
Pete Williams wrote:
> My client wants to sometimes connect to the server, send a few lines
> of data, and then disconnect.
>
> When I want to send data this is what I do
>
> procedure sendData(asMessage: string);
> begin
> mystringlist.add(asMessage);
> if mytwsocket.state <> wsConnected
Hello:
OnSessionAvailable is triggered when an incoming
connection is about to be established, as soon as the
request is received, but before the socket is
properly opened. OnSessionConnected is triggered
right after the connection, either incoming or
outgoing, is properly established and stat
Hello dz,
I think 5 is the winsock default value
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Wednesday, November 28, 2007, 19:01, [EMAIL PROTECTED] wrote:
>>--- Original Message ---
>>From: Paul[mailto:[EMAIL PROTECTED]
>>
Hello dz,
a client application should do at least a few (or infinity) retry's if
connection fails. so normally not needed to increase it. On the other
hand it does no harm to increase it.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Wednes
Hello Pete,
>mytwsocket.addr := '127.0.0.1';
>mytwsocket.port := '17072';
>mytwsocket.connect();
that's ok
> OnSessionAvailable doesn't seem to get called ever.
No you need OnSessionConnected. OnSessionAvailable is for server
sockets.
> In OnDataSent I do this
> begin
Paul wrote:
> I always use 500, no problems yet
But the ListenbacklogQueue is limited in size depending
on the OS (cannot recall the values, however it's far less
then 500, AFAIR). The more "blocking" the server behaves the
earlier you get 10061 back from a connect. Simple test is with
TcpSrv Demo
I don't mind checking simple stuff. I'm desperate, as I have a deadline
for Saturday!
It is definately connected & hooked-up. Nothing is over-writing it.
[EMAIL PROTECTED] wrote:
> Hello:
>This may sound stupid, but could you verify that
> the OnSessionAvailable event is actually wired
> (as
>--- Original Message ---
>From: Paul[mailto:[EMAIL PROTECTED]
>
> I always use 500, no problems yet
Thanks for the quick reply.
Then, is there a particular reason why it defaults to
5? It seems too low for all but the most trivial
applications (given that spawning the client object
Hello:
This may sound stupid, but could you verify that
the OnSessionAvailable event is actually wired
(assigned to the property)? It seems strange that it
is not called, yet OnDataSent is.
Also, what happens when you try to send a second
time (or does it even try)? Do you get a "Component
I always use 500, no problems yet
Paul
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Wednesday, November 28, 2007 6:27 PM
Subject: [twsocket] TWSocketServer and backlog
> Hello:
>While stress-testing my application, I noticed
> that I am able to send substantially many
Thank you to the two people who replied. I got really good advice which
I followed and this seems to have given me a working server, but I still
have client problems.
- I created a message-pump in a distinct thread for the DLL server, as
advised.
- Both client and server were changed to async p
Hello:
While stress-testing my application, I noticed
that I am able to send substantially many more
connections in the time it takes the TWSocketServer
to handle the incomming requests, causing the default
backlog to fill up quickly. Obviously, I can
increase the number, but seeing that the d
> hey just woundering.
> will ICS work with turbo delphi?
Turbo Delphi is Delphi 2006 so there is no problem.
Note that Turbo Delphi Explorer (the free version) doesn't want to install
third party components so you can't install ICS components nor any other in
the Tools Palette. This doesn't prohi
Robert W Harris wrote:
> hey just woundering.
> will ICS work with turbo delphi?
Yes, the Turbos basically are BDS2006 with just the Delphi personality,
however the free Version doesn't allow components to be installed in the
IDE, instead you have to create the ICS-Objects at runtime.
--
Arno Gar
[EMAIL PROTECTED] wrote:
> That's it! I just changed {$IFDEF DELPHI3} to {$IFDEF DELPHI2} and it
> compiled.
Fine, so most likely in both D2 and D3 a DWORD is mapped to a signed
longint. Since Delph 4 however it's a true unsigned 32 bit integer.
If you chang the conditional to "{$IFDEF DELPHI2}"
30 matches
Mail list logo
