|
Hi, I recently started playing with Unity 3.0 (the free edition), in particular i'm messing with one demo inside the "Procedural examples" package, Lightning Bolt (the C# code). I have a very simple library that does basic text communication with my public server (fixed IP) over Socket() on port 80 (it's a very simple HTTP/1.0 self-written server). It all works very well when deployed for PC or Mac, I can't say the same for the Web Player deployment, where, beside having a Socket Policy Server answering to 843/tcp, Socket communication just don't work. Monitoring using Wireshark shows that 843/tcp communication goes well till the end (connection gets closed after FIN), but then, the communication with my server stops here. Any clue?
(comments are locked)
|
Be the first one to answer this question
How do you offer the
cross-domain-policyWhat i've read is that on port 843 you just have to return the policy. There's no http on that port. Just if there's an incoming connection you have to return the policy, but I haven't used Sockets in Unity so far. Also your server is a standalone app, right? Listening sockets are not allowed in the webplayer. If you use port 80 and tcp, why don't you use the WWW class? +1 for using wireshark ;)