Bernard Normier

Unfortunately my attempted fix did not change anything: ``` Compiling [macosx-shared] src/IceBox/Service.cpp Compiling ../slice/Glacier2/PermissionsVerifier.ice /bin/sh: src/IceBox/generated/../Ice/BuiltinSequences.ice.d: No such file or directory Compiling ../slice/Glacier2/Metrics.ice Compiling ../slice/Glacier2/SSLInfo.ice Compiling ../slice/Glacier2/../Ice/BuiltinSequences.ice Compiling ../slice/Glacier2/Router.ice /bin/sh:...

For this use-case, you would typically use "bi-dir" connections for the calls to the `ActivityListener`. That is, you'd reuse the connection that the client opened to the server and not...

> As a developer of the server, I would prefer not to depend on the correctness of the client's configuration - I would like the notifications to be correctly ordered...

The only way to guarantee serialized dispatches in your client without proper coding / configuration in your client is for your server to make two-way invocations one after the other....

> I wouldn't characterize it as "easily achievable". As I said before, we have many places where the logic described in this issue needs to be implemented, and you have...

The most elegant solution here would be to provide clean APIs to these third-parties - APIs that don't depend on the RPC (Ice) layer. Then you can describe the semantics...

The updates to the IceRpc.Protobuf.Tools files are bogus. It's not immediately clear how to do it properly.

Yes, go ahead!

This is not a bug. The URI spec defines all these terms. See for example https://en.wikipedia.org/wiki/Percent-encoding.

> Per my reading of the spec these characters are not valid in a fragment: "#" / "[" / "]". I believe these characters are valid in fragments. In particular,...