Skip to content

0.5.0

Compare
Choose a tag to compare
@jakaplan jakaplan released this 06 Apr 11:45
· 129 commits to main since this release
e359311

This release contains a major new capability - sending multiple replies from the server for the same request.

New functionality

  • Routes can now use sequential replies. On the server, a handler registered for a route with a sequential reply is passed a SequentialResultProvider with which it can send arbitrarily many responses to the client. On the client side these are exposed as an AsyncThrowingStream (or for the closure-based version as a callback provided SequentialResults).
    • The server side implementation can choose to finish a sequence or it can continue to provide values indefinitely. Amongst other use cases this is intended to replace any scenarios where the client is currently polling for new values - now the server can stream those to the client upon request.

Breaking changes

  • The NonBlockingServer protocol has been renamed to XPCNonBlockingServer.
  • The underlying interprocess communication protocol between the client and server has changed (to support the above mentioned new functionality). This means if you update SecureXPC, you need to do so for both your client and server implementations at the same time.