Best Of
Re: DataStorm compilation issue on MacOS - NodeI.cpp:476:24: error: loop variable 's' of type ... create
Hi,
Thanks for reporting the issue, we have pushed the fix to the datastorm repository.
Cheers,
Jose

Re: ICE Connectivity (C# client to C++ server)
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

Re: Help To Integrate Ice Into A Complicated Architecture
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.

Re: How to upload a file through stream?

Ice 3.7.3 Released
We are pleased to announce the release of Ice 3.7.3. You can download binary distributions for your favorite platforms or fetch the complete source code from our GitHub repository.
Ice 3.7.3 offers full support for Swift on macOS and iOS, and adds support for Android 10, iOS 13, macOS Catalina, Red Hat Enterprise Linux 8, .NET Core 3.0 and more. Please refer to the Ice Release Notes and Changelog for details.
As always, we value your feedback. If you have any comments or suggestions, please post them here on the forum. Bug reports can be submitted on GitHub.
Best regards,
The ZeroC Team
Re: How to serialize named tuples (C#)?
Hi Mike,
Ice cannot directly send your named tuples, you have to use types defined in Slice, here you can probably use a couple of structs and sequences like in:
struct BenchmarkCount { long Data; // Send date as a long int Count; } sequence<BenchmarkCount> BenchmarkCountSeq; struct BenchmarkInfo { string Key; int Benchmark; BenchmarkCountSeq Counters; } sequence<BenchmarkInfo> BenchmarkInfoSeq;

Re: IceUtil::TimerTask::TimerTask() : Access violation reading location
I'm glad you get it working

Re: IceUtil::TimerTask::TimerTask() : Access violation reading location
Hi Jose,
Great news, it doesn't crash anymore !
Thanks to the settings /D_WIN32_WINNT=0x0601 and /DWINVER=0x0601 ... and big thanks to you !
I can continue now testing our app with the new ice 3.7 ...
Have a good day
Mehdi

Re: DataStorm compilation issue on MacOS - NodeI.cpp:476:24: error: loop variable 's' of type ... create
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