WICG/direct-sockets

Filling the remaining gap between WebSocket, WebRTC and WebTranspor

Existing web platform facilities for network communication include WebSocket and WebRTC. Each mandates a specific protocol, ensures TLS, and respects the Same Origin Policy. The proposed WebTransport is similar in these respects.

SocketDev/socket-mcp

Model Context Protocol server for socket.dev integration

QUIC API for Peer-to-peer Connections

This document defines a set of ECMAScript APIs in WebIDL to allow data to be sent and received from another browser or device implementing the QUIC protocol. The specification for multiplexing of QUIC with STUN/TURN/ZRTP/DTLS/RTP/RTCP [[RFC9443]] was developed within the IETF AVTCORE Working Group.

r58Playz/wisp-iwa

Wisp protocol client in an Isolated Web App

🔎 No WebSocket implementation was found in your environment. You must provide an implementation as the `ws` option. - Google Search

Generic Event Delivery Using HTTP Push

This document describes a simple protocol for the delivery of real- time events to user agents. This scheme uses HTTP/2 server push.

mschwager/socket-speed

Comparing IPC methods on Linux.

chadtmiller.com/goose

A Gleam WebSocket consumer for AT Protocol Jetstream events.

RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win | TechCrunch

Editor's note: With all of the debate lately between RSSCloud versus PubSubHubbub, we wanted to hear from a developer who could actually tell us which one might be better and why. The following guest post is written by Josh Fraser, the co-founder of EventVue, who is an active contributor to PubSubHubbub in his free time. He has contributed several client libraries for PubSubHubbub including a WordPress plugin. Guess which side of the debate he falls on. In the past few months, a lot of attention has been given to the rise of the real-time web. The problem is that the web wasn't designed with real-time in mind. There is a huge need for the tech community to get behind new protocols that will power this fundamental shift in how web applications work. Today I want to take a look at two of the leading protocols that enable real-time notifications on the web. While there are older protocols that enable real-time notifications like XEP-0060, PubSubHubbub (PuSH) and rssCloud are two new protocols which show a lot of promise of gaining adoption. Both PuSH and rssCloud address a fundamental flaw in the way web applications work today. Currently, getting updates on the web requires constant polling. Subscribers are forced to act like nagging children asking, "Are we there yet?" Subscribers must constantly ping the publisher to ask if there are new updates even if the answer is "no" 99% of the time. This is terribly inefficient, wastes resources, and makes it incredibly hard to find new content in as soon as it appears. Both protocols flip the current model on its head so that updates are event driven rather than request driven. By that I mean that both protocols eliminate the need for polling by essentially telling subscribers, "Don't ask us if there's anything new. We'll tell you." But if you find yourself confused about how they are different, you're not alone.

Isolated Web Apps (IWA)  |  Chrome for Developers

Isolated Web Apps allow for a high-trust security model for web apps allowing for access to high-trust APIs like Direct Sockets and Controlled Frame.

High Performance Browser Networking (O'Reilly)

What every web developer must know about mobile networks, protocols, and APIs provided by browser to deliver the best user experience.

bigmoves/goose

🪿 A Gleam WebSocket consumer for AT Protocol Jetstream events.

Connect

Simple, reliable, interoperable: Protobuf RPC that works.