| 1 |
Source: aiohttp-sse-client2 |
| 2 |
Maintainer: Home Assistant Team <[email protected]> |
| 3 |
Uploaders: |
| 4 |
Edward Betts <[email protected]>, |
| 5 |
Section: python |
| 6 |
Priority: optional |
| 7 |
Build-Depends: |
| 8 |
debhelper-compat (= 13), |
| 9 |
dh-sequence-python3, |
| 10 |
dh-sequence-sphinxdoc <!nodoc>, |
| 11 |
pybuild-plugin-pyproject, |
| 12 |
python3-all, |
| 13 |
python3-setuptools, |
| 14 |
Build-Depends-Indep: |
| 15 |
python3-sphinx <!nodoc>, |
| 16 |
Standards-Version: 4.7.2 |
| 17 |
Homepage: https://github.com/JelleZijlstra/aiohttp-sse-client2 |
| 18 |
Vcs-Browser: https://salsa.debian.org/homeassistant-team/deps/aiohttp-sse-client2 |
| 19 |
Vcs-Git: https://salsa.debian.org/homeassistant-team/deps/aiohttp-sse-client2.git |
| 20 |
|
| 21 |
Package: python3-aiohttp-sse-client2 |
| 22 |
Architecture: all |
| 23 |
Depends: |
| 24 |
${misc:Depends}, |
| 25 |
${python3:Depends}, |
| 26 |
${sphinxdoc:Depends}, |
| 27 |
Built-Using: |
| 28 |
${sphinxdoc:Built-Using}, |
| 29 |
Description: Async client for receiving Server-Sent Events streams over HTTP |
| 30 |
This library enables applications to connect to HTTP endpoints that provide |
| 31 |
Server-Sent Events (SSE) and to listen for real-time event streams in an |
| 32 |
asynchronous, non-blocking manner. It maintains a persistent connection to the |
| 33 |
remote SSE server, automatically handling reconnections in cases of network |
| 34 |
interruptions or dropped connections. Incoming event messages are parsed |
| 35 |
according to the SSE protocol specification, making it possible to process |
| 36 |
update notifications, messages, or status changes as soon as they are |
| 37 |
published by the server. This is useful for consuming live data feeds from web |
| 38 |
servers or public APIs, such as news updates or monitoring information. The |
| 39 |
library provides tools for error handling, including exposing server response |
| 40 |
bodies when a connection cannot be established or returns an unexpected status |
| 41 |
code. Communication occurs over standard HTTP, and connections can be |
| 42 |
established securely depending on the endpoint's configuration. |