Missing (clear) description of message structure

[theking2]

MDN URL

files/en-us/web/api/eventsource/message_event/index.md

What specific section or headline is this issue about?

Examples

What information was incorrect, unhelpful, or incomplete?

It is not clear that raw message must have a very specific structure in order for the EventSource recognize. Also server site buffering will result in behaviour in which the onmessage event is only triggered after a large number of messages is send.

What did you expect to see?

Mentioning of message structere:

event: <event-name>\n
data: \n\n

Note: For smaller messages, make sure server side buffering is adjusted adquately for message to be send in time.

Do you have any supporting links, references, or citations?

Switch off buffering for for instance nginx proxies, php-fpm etc is not at all trivial. And should at least be mentioned

Do you have anything more you want to share?

No response

[theking2]

I've found that the format of an event stream is described on MDN
It would be awesome if this had a link in the article EventSource.

[Josh-Cena]

What exactly is this issue suggesting? As you discovered, the message structure is already documented, and the https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events page is linked to on both the https://developer.mozilla.org/en-US/docs/Web/API/EventSource/message_event page and https://developer.mozilla.org/en-US/docs/Web/API/EventSource pages. That's about the degree of attention it deserves.

[theking2]

You are right. I was just slightly annoyed I spend a whole 4 hours on a sunday afternoon to figure out why the stream did not work just because messages follow a very distinctive pattern and are not json based (at all).

My effort is(was) to prevent other future developers to run in the same problem. Not sure if that is possible with the current standard.