Re: Javascript/Java [Re: Interactive MOO]

• Date: Sat, 17 Aug 1996 23:02:37 PDT
• From:
  Ben Jackson <bjj@sequent.com>
• Cc: Antonio Martos <martos@las.es>, moo-cows@parc.xerox.com
• In-reply-to: Your message of "Fri, 16 Aug 96 14:37:26 PDT." <3214EA16.26A3@mail.datasys.net>

Michael Moore wrote:
> 
> It's even easier with version 1.8.0. This code segment will do the same thing
>  :
> 
> set_connection_option (player,"binary",1)
> notify (player,"~1B[32m"+text)
> set_connection_option (player,"binary",0)

Beware that toggling the "binary" connection option may have unexpected
side-effects on your input stream.  I found when I was experiementing with
code like this (and with read() instead of notify()) that the player's
input stream is either stripped of binary characters or converted to the
~XX binary representation *at the time it arrives*, not at the time it is
consumed.  If you leave the binary option on long enough for the server to
process some data from the player's socket, you may get some unexpected
results.  The MOO "API" doesn't specify (or even document) when this might
happen.  This may be an argument for "binary-input" and "binary-output"
connection options and/or better specification/documentation.

--Ben

• Re: Javascript/Java [Re: Interactive MOO]
• From: Michael Moore <mike@mail.datasys.net>

• Prev: Re: Javascript/Java [Re: Interactive MOO]
• Next: Lambda Cores
• Index: MOO-cows
• Thread: MOO-cows