Skip to content
New issue

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

Transport properties for HTTP/SSE Source #206

Closed
dilini-muthumala opened this issue Mar 17, 2021 · 1 comment
Closed

Transport properties for HTTP/SSE Source #206

dilini-muthumala opened this issue Mar 17, 2021 · 1 comment

Comments

@dilini-muthumala
Copy link
Contributor

dilini-muthumala commented Mar 17, 2021

Description:
According to the SSE specification, a event can have the following meta attributes, in addition to the data

Quoting from https://www.w3.org/TR/eventsource/#event-stream-interpretation

If the field name is "event"
Set the event type buffer to field value.

If the field name is "data"
Append the field value to the data buffer, then append a single U+000A LINE FEED (LF) character to the data buffer.

If the field name is "id"
Set the last event ID buffer to the field value.

If the field name is "retry"
If the field value consists of only ASCII digits, then interpret the field value as an integer in base ten, and set the event stream's reconnection time to that integer. Otherwise, ignore the field.

Is there any way to access these fields in an event?
It would be useful if these fileds are made available to the SSE source as transport properties.

For example, a user might want to filter out the events of a certain type.
Are we only passing the messages of type "message" ?
If so, it would be useful to keep it as the default type, but give the user the ability to override it.

Affected Product Version:
wso2si-tooling-4.0.0-SNAPSHOT

@sajithshn
Copy link
Contributor

De-prioritizing as this is not a critical enhancement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants