.typing-indicator-stream
Used to send a signal when a user has started typing. Refer to the section on typing indicators for more information.type
could be overridden to anything you want, internally it is not processed.ContextFreeMessage
. The model of the same is:ContextFreeMessage
from a regular message is that a context-free message is never persisted, does not contain an identifier and cannot be retrieved. A context-free message is delivered purely on a best-effort basis and there are no guarantees on delivery of the same. As opposed to messages context free messages are delivered much faster and are only delivered on messaging pipelines. For clients using HTTP polling, context free messages or messages from a stream cannot be fetched.context
is provided to give a categorization to the type of message that was sent. For example, if on a stream you were sending two kind of messages - one containing only the differences in the mouse pointer from the last location and one where an absolute location was provided, then these two type of messages can be coded as two different contexts..typing-indicator-stream
for the channel. It should follow the structure:senderId
field to be in typing status for a specified amount of time (we recommend this time to be 7 seconds). If during this time interval (before the user is reset to a non-typing state) if another channel stream datum is received for the same user, this timer should be reset.create_channel_stream
privilege is required, which is always granted to .system
(i.e. when using an application access key/secret).Stream
object back, populating an identifier if you did not provide one.supportedContentTypes
to make the stream accept data in any type.send_to_channel
privilege (if the sender id is the same as the user making the call) or the send_as_other_to_channel
(if the sender id is different than the user making the call). By default all users have the send_to_channel
privilege granted to them and .system
always has send_as_other_to_channel
granted to it. Do note that this is the same privilege that is checked for sending messages to a channelsend_to_channel
can send messages to all streams in that channel. We are currently working on having stream specific privileges.read_from_channel
privilege are marked as delivery recipients. For the shape of the received payload, refer to the section pipeline payload.