How do I install the API Streaming Sse Websocket Long Polling skill?

Run npx skillmds@latest add deangrant/api-streaming-sse-websocket-long-polling in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is API Streaming Sse Websocket Long Polling safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with API Streaming Sse Websocket Long Polling?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is API Streaming Sse Websocket Long Polling free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published API Streaming Sse Websocket Long Polling?

deangrant (@deangrant) published this skill. Their other Agent Skills are listed on their SkillMD profile.

API Streaming Sse Websocket Long Polling by deangrant

Name: API Streaming Sse Websocket Long Polling
Author: deangrant

API Streaming Sse Websocket Long Polling

Choose SSE, WebSocket, or long-polling for realtime API push: directionality, reconnect, auth limits, and when to use 202 jobs instead. Use when designing event feeds, chat, or live updates.

deangrant b3fd397 4 files · 2.4 KB Updated Sep 17, 2026

File contents

Streaming APIs: SSE, WebSocket, Long-Polling

Use this skill for continuous push. One-shot slow work → async 202 + job, not streaming.

1. Long-polling

Hold GET until data or timeout (~30s); client reconnects. High header overhead; fallback for restrictive networks / infrequent updates. Client backoff.

2. SSE (one-way)

Content-Type: text/event-stream. Browser EventSource; auto-reconnect + Last-Event-ID; keep-alive comments; stop with 204. Cannot set custom headers — auth via query token or cookie. Prefer HTTP/3; scale with broker fan-out.

3. WebSocket (duplex)

Upgrade 101; full-duplex; heartbeats; reconnect+jitter; sticky LB or shared registry/pub-sub.

4. Selection

Need	Prefer
One-way server→client	SSE
Two-way high-frequency	WebSocket
Restricted networks	Long-poll
Minutes-long CRUD	202 job

5. Quick checklist

Correct transport for direction/frequency.
Reconnect + keep-alive strategy.
Auth compatible with EventSource limits if SSE.
Fan-out/broker plan at scale.
Not using streams for one-shot jobs.

See reference.md and examples.md.

Frequently asked questions