-
While it's fine for the ice or icerpc protocol implementations to depend on Slice1 or Slice2 I don't think the IceRPC core types should depend on Slice generated types.
This concerns all the types …
-
https://docs.testing.zeroc.com/icerpc/dispatch/incoming-request#request-features
I think it would be better to use an example without Slice services, the fact that the Slice-generated code takes a …
-
https://github.com/icerpc/icerpc-docs/blob/14df79f612976c1bd0684b40fe8f362e009f1e03/pages/docs/slice/language-reference/lexical-rules.md?plain=1#L89-L104
I think most of this section is incorrect.
-
### What happened?
Hi!
I am trying to make use of the **Markdoc language server** extension within VS Code to provide validation, autocomplete etc. Unfortunately, I can't seem to be able to get th…
-
Our current remote exceptions are “exception struct/class”, which works reasonably well for language with exception support. The application can define a bunch of exceptions (without inheritance for t…
-
I am writing a new example where a client slowly streams data to a server (a new element every 5 seconds).
After a while, the connection dies and the client Debug log shows me:
```
dbug: IceRpc.C…
-
Do we need to keep this generated exception? I don't see the point for this test is just like another exception.
https://github.com/icerpc/icerpc-csharp/blob/main/tests/IceRpc.Tests/ProtocolConnect…
-
It should be only on the home page, after Let's go!
-
This PR merge:
https://github.com/icerpc/icerpc-docs/pull/250
broke some callouts like:
https://docs.testing.zeroc.com/icerpc-for-ice-users/rpc-core/endpoint
It's apparently critical for the e…
-
The Slice link returns 404, We use (/slice) like in other places but It returns 404. I assume this is not transformed because the link is not in markdown but inside a component.
https://github.com/…