2010 19:35
Til: ICS support mailing
Emne: Re: [twsocket] TSslWSocket in a non-blocking multithreaded server
Eric-Lionel Rault wrote:
> -> As far as I can interpret the log, the session is closed due to
> winsock error 10053 ?
> ->"WSAECONNABORTED
> ->10053
> ->Softwar
Eric-Lionel Rault wrote:
> -> As far as I can interpret the log, the session is closed due to
> winsock error 10053 ?
> ->"WSAECONNABORTED
> ->10053
> ->Software caused connection abort.
>
> I've frequently observed this situation when communicating with Wifi
> equipments which are some times out
-> As far as I can interpret the log, the session is closed due to winsock
error 10053 ?
->"WSAECONNABORTED
->10053
->Software caused connection abort.
I've frequently observed this situation when communicating with Wifi
equipments which are some times out of range.
When receiving this mes
Kurt,
> I have been testing with ICSlogger attached in my client app, as you
> recommended, and have listed the results below.
> As far as I can interpret the log, the session is closed due to
> winsock error 10053 ?
> In my server application I am logging all failed connection attempts
> e.g.
Garrels
Sendt: 1. september 2010 14:51
Til: ICS support mailing
Emne: Re: [twsocket] TSslWSocket in a non-blocking multithreaded server
Kurt Andersen wrote:
> On a side note, I have been hammering away on my Server app using a
> (homemade) multithreaded SSL client, and sometimes
> I ge
11:31
> Til: ICS support mailing
> Emne: Re: [twsocket] TSslWSocket in a non-blocking multithreaded
> server
>
> Kurt Andersen wrote:
>
>> I have now implemented a working multithreaded test (server)
>> application which uses both the TWSocket and the TSslWSock
Kurt Andersen wrote:
> But as far as I understand Arno, he would recommend not going
> multithreaded unless absolutely necessary
> e.g. lengthy operation which blocks socket I/O.
Yes, I prefer this, it's easier to write and to debug
unless there's no need to utililize multiple CPUs for the
sock
wsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] På vegne
af Fastream Technologies
Sendt: 1. september 2010 11:37
Til: ICS support mailing
Emne: Re: [twsocket] TSslWSocket in a non-blocking multithreaded server
Hello,
AFAIU, you are suggesting multiple-clients/thread design. We have a sour
delig meddelelse-
Fra: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] På vegne
af Arno Garrels
Sendt: 1. september 2010 11:31
Til: ICS support mailing
Emne: Re: [twsocket] TSslWSocket in a non-blocking multithreaded server
Kurt Andersen wrote:
> I have now implemented a
Hello,
AFAIU, you are suggesting multiple-clients/thread design. We have a source
code example of that (C++) at,
http://www.fastream.com/webstresstester.php
HTH,
SZ
On Wed, Sep 1, 2010 at 12:30 PM, Arno Garrels wrote:
> Kurt Andersen wrote:
>
> > I have now implemented a working multithreade
Kurt Andersen wrote:
> I have now implemented a working multithreaded test (server)
> application which uses both the TWSocket and the TSslWSocket in a
> non-blocking manner.
Just a side note to your design "One Thread Per TWSocket Instance",
it's not optimal IMO. TWSocket objects allocate at lea
Hi Arno
Once again many thanks for the quick reply.
I have now implemented a working multithreaded test (server) application
which uses both the TWSocket and the TSslWSocket in a non-blocking
manner.
The "regular" WSocket is used to accept incoming sessions, which are
then carried on in a new c
Kurt,
At first read "How to use" comment in OverbyteIcsThrdLock.pas.
I would use TSslDynamicLock.
Next read:
http://www.openssl.org/docs/crypto/ERR_remove_state.html
In ICS it is function f_ERR_remove_state().
> How do we use the TSslWSocket in a similar manner with SSL enabled,
> though only wi
Hi
We have been using the TWSocket component in several non-blockling
multithreaded applications,
but now we would like to use the TSslWSocket in a similar manner.
Using the TWSocket we usually in the mainthread have:
...
TWSocket* ServerWSocket ...
...
MainThread::ServerWSock
14 matches
Mail list logo
