Description
The JSON object send as an event over EventSource contains a pushState paramater.
{"@type":"StateChange","changed":{"cf2e474f942d8ea3192028d2e37d5b08b3ddd36fb986d2ad6a19d66277a981c4":{"Email":"b7ee2d20-96ec-11eb-b57c-1b93c9e59cb7"}},"pushState":"ddc397e7a13fd27566ec3b7ed9bcc702c4c097e1ad83ebc8b909f3d5be459345"}
This pushState parameter is not defined in RFC 8620 7.1 and is therefor unnecessary. It is an extension that only the WebSocket protocol uses.
However EventSource defines it's own event ids inband that are probably (not knowing a lot about the server side of this implementation) functionally equivalent.
James should use the EventSource’s id instead of putting the id in the JSON payload.
Attachments
Issue Links
- links to