Progress: Additional Help

Some helpful e-mails have come through from various people, giving me a few more options to consider.

Correspondence with Zero Linden, creator of Silo, has proven fruitful. The first issue to overcome was debugging...Silo was not passing the tests set to it by the python program included with the download. The issue was actually in the formatting of the url, which is highly dependent on your apache server configuration. Silo has now passed all tests and has created the data folders that it needs to communicate with SL.

Zero Linden was also kind enough to provide me with a smaller, more efficient script to relay chat data to Silo from SL. Effectively, all it does is send everything it hears to Silo, with each message overwriting the last. That should be fine, since I want the data to be passed along to Max/MSP as soon as it hits Silo. Here's the new script:

default {
state_entry() { llListen(0, "", NULL_KEY, ""); }
listen(integer ch, string name, key id, string what) {
llHTTPRequest("http://some-url/chat", [ HTTP_METHOD, "PUT" ] , what);
}
}

Though, I'm still having issues getting everything working start to finish. Zero clarified for me in another e-mail that LSL scripts run on SL's side of the internet pond, not on my machine, so Silo MUST be installed on a remote server. This is where Stetson's IT department comes in.

Through several exchanges with IT, it's been determined that it'll be far easier if I just go meet with them and explain exactly what it is I'm doing. They claim that there is a problem with the Silo code and that they're getting several different errors. I have an appointment to meet with them today, so we'll see how it goes. Hopefully this will remove the last roadblock on this path!

- M