Search Results for "process"

LaravelS is an out-of-the-box adapter between Laravel/Lumen and Swoole. LaravelS uses Swoole's Synchronous IO mode, the larger the worker_num setting, the better the concurrency performance, but it will cause more memory usage and process switching overhead. If one request takes 100ms, in order to provide 1000QPS concurrency, at least 100 Worker processes need to be configured. Create WebSocket Handler class, and implement interface WebSocketHandlerInterface. The instant is automatically instantiated when start, you do not need to manually create it.

Simple WebSocket server implemented in PHP.

facil.io is an evented Network library written in C. facil.io provides high performance TCP/IP network services by using an evented design that was tested to provide an easy solution to the C10K problem. facil.io includes a mini-framework for Web Applications, with a fast HTTP / WebSocket server, integrated Pub/Sub, optional Redis connectivity, easy JSON handling, Mustache template rendering and more nifty tidbits. facil.io powers the HTTP/Websockets Ruby Iodine server and it can easily...

...If you can run your program from the command line, you can write WebSocket endpoints. Just read incoming text from stdin and write outgoing text to stdout. Messaging is simple. Each inbound WebSocket connection runs your program in a dedicated process. Connections are isolated by process. Available for Linux, OSX, Windows, FreeBSD, OpenBSD and Solaris. Serves your static HTML, JavaScript, etc. Route different URLs to different programs. Dynamic generate content over HTTP too. Out-of-the-box support for serving content using HTTPS and WSS. Restrict which pages can make WebSocket connections. ...

N2O is an embeddable message protocol loop library for WebSocket, HTTP, MQTT and TCP servers. It provides basic features, such as process management, virtual nodes ring for request processing, sessions, frame encoding, and unified API for external mq and caching services.

...It is originally designed to be used by the ROYGBIV Engine. However, it can be used outside of ROYGBIV as well. Javascript is slow, therefore we want to have as much main-process-power as we can in order to do game related calculations, graphics rendering and achieving 60 FPS. For multiplayer games achieving 60 FPS gets even more complicated given that transferring data over WebSockets is a slow operation. It also triggers GC activity by copying the transferred data (if JSON is the preferred way), which eventually slows down the main thread as well.