Cloud event posting now distinguishes a dead session from a network failure.
What's wrong with this entry?
Posting an event to a cloud session now returns a named outcome instead of a value or null, so an event sent to a session that is no longer running is distinguished from a network failure.
- Outcomes: accepted (with a sequence number), session inactive, or failed with a cause separating HTTP, timeout and network errors.
- An inactive session logs "(session not active)" and increments a
remote_send_event_session_inactivecounter. - Control responses can now supply their own message identifier and are counted as sends.
remote_send_event_session_inactive
Strings lifted out of the shipped bundle, so the claim above can be checked against them.