[Gambas-user] Connect hang with latest revision

[Ron]

I tried it,
without specifying .Blocking or .Timeout the _Error event is still
triggered after +2 minutes.

With specified .Timeout = 10 * 1000 (10secs) the same, after +2 minutes.

When specifying .Blocking (either True or False) you get this directly
when opening:
Error: Stream is closed


Regards,
Ron_2nd.


2013/6/3 Benoît Minisini <gambas at ...1...>:
> Le 02/06/2013 17:05, Ron a écrit :
>> Bug #1 and Bug #2 are fixed, thanks for that!
>>
>> The time it takes for Event_Error to trigger is still more than 2 minutes.
>> I see that in ClientSocket there is a 10sec timer running which cuts
>> the socket if still not connected.
>>
>> Is this the way it should be implemented, what about the TimeOut
>> property it seems it doesn't work?
>> Would be nice if users know after 10 secs that the socket is unable to
>> connect, +2 minutes is too long...
>>
>> Regards,
>> Ron.
>>
>
> Hi Ron,
>
> I have implemented what Caveat told in revision #5696: the timeout is
> reset each time the blocking mode changes internally.
>
> Can you try it and tell me if it changes anything for you?
>
> --
> Benoît Minisini
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Gambas-user mailing list
> Gambas-user at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gambas-user