On Thu, 23 Dec 1999, Alex wrote:
>> >A better sequence would have been \n!\r!(...) which can't be spoofed by
>> >input.
>> It's still spoofable in notes and such.
>>
>> Hi
>> !(...)
>>
>> That's "Hi\r\n!(...)" to the client.
>And dak's was '\n!\r!(...)'. Note the *two* '!' marks in there. Don't
>feel bad, I missed it the first time.
Oops, yes, I apologize. I don't know anything that could make that
sequence, although wouldn't it break telnet specs if used on a
non-accepting client? \n preceded by a \r, I mean.
>However, the entire design of the protocol is weak, regardless. Last I
>checked, you had to define a hard path to the sound in question, rather
>than a 'class' of sound (or whatever), which immediately cuts out some
>machines. Ick.
Yes, I noticed that in the lines I've seen.
"c:\music\beep.wav" isn't very portable I'd say.[1]
Having the sound types like you'll find under the Windows Control Panel for
Sounds would work much better than filenames.
--
George Greer | Shirak's CircleMUD for Windows help
greerga@circlemud.org | http://shirak.circlemud.net/
1. Although under Linux I'd just make a file called c:\\music\\beep.wav :)
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST