Don't know if this is a good idea. However this is optional, only if options.policyPort is set.
Maybe instead of server.handleSocket, policyfile could be used (however policyfile seems to grab all 'error' and 'data' events, so the current solution is a bit nicer)...
cleanup flashpolicy transport
add policyPort support and instantiate a policyfile server
The reason I didn't want to go with a policy server is that you would probably run it standalone, outside of engine.io, right?
Yeah, you're right...
i would lazy require this when the options.policyPort has been set.
Ok, sounds good. And remove "polifyfile" from the dependencies?
@guille then you shouldn't support the websocket-js library either as it depends on having a policy file server
lazy require policyfile
@3rd-Eden We have a policy file in lib/transports/
We're not doing this. If someone needs a policy server they should set up their own standalone, where they could also handle non-engine related Flash security policies.
We also added a policyPort option to engine.io-client to facilitate this.