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
> refresh the windows, but as I was watching Dortmund its the
> most likely cause.
>
> 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
> sending a command every now and then.
>
This kind of lock is highly possible, as sockets are in lock (sync) mode.
Maybe I/O operations will end by themselves after a while and give the hand
back to the user. A solution is to use threads, but some Tcl/Tk releases of
some Linux distributions have inhibited thread support. I will try to check
FICS documentation to understand what is going on.
Pascal
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Scid-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users
