new ReceivedEvent()
Message Received on Server event: "acknowledge" or "negative acknowledge" - these are the events which the
returned Promise of a send(..) is settled with (i.e. then() and catch()), and which
request's receivedCallback function are invoked with.
- Source:
Members
description :string
Sometimes, typically on Server NACKs (e.g. targetting non-existing Endpoint), the Server supplies a
description to why this was no good.
Type:
- string
- Source:
receivedTimestamp :number
Millis-since-epoch when the ACK or NACK was received on the Client, millis-since-epoch.
Type:
- number
- Source:
roundTripMillis :number
Round-trip time in milliseconds from Initiation of flow (send, request, requestReplyTo) to Received
acknowledgement (ACK/NACK) was received, basically
#receivedTimestamp
- #sentTimestamp, but depending on the browser/runtime, you might get higher resolution
than integer milliseconds (i.e. fractions of milliseconds, a floating point number) - it depends on
the resolution of performance.now().
Notice that Received-events might be de-prioritized on the Server side (batched up, with micro-delays
to get multiple into the same batch), so this number should not be taken as the "ping time".
Type:
- number
- Source:
sentTimestamp :number
Millis-since-epoch when the message was sent from the Client.
Type:
- number
- Source:
traceId :string
TraceId for this call / message.
Type:
- string
- Source:
type :string
Values are from ReceivedEventType: Type of received event, either "ack",
"nack" - or "sessionclosed" if the
session was closed with outstanding initiations and MatsSocket therefore "clears out" these initiations.
s
Type:
- string
- Source: