-
DEFAULT_MAX_SSE_CLIENTS in AsyncEventSource.h not used anywhere
-
The current client API offers a great deal of flexibility:
- with an `sse.Client` multiple `Connection`s with the same configuration can be made
- there can be multiple event listeners (for distinct…
-
**Description:**
$Subject. Only happens in http2.
Service is not fully hung. each request gets served until the point of http client creation. Service works for sometime and this hanging behavior…
-
Hello!
Didn't find in your documentation information about support SSE.
Can Feign client was sse client?
-
### Description
This leads to resource leakage. Possibly relevant to #2958.
### URL to code causing the issue
https://github.com/vrslev/litestar-sse-cleanup-issue
### MCVE
_No response_
### Step…
-
Hello
at the Browser like (chrome) its possible to close active opened event-source by just close the Browser,
now I have a server allow only 1 concurrent SSE , so only one client (session) is allo…
-
### Suggestion
Enable Server-Sent Events (SSE) in `@configu/proxy`. The proxy should trigger SSE based on a cron job interval string passed as a query parameter to the `POST /export`, which runs th…
-
### Problem description
With the implementation of #6209 to detect slashable events, it still requires either useful infrastructure/3rd party software to take advantage of this feature. An idea is to…
-
EVENTSTREAM_STORAGE_CLASS = "django_eventstream.storage.DjangoModelStorage"
1. client connected, listener added
![image](https://github.com/user-attachments/assets/62873e5e-8ccf-4962-ab56-7d66f218…
-
### What happened?
I tried to complete a simple SSE example and passed the test using curl, but discovered the following problems while writing the go test case.
I found an unknown bug in client…