Best Of

Hi Sergio,

We don't have any JavaScript demos for this but it should work, the JavaScript generated code for IceGrid service is provided with our JavaScript distribution. You will have to configure IceGrid to listen on a WebSocket endpoint or set up a WebSocket proxy that forwards the connections to IceGrid.

Cheers,
Jose

Thanks much xdm!!! In fact I was looking at the ant-ice code too, but could not figure it out. Your first option works (adding to the ice file). I will also try your second option for completeness. Again Thanks much!!!

Many thanks - "working" (fast action - like in old times :-) ).

just a small copy/paste issue I think:
In demos/cpp/make/Make.rules
DATASTORM_HOME ?= /opt/DataStorm-3.7.0
should be changed to
DATASTORM_HOME ?= /opt/DataStorm-0.2.0
for bare consistency with the version number

sent pull request

Cheers
Manfred

Hi,

Thanks for reporting the issue, we have pushed the fix to the datastorm repository.

Cheers,
Jose

With Glacier2, you don't necessarily need to go through the backend server for Ice invocations. Your JavaScript client could directly invoke the Game instance server by going through Glacier2 without having to go through the backend server. Glacier2 will only listen on a single port so this means you would have to expose only two ports to clients: the Glacier2 port and the backend server port.

It's hard to provide specific advice without knowing more about your architecture. In general, using Glacier2 will be simpler when a client has to communicate with multiple servers: it creates a session with Glacier2 and invocations from the clients will be routed to the different servers deployed behind Glacier2 by the Glacier2 router.

Using bi-dir directly is fine as well for simple client-server communications. It gets more complicated if the client has to talk to multiple servers as you will need to implement some kind of routing for requests if you want the client to only connect to a single server instance.