On CbuilderXE if I create a TWSocketServer and the I call the ClientCount
method I get an access violation.
If The debugger query the method fSrvWSocket->ClientCount give the following
error:
E2122 Function call terminated by unhandled exception 0xc005 at address
0x6f4c7363
Belowe the sam
Tony Caduto wrote:
> I see there is a LineLimitExceeded event, but not sure how to use it.
By default the component clears the internal line buffer if the end of
line marker wasn't found. I would assume some attack or a suspicious
client when that happens at the server side and close the connecti
Hi,
I am new to ICS, I have always used blocking sockets in the past(synpase)
and I recently made a messenger server with ICS and
I use the linemode to get the commands etc.
My question is how do you handle the situation where the line length is
greater than the default linelimit param?
I see ther
uot;
To: "ICS support mailing"
Sent: Monday, February 14, 2011 2:19 PM
Subject: Re: [twsocket] TWSocketServer & TWSocketClient send receive files
Thank you :)
Just what wanted to hear.
With best regards
-Original Message-
From: Francois PIETTE
Sent: Monday, Febr
Thank you :)
Just what wanted to hear.
With best regards
-Original Message-
From: Francois PIETTE
Sent: Monday, February 14, 2011 2:19 PM
To: ICS support mailing
Subject: Re: [twsocket] TWSocketServer & TWSocketClient send receive files
FTP, HTTTP, SMTP/POP3, NNTP are all capabl
FTP, HTTTP, SMTP/POP3, NNTP are all capable of transmit file and they are
standard protocols based on TCP sockets.
You may also design your own protocol based on your own requirements which
are...
--> I actualy have the protocol which is just the command based and
everything works real good and s
Thanks Francois,
I probably need to get into this abit more.
I have some more details..
What about file metadata such as filename and timestamp ?
What about permissions to access the file at sender side and to write the
file at receiver side ?
--> I actualy think I could handle it on the both si
I hope this was clear.
Not enough. see below.
I need to send single file from the server and receive single file from
the client (1 file at the time such as: .txt, .exe).
What about file metadata such as filename and timestamp ?
What about permissions to access the file at sender side and to
maximum of 100MB
Is it possible to do it over the socket with for example file stream?
if not what are your suggestions?
I hope this was clear.
Best regards
-Original Message-
From: Francois PIETTE
Sent: Monday, February 14, 2011 12:38 PM
To: ICS support mailing
Subject: Re: [twsocket
Can someone please guide me to a correct demo/sample of how to send &
receive files?
Do you have any preference about the protocol to use ?
What are your requirement ? "Send and receive" file is a little bit short to
describe your needs.
--
francois.pie...@overbyte.be
The author of the freewa
Hello,
Can someone please guide me to a correct demo/sample of how to send & receive
files?
thanks in advance
--
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
Probably because it is automatic in C++(?)
Regards,
SZ
On Tue, Feb 1, 2011 at 5:53 PM, Anton S. wrote:
> Tobias, oh, thanks a lot! Today is the day when I use to forget to call
> ancestors' methods :)
>
> --
> Anton
> --
> To unsubscribe or change your settings for TWSocket mailing list
> plea
Tobias, oh, thanks a lot! Today is the day when I use to forget to call
ancestors' methods :)
--
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!
> destructor TSrvClient.Destroy;
> begin
> FreeAndNil(FList); // *** set breakpoint here to ensure client is destroyed
> ***
> end;
This should be:
destructor TSrvClient.Destroy;
begin
FreeAndNil(FList);
inherited; // <-- added call to ancestor
end;
Regards,
Tobias
--
To
I faced strange issue when connected clients seem not to be removed from
server's list on disconnect.
I wrote simple demo project to test this, it'll be later. In short words,
client objects seem to never be deleted from FClientList. I've set breakpoint
on the line "FClientList.Remove(AComponent
RTT wrote:
> That's why the security agencies don't like closed protocols.
Nobody knows whether a proprietary security protocol has some
built-in universal key, given i.e. to a security agency.
That's also why users should not rely on proprietary security
protocols and cryptographic algorithms.
On 27-01-2011 18:27, Arno Garrels wrote:
Without the certificate(s) and private key(s) he may intercept transparently
as long as he likes. When he wants to decrypt the session on the fly he
has to go thru the handshake process on behave of the victim by presenting
the stolen certificate(s), actin
RTT wrote:
>> With a stolen key that's easy.
>
> Sure, and this is exactly what SSL try to circumvent.
> But not so easy if the encrypt key is not a fixed value, but a
> variable one. The attacker will need to stole the client or server
> code and reverse engineering it too.
>
>>> This is also va
SOLVED!!
-Original Message-
From: daniel cc
Sent: Thursday, January 27, 2011 7:33 PM
To: ICS support mailing
Subject: Re: [twsocket] TWSocketServer and TWSocket Port
So, leave SSL apart for now.
I don't see any reasons to leave the SSL because I already spent 3 weeks
with m
So, leave SSL apart for now.
I don't see any reasons to leave the SSL because I already spent 3 weeks
with making lot of tests and have learned much about SSL and I will
continue.
I am also hoping that you guys try to understand my approach instead of
asking to leave it.
SSL is good enough f
With a stolen key that's easy.
Sure, and this is exactly what SSL try to circumvent.
But not so easy if the encrypt key is not a fixed value, but a variable
one. The attacker will need to stole the client or server code and
reverse engineering it too.
This is also valid for SSL.
No, the
It is a very simple monitoring system.
SSL is okay for this as far as I am concerned.
As others have say to you already, just concentrate your efforts in the
development of the client and server code. Leave the data encryption to
the last stage of the project.
Starting with the SSL componen
RTT wrote:
>>> "Man in the Middle" attacks don't work if the "man in the middle"
>>> don't know how to handle the encrypted data/protocol he is
>>> intercepting.
>> True, and how do you manage that is not happening?
>
> Can't be happening because the man in the middle can't generate valid
> data,
It's easy to implement encryption but you'll have to add key exchange also and
exclude possibility of key sniffing what is quite harder.
Just start with a fixed strong password, and add to it a variable salt
that can be a hash of some of the client/server header fields. One of
this fields c
RTT:
Why you insist in use SSL if the client and server applications are
coded by you?!! Why use a standard that only exist because of the need
to connect many different implementations of clients to many different
implementations of servers?
It's easy to implement encryption but you'll have to
RTT,
First,
I am not building a bank system where I would need extremely high security.
It is a very simple monitoring system.
SSL is okay for this as far as I am concerned.
You may be right or may not.
For me the mosty important here is to learn one thing at a time.
If I listen you,
I have to s
"Man in the Middle" attacks don't work if the "man in the middle"
don't know how to handle the encrypted data/protocol he is
intercepting.
True, and how do you manage that is not happening?
Can't be happening because the man in the middle can't generate valid
data, or alter intercepted data
RTT wrote:
>> SSL/TLS aktually uses common, powerful and strong encryption
>> algorithms. However secure peer to peer communication is much more
>> than just that. SSL security includes, for instance, peer
>> verification and protects against "Man in the Middle" attacks.
>
> "Man in the Middle" at
On 26-01-2011 20:15, daniel cc wrote:
I Insist because I have no other options because I don't have
knowledge of doing it in the other way.
So, you just need to learn how to use a common web search engine and how
to make the right questions at the right places.
Reading old replies to your que
SSL/TLS aktually uses common, powerful and strong encryption algorithms.
However secure peer to peer communication is much more than just that.
SSL security includes, for instance, peer verification and protects
against "Man in the Middle" attacks.
"Man in the Middle" attacks don't work if the
Thanks Arno,
Your answer is just a music to my ears :)
RTT wrote:
(I am using SSL sockets in both sites)
Why you insist in use SSL if the client and server applications are
coded by you?!! Why use a standard that only exist because of the need
to connect many different implementations of clie
(I am using SSL sockets in both sites)
Why you insist in use SSL if the client and server applications are
coded by you?!! Why use a standard that only exist because of the need
to connect many different implementations of clients to many different
implementations of servers?
You will be much
RTT wrote:
>> (I am using SSL sockets in both sites)
>
> Why you insist in use SSL if the client and server applications are
> coded by you?!! Why use a standard that only exist because of the need
> to connect many different implementations of clients to many different
> implementations of server
(I am using SSL sockets in both sites)
Why you insist in use SSL if the client and server applications are
coded by you?!! Why use a standard that only exist because of the need
to connect many different implementations of clients to many different
implementations of servers?
You will be mu
daniel cc wrote:
> I need to open port 443 in both sites.
Note that port 443 is the standard port for HTTPS
used by webservers. So that port might be in use or if
your application manages to bind to that port first the
webserver might fail listening.
--
Arno Garrels
--
To unsubscribe or cha
Please do correct me if I am wrong.
Now,
You are saying that it is not possible to have only server port opened, I
need to open port 443 in both sites.
Site A port 443 need to be open from PC and from the firewall.
Site B port 443 need to be open from PC and from firewall.
No, I didn't meant
The use only one socket and make all communications over that unique
connection. No other choise in your situation.
Thanks Francois,
Please do correct me if I am wrong.
Now,
You are saying that it is not possible to have only server port opened, I
need to open port 443 in both sites.
Site A
I would like to use the same port which the site A uses when it connects
to the site B.
Yes, you can have a same listening port at both sides.
Thanks for the response.
Yes,
I know I can listen same ports but my question is,
can I do that at "Site A" without opening any ports at the
routers/f
I would like to use the same port which the site A uses when it connects
to the site B.
Yes, you can have a same listening port at both sides.
Thanks for the response.
Yes,
I know I can listen same ports but my question is,
can I do that at "Site A" without opening any ports at the
routers/f
I would like to use the same port which the site A uses when it connects
to the site B.
Yes, you can have a same listening port at both sides.
--
francois.pie...@overbyte.be
http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elis
Hello all,
If I have server and client component at one side,
server and client component at the other side
Side A: TWSocketServer and TWSocket ==> Acts as client
Side B: TWSocketServer and TWSocket ==> Acts as server
Side A connects automatically to the site B because site A is acting as client
Arno Garrels wrote:
> Arno Garrels wrote:
>
>> Back to the keyboard then. I think a found a way everybody can live
>> with. Will commit this new attempt to the IPv6 branch when I think
>> it's alpha-ready. Then we are able to continue the discussion based
>> on an existing implementation.
>
> Don
Francois PIETTE wrote:
>>> Probably breaking changes could be iontroduced the day ICS stops
>>> supporting
>>> non unicode compiler.
>>> Probably ICS-V8 could be that one, maybe to be released at the same
>>> time as
>>> Delphi crossplatfom, abandonning support for most of old Delphi
>>> version. I
Arno Garrels wrote:
> Back to the keyboard then. I think a found a way everybody can live
> with. Will commit this new attempt to the IPv6 branch when I think
> it's alpha-ready. Then we are able to continue the discussion based
> on an existing implementation.
Done, IPv6 branch updated (new mult
>Probably breaking changes could be iontroduced the day ICS stops
>supporting
non unicode compiler.
Probably ICS-V8 could be that one, maybe to be released at the same time
as
Delphi crossplatfom, abandonning support for most of old Delphi version.
I'm
thinking about letting ICS-V7 live for D7
>Probably breaking changes could be iontroduced the day ICS stops supporting
>non unicode compiler.
>Probably ICS-V8 could be that one, maybe to be released at the same time as
>Delphi crossplatfom, abandonning support for most of old Delphi version. I'm
>thinking about letting ICS-V7 live for D
Francois PIETTE wrote:
> In my option a real ICS multi-listening server should handle all
> client objects in one list. These client objects should be aware
> of what listening socket accepted them.
That is a good idea.
> This is not possible to achive
> with cu
In my option a real ICS multi-listening server should handle all
client objects in one list. These client objects should be aware of
what listening socket accepted them.
That is a good idea.
This is not possible to achive
with current TWSocketServer design.
I wouldn't be so sure.
In the me
Arno Garrels wrote:
> Francois PIETTE wrote:
>>> In my option a real ICS multi-listening server should handle all
>>> client objects in one list. These client objects should be aware of
>>> what listening socket accepted them.
>>
>> That is a good idea.
>>
>>> This is not possible to achive
>>> w
Francois PIETTE wrote:
>> In my option a real ICS multi-listening server should handle all
>> client objects in one list. These client objects should be aware of
>> what listening socket accepted them.
>
> That is a good idea.
>
>> This is not possible to achive
>> with current TWSocketServer des
Hello!
>> Now let's assume that application listens on two ip:port pairs, each for
>> different kind of communication. For example, 192.168.1.1:2048 and
>> 192.168.1.1:27015. Also, let's assume that user can define on which
>> ip:port
>> one of servers should listen (another ip:port pair would be
g ICS-V7 live for D7-D2010 and have ICS-V8 for
Delphi-XE and the next one.
Just ideas right now.
--
francois.pie...@overbyte.be
http://www.overbyte.be
- Original Message -
From: "Arno Garrels"
To: "ICS support mailing"
Sent: Saturday, November 27, 2010 6:32 PM
stening hack should be removed from the
IPv6 branche as well for the same reason).
--
Arno Garrels
>
> --
> francois.pie...@overbyte.be
> http://www.overbyte.be
>
> - Original Message -
> From: "Arno Garrels"
> To: "ICS support
ember 27, 2010 4:58 PM
Subject: Re: [twsocket] TWSocketServer:
howtomakeitlisteningtoseveralIP:Port?
Francois PIETTE wrote:
There is, for instance, property SslEnable in TWSocketServer
descendant TSslWSocketServer that is propagated to clients.
Let's say you want two listeners /192.168.1.1
Francois PIETTE wrote:
>> There is, for instance, property SslEnable in TWSocketServer
>> descendant TSslWSocketServer that is propagated to clients.
>> Let's say you want two listeners /192.168.1.1:80/192.168.1.1:443
>> one SSL and one plain text. Then you have to set SslEnable
>> property at run
There is, for instance, property SslEnable in TWSocketServer descendant
TSslWSocketServer that is propagated to clients.
Let's say you want two listeners /192.168.1.1:80/192.168.1.1:443
one SSL and one plain text. Then you have to set SslEnable
property at run time.
Maybe not. Look at TStatusBar
Francois PIETTE wrote:
> About event handler:
> We have the choice to enforce all are in sync or not. I'm not sure
> yet what is best. At least it is easy to propagate all event handlers
> to all component whichever subcomponent is used to assign the new
> event handler. It is also very easy to ha
essage -
From: "Arno Garrels"
To: "ICS support mailing"
Sent: Saturday, November 27, 2010 12:01 PM
Subject: Re: [twsocket] TWSocketServer: how to make
itlisteningtoseveralIP:Port ?
Francois PIETTE wrote:
This design would not break any existing code and would ease using
Francois PIETTE wrote:
>>> This design would not break any existing code and would ease using
>>> the new multiple listen easy to implement in higher level
>>> components.
>
>> It won't break existing code, but remains a hack IMO.
>
> I don't agree with you. Please explain.
> The main instance
Since the Addr property is a string, the component could easily handle
any
special format in that field to support multiple listening IP:Port
(Interface to listen to and port to use on that interface). I think
something like "/192.168.1.1:80/0.0.0.0:81/". IPv4 or IPv6 could be used.
The component
Hello!
> Hello all,
> Since the Addr property is a string, the component could easily handle any
> special format in that field to support multiple listening IP:Port
> (Interface to listen to and port to use on that interface). I think
> something like "/192.168.1.1:80/0.0.0.0:81/". IPv4 or IPv
This design would not break any existing code and would ease using
the new multiple listen easy to implement in higher level components.
It won't break existing code, but remains a hack IMO.
I don't agree with you. Please explain.
All event assignments and unassignments have to be kept in s
Francois PIETTE wrote:
> This design would not break any existing code and would ease using
> the new multiple listen easy to implement in higher level components.
It won't break existing code, but remains a hack IMO.
All event assignments and unassignments have to be kept in sync.
Also I would n
> Otherwise forcing IIS to allocate even only one IP is impossible.
It is quite possible, my public server uses IIS/7 and an ICS web
application on different IPs. There are NETSH HTTP IPLISTEN commands
that force IIS to listen only on specific IPs, or just change some
registry settings.
My app
On Fri, Nov 26, 2010 at 4:28 PM, Angus Robertson - Magenta Systems Ltd <
an...@magsys.co.uk> wrote:
> > I do not see any need for multiple listening except 0.0.0.0 and ::0
> > as I have seen none of the servers doing it.
>
> No commercial server listens on 0.0.0.0 since commercial servers all have
> I do not see any need for multiple listening except 0.0.0.0 and ::0
> as I have seen none of the servers doing it.
No commercial server listens on 0.0.0.0 since commercial servers all have
multiple IP addresses with multiple users and multiple applications, with
the exception of IIS that hogs al
Hello Francois,
Of course it will be a cool design but I do not see any need for multiple
listening except 0.0.0.0 and ::0 as I have seen none of the servers doing
it.
Regards,
SZ
On Fri, Nov 26, 2010 at 11:12 AM, Francois PIETTE wrote:
> Hello all,
>
> Since the Addr property is a string, th
Hello all,
Since the Addr property is a string, the component could easily handle any
special format in that field to support multiple listening IP:Port
(Interface to listen to and port to use on that interface). I think
something like "/192.168.1.1:80/0.0.0.0:81/". IPv4 or IPv6 could be used.
Dear arno.garr...@gmx.de,
I will be away on holiday from 27/7/2010 until 10/8/2010 and will be unable to
deal with your recent message regarding `Re: [twsocket] TWSocketServer
OnConnection event`.
For technical support enquiries please email supp...@ietgroup.com or telephone
01442 878777
Damien Wright wrote:
> I looked through the source and can see in the TriggerSessionAvailable
> handler the line If Error <> 0 then Exit;
>
> And this is done before the construction of a 'client socket' object
> with which to handle the connection and also prior to the point where
> the OnClien
Dear damienwri...@segurosoft.com,
I will be away on holiday from 27/7/2010 until 10/8/2010 and will be unable to
deal with your recent message regarding `Re: [twsocket] TWSocketServer
OnConnection event`.
For technical support enquiries please email supp...@ietgroup.com or telephone
01442
ling
Subject: Re: [twsocket] TWSocketServer OnConnection event
> I have been asked to investigate a strange issue we are encountering at
> a
> customer site in Mexico. I am a contractor for a company which supplied
> surveillance and monitoring software based on the ICS component set.
Dear francois.pie...@skynet.be,
I will be away on holiday from 27/7/2010 until 10/8/2010 and will be unable to
deal with your recent message regarding `Re: [twsocket] TWSocketServer
OnConnection event`.
For technical support enquiries please email supp...@ietgroup.com or telephone
01442
I have been asked to investigate a strange issue we are encountering at
a
customer site in Mexico. I am a contractor for a company which supplied
surveillance and monitoring software based on the ICS component set. The
software runs fine on other sites with no problems encountered for over 8
mo
Dear arno.garr...@gmx.de,
I will be away on holiday from 27/7/2010 until 10/8/2010 and will be unable to
deal with your recent message regarding `Re: [twsocket] TWSocketServer
OnConnection event`.
For technical support enquiries please email supp...@ietgroup.com or telephone
01442 878777
Hello,
Damien Wright wrote:
> and on each occasion if I run NetStat on the server it appears a
> windows socket object is left in FIN-WAIT 1 or FIN-WAIT2 state.
> Eventually the system fails as all windows socket objects are
> expended and there is a catastrophic failure of the software and/or
>
Dear damienwri...@segurosoft.com,
I will be away on holiday from 27/7/2010 until 10/8/2010 and will be unable to
deal with your recent message regarding `[twsocket] TWSocketServer OnConnection
event`.
For technical support enquiries please email supp...@ietgroup.com or telephone
01442 878777
Dear All,
I have been asked to investigate a strange issue we are encountering at a
customer site in Mexico. I am a contractor for a company which supplied
surveillance and monitoring software based on the ICS component set. The
software runs fine on other sites with no problems encountered for
> I would like to know how to detect a client's broken link in an
> TWsocketserver application. Not a closed connection but really a
> broken one.
An idle TCP connection does not send any data, so you will not know it's
broken until it times out failing to send data.
You can enable keep alive
Hi,
I would like to know how to detect a client's broken link in an
TWsocketserver application. Not a closed connection but really a broken one.
For exemple the BrokenLink procedure below doesn't add anything in the
Tlistbox1 when the connection is down.
**
**
TMyClient = class(TWSocketClient)
robertoschler wrote:
> I have a server socket application that uses TWSocketServer. When
> clients disconnect, I do get see a SessionClosed event triggered for
> the client socket and then the TWSocketServer ClientDisconnect event
> handler fires. However, the ClientCount does not go down, and ke
I have a server socket application that uses TWSocketServer. When clients
disconnect, I do get see a SessionClosed event triggered for the client socket
and then the TWSocketServer ClientDisconnect event handler fires. However, the
ClientCount does not go down, and keeps incrementing with eve
> I have a TWSocketServer in my main form.
> What value should I give to the Multithreaded property ?
FALSE.
You use TRUE when the component is used within a workerthread. Dropping the
component make it works in the main thread.
--
francois.pie...@overbyte.be
Author of ICS (Internet Component Sui
I have a TWSocketServer in my main form.
What value should I give to the Multithreaded property ?
TIA,
Engi
--
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
> We have all of this (uses ics6, win server 2003, 2CPU XEON 3.2GHz,
> 4Gb RAM, 1Gb network). Seems like it's not an issue and there is
> something wrong with our server implementation (based on ics
> twsocketserver).
If you have a set-up that can easily generate 5,000 client sessions, it
might
We have all of this (uses ics6, win server 2003, 2CPU XEON 3.2GHz, 4Gb RAM, 1Gb
network). Seems like it's not an issue and there is something wrong with our
server implementation (based on ics twsocketserver).
I've asked for an advise on ics programmer who could help us in the neighbor
message.
> We need 5000+ clients stable work.
You need Windows /SERVER/ operating system.
You need 4GB of RAM (even if there is free memory).
You need to use ICS-V6.
You need to carefully design you application because you'll reach many
Windows limits (there is a 1 handles per process limit).
Contribu
Hello Alexander,
the only limit is the OS and available RAM. This is winsock issue not
ICS. You need 10 KB non-paged RAM per socket. Non paged RAM can grow in
OS until maximum 1/8 of fisical RAM.
Note that other programs also can use non paged memory. that is each
program that uses overlapped IO
We need 5000+ clients stable work.
Angus Robertson - Magenta Systems Ltd <[EMAIL PROTECTED]> wrote: > How many
client connections can produce as maximum TWSocketServer
> at the same time? (Every client will be sending ~2Kb every 3-5sec.
> Server will be rarely sending 1Kb broadcast to all clie
> How many client connections can produce as maximum TWSocketServer
> at the same time? (Every client will be sending ~2Kb every 3-5sec.
> Server will be rarely sending 1Kb broadcast to all clients.)
Hundreds of connections, PC OS and memory dependent. I ran a test last
week on XP with 250 cli
How many client connections can produce as maximum TWSocketServer at the same
time? (Every client will be sending ~2Kb every 3-5sec. Server will be rarely
sending 1Kb broadcast to all clients.)
Thanks.
-
Never miss a thing. Make Yahoo your homepage.
--
mpeting with the
socket communication. How's that for an endorsement :)
Thanks to all of you who offered help and suggestions.
Cheers!
-dZ.
>--- Original Message ---
>From: Hoby Smith[mailto:[EMAIL PROTECTED]
>Sent: 12/5/2007 12:44:57 PM
>To
TECTED] On
Behalf Of DZ-Jay
Sent: Thursday, November 29, 2007 4:52 AM
To: ICS support mailing
Subject: Re: [twsocket] TWSocketServer and backlog
Wait, I'm sorry, I perhaps did not explain correctly: It was taking 5
to 7 minutes for the server to *process* the client's request to
compl
On Nov 29, 2007, at 14:20, Arno Garrels wrote:
> Hard to tell, a good compromise is using TWSocketServer given
> any lengthy task is run in worker threads. I think separating
> socket IO work from other tasks by using worker threads for those
> tasks considered "lengthy" is the way to go. The def
ot; is the way to go. The definition of
"lengthy" however is another story then.
--
Arno Garrels
>-dZ.
>
>> Sent: 11/29/2007 1:52:38 PM
>> To : twsocket@elists.org
>> Cc :
>> Subject : RE: Re: [twsocket] TWSocketServer and backlog
>>
&g
that I don't
have to redesign it right now.
-dZ.
>Sent: 11/29/2007 1:52:38 PM
>To : twsocket@elists.org
>Cc :
>Subject : RE: Re: [twsocket] TWSocketServer and backlog
>
>DZ-Jay wrote:
> On Nov 29, 2007, at 06:10, Wilfried Mestdagh wrote:
>
>&g
DZ-Jay wrote:
> On Nov 29, 2007, at 06:10, Wilfried Mestdagh wrote:
>
>> Hello DZ-Jay,
>>
>> So conclusion is that increasing the backlog does:
>>- decrease the performance for accepting connections
>>- decrease the overall performance of the application
>
> This seems to be the conclusi
On Nov 29, 2007, at 06:10, Wilfried Mestdagh wrote:
> Hello DZ-Jay,
>
> So conclusion is that increasing the backlog does:
>- decrease the performance for accepting connections
>- decrease the overall performance of the application
This seems to be the conclusion of mine and Huby's tests
Hello DZ-Jay,
So conclusion is that increasing the backlog does:
- decrease the performance for accepting connections
- decrease the overall performance of the application
Also:
- connecting clients should have a range of retry's when refused,
eventually with a random small delay.
For yo
Wait, I'm sorry, I perhaps did not explain correctly: It was taking 5
to 7 minutes for the server to *process* the client's request to
completion, not the connection. My tests, although quick and dirty,
are intended to check the behaviour of my application as a whole, not
just the connection.
1 - 100 of 169 matches
Mail list logo
