ably/specification

Remove usage of "will" to describe requirements

#402

· lawrence-forooghian opened

on Nov 3, 2025

Docstrings for `ErrorInfo` are not suitable for public

documentation

#395

· lawrence-forooghian opened

on Oct 16, 2025

Change Objects plugin name according to the plugin naming convention changes

live-objects

#377

· VeskeR opened

on Sep 8, 2025

Clarify `RTO10b` suggests the SDK to store `objectsGCGracePeriod` value from latest received `CONNECTED` event (but not wait for it) and use a default value otherwise

live-objects

#376

· VeskeR opened

on Sep 5, 2025

Clarify in CONTRIBUTING guide whether the spec should be trying to handle users passing incorrect argument types or client receiving malformed messages from realtime

live-objects

#374

· VeskeR opened

on Sep 5, 2025

Clarify encoding/decoding for `float64` numbers in LiveObjects

live-objects

#373

· VeskeR opened

on Sep 5, 2025

Clarify how we want to represent `undefined` values in LiveMap methods like `.entries()`, `.values()` and `.size()`

live-objects

#372

· VeskeR opened

on Sep 4, 2025

Update `RTO2` to check only against the modes granted by the server and give languages a choice of loggin a warning instead of throwing an error

live-objects

#371

· VeskeR opened

on Sep 4, 2025

Change `RTO1` to have an implicit channel attach and clarify how it reacts to sync sequence changes

live-objects

#369

· VeskeR opened

on Sep 4, 2025

`ObjectsCounterOp` size calculation inconsistency

live-objects

#367

· lawrence-forooghian opened

on Sep 4, 2025

Clarify if `ObjectMessage.operation` should have `map` or `counter` properties set when sending `MAP_CREATE` and `COUNTER_CREATE` messages

live-objects

#366

· VeskeR opened

on Sep 3, 2025

Assess the potential impact of requiring `echoMessages` to be set to `true` when using the LiveObjects plugin across various product offerings (PubSub, Chat, and Spaces)

live-objects

#365

· VeskeR opened

on Sep 3, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Remove usage of "will" to describe requirements

Docstrings for `ErrorInfo` are not suitable for public

Change Objects plugin name according to the plugin naming convention changes

Clarify `RTO10b` suggests the SDK to store `objectsGCGracePeriod` value from latest received `CONNECTED` event (but not wait for it) and use a default value otherwise

Clarify in CONTRIBUTING guide whether the spec should be trying to handle users passing incorrect argument types or client receiving malformed messages from realtime

Clarify encoding/decoding for `float64` numbers in LiveObjects

Clarify how we want to represent `undefined` values in LiveMap methods like `.entries()`, `.values()` and `.size()`

Update `RTO2` to check only against the modes granted by the server and give languages a choice of loggin a warning instead of throwing an error

Change `RTO1` to have an implicit channel attach and clarify how it reacts to sync sequence changes

`ObjectsCounterOp` size calculation inconsistency

Clarify if `ObjectMessage.operation` should have `map` or `counter` properties set when sending `MAP_CREATE` and `COUNTER_CREATE` messages

Assess the potential impact of requiring `echoMessages` to be set to `true` when using the LiveObjects plugin across various product offerings (PubSub, Chat, and Spaces)

Issues

Search results