Le 07/06/2013 09:52, Ron a écrit :
> I just checked, gambas2 didn't/doesn't respect timeout either in this
> case when a hiost cannot be reached.
> And reports after 2+ minutes.
> So it was always like this, maybe because of the fact that it was
> difficult to implement?
>
> Regards,
> Ron.
>
I ha
I just checked, gambas2 didn't/doesn't respect timeout either in this
case when a hiost cannot be reached.
And reports after 2+ minutes.
So it was always like this, maybe because of the fact that it was
difficult to implement?
Regards,
Ron.
> Thanks.
> The blocking mode issue is not that bad, s
Thanks.
The blocking mode issue is not that bad, since I always want to use
non-blocking mode anyway, my project is too big to be interupted by sockets.
About the timeout I thought gambas2 did this correctly, but I'm not sure
now, since the ClientSocket example uses a timer to remove Socket if i
Hmmm... well I've taken a quick glance at the source and the
documentation (Shock news! Developer looks at documentation!!!) and it
looks like it's less simple than we thought.
When making a connection, it seems as if Gambas insists on using
Blocking mode True internally, there is no storage or
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
Regard
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
Le 03/06/2013 09:39, Caveat a écrit :
> Strangely enough, I had a similar problem with sockets in python.
> Turned out that the problem was caused by setting the timeout value on a
> socket, *then* setting the blocking mode. It seems as if the underlying
> socket 'loses' the timeout value (I actua
Strangely enough, I had a similar problem with sockets in python.
Turned out that the problem was caused by setting the timeout value on a
socket, *then* setting the blocking mode. It seems as if the underlying
socket 'loses' the timeout value (I actually discovered it when creating
a help fu
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
propert
Le 01/06/2013 10:33, Ron a écrit :
> Benoit,
>
> It seems to be a Gambas3 thing all along... not latest revisions...
> but I didn't see this until I specified a wrong IP address to connect
> too in my project.
> Also on the Raspberry Pi I saw this earlier, thinking... man that's a
> slow device, no
Benoit,
It seems to be a Gambas3 thing all along... not latest revisions...
but I didn't see this until I specified a wrong IP address to connect
too in my project.
Also on the Raspberry Pi I saw this earlier, thinking... man that's a
slow device, now I know Gambas socket blocks everything when a
Le 30/05/2013 20:56, Ron a écrit :
> Strange i updated two machines and they both hang at startup trying to
> connect to a tcp socket.
> Will downgrade tomorrow and try to isolate it.
>
> Regards,
> Ron_2nd
Do you have the old revision number before the hang?
--
Benoît Minisini
Strange i updated two machines and they both hang at startup trying to
connect to a tcp socket.
Will downgrade tomorrow and try to isolate it.
Regards,
Ron_2nd
Op 30 mei 2013 20:45 schreef "Benoît Minisini"
het volgende:
> Le 30/05/2013 20:08, Ron a écrit :
> > Did something change in the latest
Le 30/05/2013 20:08, Ron a écrit :
> Did something change in the latest 10 revisions trunk regarding socket
> connects?
>
> I upgraded my Gambas3 to latest rev, and now my project hangs when starting.
>
> this is the first part of the gdb bt:
> 0x7fffc6ffe000
> 0x7f8a61c0dfdd in connect () at
14 matches
Mail list logo
