Pascal Georges wrote:
Hi!
> > Actually, I think that FICS is just closing the connection
>> > if it does not receive any input for a certain ammount of
>> > time.
>>
>> FICS closes connection inactive (with no input) for one hour.
So I remembered correctly. :)
>> > I
2008/7/17 Marcin Kasperski <[EMAIL PROTECTED]>:
> > Actually, I think that FICS is just closing the connection
> > if it does not receive any input for a certain ammount of
> > time.
>
> FICS closes connection inactive (with no input) for one hour.
>
> > I normally solve this by just sending a "."
> Actually, I think that FICS is just closing the connection
> if it does not receive any input for a certain ammount of
> time.
FICS closes connection inactive (with no input) for one hour.
> I normally solve this by just sending a "." from time to
> time
I used to send 'date' ;-)
--
> Actually, I think that FICS is just closing the connection
> if it does not receive any input for a certain ammount of
> time. I can't give you the pointer but it is AFAIK even
> documented somewhere. While this is no issue at all if you
> play on FICS it is a problem if you only observe a game,
Pascal Georges wrote:
Hi!
> Additionally, as it is likely that one is not doing
> anything while just observing a major turnament (ie.
> not sending commands to FICS as it is unnecessary)
> maybe it would be a good thing to be able to switch on
> a "keep alive", like just sen
2008/6/29 Alexander Wagner <[EMAIL PROTECTED]>:
> Hi!
>
> Could it be that the current code has a problem if FICS
> closes the connection? FICS does that after some "inactivity
> time" AFAIK automatically. I do not see whether this was the
> cause because scid locked up entirely and did not even
>
Hi!
Could it be that the current code has a problem if FICS
closes the connection? FICS does that after some "inactivity
time" AFAIK automatically. I do not see whether this was the
cause because scid locked up entirely and did not even
refresh the windows, but as I was watching Dortmund its the
m
