You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a bit difficult to translate the spec to the behaviour that we should implement, but I think this bullet:
> If the data buffer is an empty string, set the data buffer and the event type buffer to the empty string and return.
Implies that if the event has no data, we should automatically wait for an event with data. This allows APIs to stream SSEs containing only comments to keep the stream alive. I think it makes sense to handle this hear, rather than requiring the end user to deal with it.
`event$data` is also now guaranteed to be a single string, which I think is easier to deal with.
Fixes#650
Copy file name to clipboardExpand all lines: NEWS.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# httr2 (development version)
2
2
3
-
*`aws_v4_signature()` now works if url contains query parameters (@
4
-
jeffreyzuber, #645).
3
+
*`resp_stream_sse()` now automatically retrieves the next event if the current event contains no data. The data is now returned as a single string (#650).
4
+
*`aws_v4_signature()` now works if url contains query parameters (@jeffreyzuber, #645).
0 commit comments