Search Results for "libhamlib-4"

Socket.IO-client for iOS/OS X. Supports Socket.IO server 2.0+/3.0+/4.0+. Supports Binary, supports Polling and WebSockets, and supports TLS/SSL. Requires Swift 4/5 and Xcode 10.x. Add the project as a dependency to your Package.swift. Add the Starscream and SocketIO frameworks to your projects and follow the usual Carthage process.

...Ratchet provides many components for you to pick and choose from to easily add functionality. The component architecture allows you to focus on functionality with the ability to reuse and add or remove other component functionality. Ratchet is fully PSR-4 compliant, so it naturally plays well with others. Leveraging components from Symfony2, development should feel similar to many. Ratchet passes all WebSocket tests to ensure it works on all supported browsers.

Wslay is a WebSocket library written in C. It implements the protocol version 13 described in RFC 6455. This library offers 2 levels of API: event-based API and frame-based low-level API. For event-based API, it is suitable for non-blocking reactor pattern style. You can set callbacks in various events. For frame-based API, you can send WebSocket frame directly. Wslay only supports data transfer part of WebSocket protocol and does not perform opening handshake in HTTP. Wslay does not perform...

This library is a WebSocket server/client library with HTTP server capability. Sample chat server/client apps attached. * .NET 4.5 required * WPF application

This project provides 6 new functions to PHP that are meant to interact with a websocket (RFC6455) peer. ws_get_frame_info() - Gets information about an upcoming websockets frame ws_read_frame() - Reads the data of a websockets frame from a client or server ws_send_close() - Sends a close frame to the websockets peer ws_send_ping() - Sends a ping frame to the websockets peer ws_send_pong() - Sends a pong frame to the websockets peer These functions are written in low level C so...

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:...