Tom Bevan

Hi, Any event should be sent immediately providing there is `Data` associated with it. Buffering should only come into play if you are generating events faster than the underlying TCP...

Given what you've described, I've attempted to replicate your issue with the following test code and can't get similar results. ```go srv := sse.New() mux := http.NewServeMux() mux.HandleFunc("/events", srv.HTTPHandler) server...

@kabaluyot Sorry for the delay in getting back to you. I've been on annual holiday. You may want to decouple the kafa stream logic from the sse handler to rule...

Hi! As the library was released with a server implementation and was only intended to be used in conjunction with one another, there was never any emphasis on conforming to...

@loeffel-io The implementation adheres to the SSE specs on everything with the exception of supporting the `retry` field. We use exponential backoff to determine when to reconnect, so it never...

Hey @Venoox , very sorry for not getting back to you sooner! I think this sounds like a good feature to have. If you still have a need for it,...

@Venoox You should now be able to configure the bufio scanner size in `2.7.0` like so: ```go // sets the buffer size to 1

Hey @frederikhors, welcome to the Go community! Good question! Currently enabling stream replay will keep all messages for the life of the stream. The current implementation does not support a...

Hi @tigerlee Thanks for raising the issue! This should now be fixed in `v2.3.6`

Hey @aexvir , thanks for raising the issue! So there are a couple of ways to handle this: 1. use `diff.Filter` as you suggest 2. use `diff:"-"` tag on your...