Re: [CF:1317] client 0.95 dies with "Got error on read", other probs

[Jan Echternach <echter@informatik.uni-rostock.de>]

On Mon, Jun 19, 2000 at 11:23:13AM -0500, Frank McKenney wrote:
>  1) Major:  Frequently but intermittly both client and server die.
>     This mostly (but not always) occurs when switching maps.  cfclient
>     exits from its main loop follwing DoClient() with the message "Got
>     error on read (error k), exiting.", where 'k' is usually 0 (but was
>     11/EAGAIN on one occasion).

I can confirm this.  One reason is that the server died and the client
doesn't handle this condition gracefully.

The other reason is a genuine bug in the client:  EAGAIN is not handled.

>  2) Serious:  Performance is noticeably worse than 0.93.x.  Movement is
>     sluggish, then "bursty", so it is very difficult to react properly
>     to on-screen events.  I'm talking about the kind of jerky

I only see this when the network connection is slow (or even has packet
loss).  Not a problem of crossfire IMHO.

>  3) Serious:  On several occasions my character would get "stuck" and
>     only move north or northeast.  There are any number of places where
>     this is Not A Good Thing, leading to death or starvation.

I think there are two reasons for this:

a)  You've released the key, but the server doesn't know yet that you
have released the key because of network lag.

b)  I think it's possible that you get stuck in the "run" mode.  This
would be a bug in client or server.

>  4) Minor:  The old "single invocation" feature(?)  seems to be gone.

Yes, client and server are now seperated.

-- 
Jan