We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RxNetty's SSE encoder does not produce valid output. If you look at spec (http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#event-stream-interpretation), the ServerSentEventDecoder is pretty close following it. So for example if we get on the wire
event: add data: something id: 1
It will be mapped to ServerSentEvent object ServerSentEvent("1", "add", "something").
However the encoder will just produce for such event just one line of this kind:
add: something
And small naming improvement - eventName is described as eventType in the spec.
The text was updated successfully, but these errors were encountered:
cc @g9yuayon
@tbak makes sense to me.
So, this is what I understand which should be possible
event: <name> data: <data> id: <id>
event: <name> data: <data>
data: <data> id: <id>
data: <data>
The usecase of above would predominantly be to send multiple data attributes per event name or event name + id combination.
Sorry, something went wrong.
5eca246
Merge pull request #152 from tbak/master
3b66dc6
Fix #141 issue.
No branches or pull requests
RxNetty's SSE encoder does not produce valid output. If you look at spec (http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#event-stream-interpretation), the ServerSentEventDecoder is pretty close following it. So for example if we get on the wire
event: add
data: something
id: 1
It will be mapped to ServerSentEvent object ServerSentEvent("1", "add", "something").
However the encoder will just produce for such event just one line of this kind:
add: something
And small naming improvement - eventName is described as eventType in the spec.
The text was updated successfully, but these errors were encountered: