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

[Sven M. H. <pe...@so...>]

On Tue, Jan 11, 2000 at 09:56:09PM +0100, Uwe Hermann wrote:
> 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 :-)

OK, then.


> > 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.

OK, then.


> > > 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 :-)

Why? I find multi-line replies to be a pretty clean thing.

> How about this:
> 
> chat [who] 144
> 
> and then 144 chars of text, just like in update-prices?

Don't like it... but that's me...

> 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.

Well, erm, grmpf... Don't like the thought of the server sending 'commands' to
the client... Because all the server is giving out is information, really. The
client is the only one actually commanding. It tells the server what to do.
I just think we should pick a very clean representation of the reality,
mirrored in the protocol. Just like to persons talking to each other. It might
work other ways, too; it's just a matter of which way is neatest.

Back to the point, consider this metaphor:
You are working for a company which sells sofas and a
customer calls you and says he wants to buy three orange sofas. You sell him
three orange sofas and order the delivery dude to deliver them. However, let's
say you have a colleage, who does the same job as you. You must inform him,
that there's three sofas less in stock than before. You'd probably not say
"Hey Joe, please decrease the number of orange sofas stored in your memory by
three." but rather "Yo, I sold another three of the orange sofas, dude.".

> > > It will. The server must inform all affected clients of changing prices,
> > > changing amount of goods etc.
> > 
> > The key word is _affected_.
> 
> ?

Not everyone is affected. Thought must be put into how many actually are.

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

How much?


> > 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.

Ok, just leave it at 20, that's fine with me.


greets,
Sven

-- 
Sven M. Hallberg <pe...@gm...>
PGP key available at http://www.sh-home.de/~sol
 [ KeyID........: 0x0F520CF9 ]
 [ Fingerprint..: 56 61 00 18 14 B4 01 01  06 90 D0 29 96 BD 58 6F ]
return 0;