Releases: rsocket/rsocket-py
Releases · rsocket/rsocket-py
v0.4.15
- Websockets server support (https://github.com/python-websockets/websockets)
- AsyncWebsockets client support (https://github.com/Fuyukai/asyncwebsockets)
v0.4.14
- GraphQL: Use async methods for query resolvers. Fixed using mutation methods and passing variables.
v0.4.13
- GraphQL basic support (See examples/graphql)
v0.4.12
- Fixed fragmentation for fire and forget
- Fixed incorrect limit on tag (and route) length from 127 to 255 (GooDer)
v0.4.11
- Breaking change: RequestRouter argument 'payload_mapper' was replaced with 'payload_deserializer' and 'payload_serializer'*
- Added CloutEvent serialize/deserialize helpers for use in RequestRouter
v0.4.10
- Code cleanup
- Breaking change: Removed deprecated rsocket.routing.helpers module
- Added CloudEvents client/server usage example (compatible with java rsocket example from cloudevents/sdk-java)
- Switched to pyproject.toml
v0.4.9
- Optimization to routing requests to methods and parsing composite metadata
v0.4.8
- Removed copying data and metadata into frame during serialization
v0.4.7
- Send cancel to responders when requester disconnects and error to requesters when requester disconnects
- Fix guide examples to properly cancel responders which use asyncio Task as value source
- Rewrote guide statistics example to use generator instead of task
v0.4.6
- fire_and_forget now only removes the stream id when the future denoting the frame was sent, is done
- API documentation auto generated at rsocket.readthedocs.io
- Request router changes:
- Raise error on empty or None route specified in request router
- Added the following methods to RequestRouter to allow specifying handlers of unknown routes:
- response_unknown
- stream_unknown
- channel_unknown
- fire_and_forget_unknown
- metadata_push_unknown
- Officially support route aliases by using the decorator multiple times on the same method
- Fix value mapping in request router:
-A parameter of any name (not just payload) specified on a routed method with a type-hint other than Payload will use the payload_mapper to decode the value- Any parameter with the type CompositeMetadata will receive the composite metadata