Search Results for "main"

µWebSockets.js is a web server bypass for Node.js that reimplements eventing, networking, encryption, web protocols, routing and pub/sub in highly optimized C++. As such, µWebSockets.js delivers web serving for Node.js, 8.5x that of Fastify and at least 10x that of Socket.IO. It is also the built-in web server of Bun.

...Since v.0.4.1 Boost::ASIO (1.66 or higher) is also supported. Consider the task of writing a C++ application that must support some REST API, RESTinio represents our solution for that task. Server runs on the main thread, and responds to all requests with a hello-world message. Of course, you've got access to the structure of a given HTTP request, so you can apply complex logic for handling requests. Async request handling. Cannot get the response data immediately? That's ok, store the request handle somewhere and/or pass it to another execution context and get back to it when the data is ready.

...The API should follow HTML5 Websockets API as closely as possible. All the transports must support cross domain connections out of the box. It's possible and recommended to host a SockJS server on a different server than your main web site.

Client library providing WAMP on Java 8 (Netty) and Android, plus (secure) WebSocket for Android. The WebSocket layer is using a callback-based user API, and is specifically written for Android. Eg it does not run any network stuff on the main (UI) thread. The WAMP layer is using Java 8 CompletableFuture for WAMP actions (call, register, publish, and subscribe) and the Observer pattern for WAMP session, subscription and registration lifecycle events. The library is MIT licensed, maintained by the Crossbar.io Project, tested using the AutobahnTestsuite and published as a JAR to Maven and as a Docker toolchain image to Dockerhub.

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

...A demo is included in the same patch : 'Flames', a simple cross-browser, multi-touch and multi-player graphical interface which makes Pd play creepy sounds :) Just try it : In Pd (vanilla) on Windows, Mac or Linux, install the 'mrpeach' library via 'Help->Find externals' menu, then open the patch and fire any recent web-browsers (on same machine or other computer, smartphone or tablet on same local network) with the URL provided at the top of main windows, and you're good to go !