The question: What are the limitations on filenames when recording a stream to FMS2?
The answer:
I used to know where this was documented but can't find it anymore. I'll keep looking. Until then, my opinion has always been that the file name has to be URL safe. So no weird characters like question marks or colons etc. I thought I had heard a while back to not start a stream name with a number so I always start mine with a character, usually "stream_" or "userstream_", or word.
I'll look around a bit for a better answer but either way you can't go wrong with the above.
Keep in mind that Windows machines are case insensitive and Unix machines are. It's a good practice to make all your stream names lower case so you don't need to worry about that later if you ever move from Windows to Unix.
Well, another hour or so and I'll be taking our crappy transit system to Vancouver to go hang out with the AIR guys. It was supposed to get really really hot today so I had been debating on whether I really wanted to go or not without a nice air (har har) conditioned car but it looks like the high of 37 celsius won't be reached, which is good. I would drive down there but the seminar is right at rush hour.. and that in itself would suck.
So! I'll update with whatever tidbits I get when I make it back. Should be fun.
Something quick, fast and easy here. Almost falls in line with the RTFM mantra actually. But I'm not one to just say that, so here's some direction hopefully.
The question: How can I get (in the server side, main.asc) the IP of client requesting connect?
The answer:
There's a property of the client object called "ip". Grab that.
Here's a direct link to the docs actually. But here's the code copied and pasted from there:
application.onConnect = function(newClient, name){
if (newClient.ip == "127.0.0.1"){
// Insert code here.
} else {
// Insert code here.
}
};