Re: [htsserver-devel] D-0002.txt: Holsham Traders Server-Replies]

[Uwe H. <uh...@bi...>]

On Tue, Jan 11, 2000 at 02:22:18PM +0100, Sven M. Hallberg wrote:
> > 441 Maximum number of connections reached.
> > 442 New socket descriptor greater than FD_SETSIZE.
> > 200 Welcome to htsserver version 0.5.5
> > 451 Game is paused. Your input will be ignored.
> 
> What's the purpose of a pause command? The game can't be paused, if someone
> wants to leave the game, let him leave... It has no effect on his situation
> when he returns.

Yep, it can't be paused normally, at least not by players.
The admin-command 'pause' causes all input from any client to
be ignored, until the admin disables 'pause' again.
Don't know if it's useful at all, I just felt like implementing it :-)

 
> > 521 Your login-timeout has expired. Bye.
> 
> What's a login-timeout (in this case, of course). Sorry, I'm not up-to-date on
> the source...

If you are connected longer than 60 seconds and didn't login, you're
kicked.
 
> > 421 You must log in first.
> > 422 Player is not connected.
> > 423 Player doesn't exist.
> > 000 Chat message from XXXX: "foo bar ..."
> > 511 Syntax error.
> > 
> > 
> > The chat-message is an exception, here, because important information is
> > stored in the text-part, which is not a very good solution. I'm not
> > quite sure about how to make this better, at the moment...
> 
> Multi-line?

Hmm.. no. Multi-line sucks :-)

How about this:

chat [who] 144

and then 144 chars of text, just like in update-prices?


Chat isn't really a server-reply, so it doesn't need the reply-codes,
anyway.

Hmm.. reminds me that "type-of-reply"-group 0 (Information from server)
isn't really needed, too. Info from the server is sent as commands, not
as replies with reply-codes... Hm.. need to put some more thoughts into
this.
 
> > It will. The server must inform all affected clients of changing prices,
> > changing amount of goods etc.
> 
> The key word is _affected_.

?

 
> > Uaa... I don't like this. Either we make the maximum line length bigger,
> > and/or use 'transmit'. 
> 
> I don't like 'transmit' :)

OK. So let's make the line length bigger :-)


> I think a rather short limit on good names should be set. That forces readable
> names. What about 32 characters (including trailing newline of course, because
> 33 is not a buflen you want (real programmers appreciate their powers of
> two!)) ;^)

At the moment it's 20. We could change it to 32, but IMHO it's not
necessary.

I agree that they need to be relatively short, because of
readability-reasons and because the ncurses-client is limited to 80
chars/line normally, and we want to have a nice display for the
ncurses-client, too :-)
 

Uwe.
-- 
Uwe Hermann <uh...@bi...>
http://www.bingo-ev.de/~uh1763/index.html
-----------------------------------------
:wq