Search Results for "linux socket ipc"

Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client. Messages are represented through the JSON structure and are stringified before being sent over the network. They are bidirectional, meaning both the server and the client must conform to the specified message structure. Connection is a connection within the established socket describing a "connection" through which the operation requests will be communicated. The server can close the socket...

A Node.js serverless framework for front-end/full-stack developers. Build the application for next decade. Works on AWS, Alibaba Cloud, Tencent Cloud, and traditional VM/Container. Super easy integrate with React and Vue. There are many similar frameworks in the community, so why do you need Midway? Midway is a framework that Alibaba has been developing continuously. Before egg was used as the underlying framework, an application-oriented framework was required to connect with the group's...

Socket.IO Redis Adapter is the official Redis-backed adapter for scaling Socket.IO applications across multiple Node.js server instances. It allows events emitted on one Socket.IO server to be broadcast to clients connected to other servers. The adapter uses Redis Pub/Sub as its communication layer, so Socket.IO packets can move between processes without storing persistent session data in Redis. It is useful when an application runs behind a load balancer, in a cluster, or across multiple...

Inputs watch log files for changes, send new log messages to the server, which broadcasts to web clients. Log messages are tagged with stream and source information based on user configuration. log.io has no persistence layer. File inputs are informed of file changes via inotify, and log messages hop from input to server to web client via TCP and socket.io, respectively. log.io uses a stateless TCP API to receive log messages. Writing a third party harvester is easy. Open a TCP connection to...

FluxyChat is a multi-tenant realtime chat API built on Cloudflare Workers, Durable Objects, and D1. What's different: - One Durable Object per room: WebSocket fan-out + ordering at the edge, no socket fleet to manage - Agent tool calls stream on the same room WebSocket as chat messages — debuggable in the operator console - MIT self-host on your own Cloudflare account, or use the hosted beta - Next.js operator console: rooms, agents, billing hooks out of the box - @fluxy-chat/sdk:...