Deployment Question
I have a .jnlp file. It is a client te accesses a small mulit-player card game server (poker and gin rummy). It appears that I cannot put the client.jnlp on any random web server: it only works properly if it is issued to downloading clients from the same machine as that on which the game server is deployed. Is this normal, is there a way around this?
So:
10.0.10.194 - Web server (client.jnlp does not work)
10.0.10.196 - Game Server (client.jnlp works)
This current limitation causes some immediate future problems for my scenario:
1. I must run a small http server on my Game Server (10.0.0.196) which I don't really want to do to.
2. If I get many players at one time it is going to seriously degrade my Game Server bandwidth as the downloads occur. I really want to be able to load balance and put the client.jnlp on a number machines as my client demand increases. There must be a way.
Regards,
NC
[961 byte] By [
peelmana] at [2007-10-2 4:38:40]
The jnlp sandbox, just like the applet sandbox, only allows connections back to the host that the application was downloaded from. A feature was put in mustang to allow connections to any host, if the user agrees, but this would cause a popup dialog to the user that these game players wouldn't necessarily understand.
The app could be signed to allow all-permissions, but this is overkill for this type of application, where no other permissions is really needed, and the trust dialog would then also scare away most casual users.
The best solution is to handle the re-directorn on the server, so that one front-end server recieved all the requests and forwarded them to either the download server or the game server as appropriate, then as demand grew, and there was need for multiple download or game servers, the front-end server could load ballance as appropriate.
dnpa at 2007-7-16 0:11:47 >
Thank you for the detailed and informed answer, much appreciated. Any pointers at all where to begin for implementing your suggested solution - i.e. how to have a "front-end" server redirecting the requests.
Is it to be a small Java program doing the redirects, or a configured webserver, etc? I understand there may be many options, but for my case what would _you_ recommend?
Sorry for the stupid questions, I am new to this :)
--
Neil
