No description provided.
Standards-compliant WebSocket server and client
Simple pub/sub messaging for the web
WebSocket protocol handler with pluggable I/O
Simple pub/sub messaging for the web
Redis backend engine for Faye
Generic extension manager for WebSocket connections
Per-message DEFLATE compression extension for WebSocket connections
Redis backend engine for Faye with support for sharding
A Node.js API Gateway for the masses!
Simple pub/sub messaging for the web
Simple pub/sub messaging for the web
Redis backend engine for Faye with support for sharding
Development server for PRPL
TypeScript definitions for sfdx-faye
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
forked from http://faye.jcoglan.com
Serves a webpack app. Updates the browser on changes.
geo.mess
A simple zero-configuration command-line http server
Support for presence channels in Faye
Modern and scalable routing for React applications
Modern and scalable routing for React applications
HTTP proxying for the masses
Easily create a Faye pub/sub server
This gem is a logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/plugin install gemname. This gem is not a stand-alone program
Quickly and easily connect your app to a Faye server
Allow a long running faye client to reconnect to a faye server with the same client ID
Colossus is a Push and Presence pure Ruby server. It uses Faye internally.
Uses faye to keep keep a local copy of the queue at the server specified
This plugin automatically starts and restart Faye message server under Guard
Enable server sent events with rack middleware implemented over Faye and Broadcaster (Redis Pub/Sub)
A Redis-based backend engine for Faye messaging server, allowing distribution across multiple web servers
Push ActiveModel changes to Backbone Collections and Models though a Faye Pub/Sub server.
Allows to publish messages to a faye server, the main difference with the default faye client is that it does not need to run inside a EventMachine loop as it only opens a http connection with the server to send the event. Because of this is best to publish events from a separate thread using sidekiq for example.