Thank you so much to give me a path forward !
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!!!
Thank you very much for your help, let me solve the problem
Many thanks - "working" (fast action - like in old times :-) ).
just a small copy/paste issue I think:
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
Thanks for reporting the issue, we have pushed the fix to the datastorm repository.
This exception indicates that your client is trying to talk to an Ice 3.4 server using the 1.1 encoding, the 1.1 encoding is supported with Ice 3.5 or later.
If you cannot upgrade your server to a more recent Ice version you will have to use the 1.0 encoding, see https://doc.zeroc.com/technical-articles/general-topics/encoding-version-1-1#EncodingVersion1.1-InteroperabilitywithIce3.4andearlierreleases
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.
Success, thanks for the help!