The README included with FMud seems pretty straight forward. You need to run the flashpolicyd.py daemon script to serve up your socket policy file. It has a default port of like 843, but you can choose a different one if you want, just remember to update it in the flash parameters you set in your HTML file. If you're on a MUD host that restricts the number of ports you can tie up, that may or may not be an issue.
Otherwise, just follow the directions, update the necessary configuration settings, and it should work fine.
According to the FMud README, you can use the default or use any above 1024 and then tell the SWF what you picked in the options list.
This article talks about using non-privileged ports: http://www.adobe.com/devnet/flashplayer/.... The way I understand this is that you can allow the flash to use an alternate port, but it will consider 843 to be authoritative. My guess is this means that if two people are running socket policies off the same machine, one on 843 and one on another port, you might run into some problems, but take that with a grain of salt since I don't work with Flash at all.
A year or two ago I read the Adobe spec as being favorable to non-priv custom port specification. I never got custom ports to work with FMud and all I saw online were people bitching about the same thing with their apps. I'd like to know, aside from the doc, if anyone actually got that going, and specifically if FMud is known to support non-priv custom ports.
That would be reason enough to go back to giving it another day in court.
I'd like to know, aside from the doc, if anyone actually got that going, and specifically if FMud is known to support non-priv custom ports.
Yes, you can specify a custom port for the policy file with FMud, although this wasn't always the case so that may be where the confusion is.
The way I understand this is that you can allow the flash to use an alternate port, but it will consider 843 to be authoritative.
That's pretty much my understanding too, although the policy file on 843 may need to include the master policy file directive in order to override any other policy file and you can only specify a master policy on port 843.
09 Apr, 2010, boblinski wrote in the 10th comment:
Are there any alternatives to FMud?
My friend that hosts my forums just got back to me and said we cannot use FMud for the following reasons:
1. One way of setting it up requires python 2.5, and our webhost runs python 2.4.3, making it incompatible with the socket policy server written in python.
2. I attempted to side-step this issue by using a socket policy server written in perl, only to find out that our webhost blocks all ports but the ones that are necessary for the cPanel, webmail, and HTTP. This is for security reasons. To get around this, I would have to purchase a dedicated IP from them, and then specifically request the port I want to be opened.
Anything with Flash is going to require a policy file, so you'll probably want to look at something using Java or websockets. Incidentally, if your host doesn't allow you to use any ports other than cpanel, webmail and http, how do you host the mud?
Edit: Rereading your post, if your mud is on a different host to your website/forums, it's the mud host that needs to serve the policy file and not the web host where the client itself is hosted.
10 Apr, 2010, Asylumius wrote in the 14th comment:
You said your MUD is hosted with isunlimited.net, so that's where your policy file needs to be.
I would imagine you have SSH / shell access to isunlimited.net and that is how you actually boot your MUD up. You'll have to check with them about Python versions and whatnot, and possibly ask for permission to run a process on another port (if you were allowed one to begin wtih).