__color__ __group__ ticket summary component version type owner status created _changetime _description _reporter 1 Release 1 It goes pop client defect somebody new 2006-04-03T11:20:41+0100 2006-04-04T22:21:31+0100 "If you feed marvin a long command, the server keels over: ** Welcome to Marvin Version 0.01 =| This is the completly alpha test version *->................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. warning unknown type 8 in message_send(1)--> EOF, say bye bye S-Lang says: So long, and thanks for all the fish... silver>MARVIN_SLANG_PATH=~arthur/work/marvin ~arthur/marvin localhost 5000 Connection to 'localhost' failed: Connection refused Bummer. " rohan@… 3 Release 2 Tab completion does files client defect somebody new 2006-04-03T11:26:12+0100 2006-04-03T11:26:12+0100 Tab completion works, but on files in your pwd. Of course it should work on users instead. It not working at all would be better though. dez@… 3 Release 6 spidermonkey server enhancement somebody new 2006-05-15T16:08:15+0100 2006-05-15T16:08:15+0100 "Look at replacing the (broken) cslang language library with spidermonkey (javascript) it looks pretty flexible, and the language may be more familiar to people. http://www.mozilla.org/js/spidermonkey/" arthur 3 Release 7 jscript xml server enhancement somebody new 2007-03-13T11:19:09Z 2007-03-13T11:19:09Z "The [http://www.whitebeam.org/library/guide/TechNotes/xmlproc.rhtm WhiteBeam] project has an XML DOC extention to spidermonket, steal it. This way we can hande the raw ipc message contents straight into/outof the script engine, and let a layer of jscript handle with bundling up. " arthur 4 Release 3 "Short commands don't work and all unrecognised commands get ""spoken""" client enhancement somebody new 2006-04-03T12:59:44+0100 2006-04-04T21:25:29+0100 "The short versions of commands (e.g. .e for .emote) don't work and any command thats not recognised gets spoken rather than returning an error message. " rohan@… 4 Release 4 Implement multi-streaming in SCTP branch server task firefury assigned 2006-04-03T21:30:16+0100 2006-04-03T21:30:36+0100 "The XML conversations are currently assigned a unique ID to allow multiple conversations to take place at once. This should be implemented using SCTP multi-streaming. Have to work out how to allocate streams to message IDs. Are message IDs 1-shot or can they be persistent? If they aren't persistent (or maybe even if they are?) we could just do: stream = msgid % available_streams Clearly we still need to leave the real message ID in the message. Need to check that events (such as ) from the server get assigned a consistent message ID - these messages need to go into a single stream so they are guaranteed to arrive in-order. There is some preamble on current messages too which we should deal with for SCTP: - Command (can be ""CMD"", ""RPY"" or ""ERR"") - We need to parse this so we know what slang functions to execute. Although IMHO it'd be nicer to include this in the XML. Maybe the whole XML message can be wrapped in """", """" and """" tags. Another possibility is to add a msgtype=""cmd"", msgtype=""rpy"" or msgtype=""err"" to the root element of the XML. - Expected message size - we don't need this at all under SCTP since it's a datagram protocol and we're guaranteed to get the whole buffer in a single read." firefury