Search Results for "javascript"
Sort By:
Showing 5 open source projects for "javascript"
View related business solutions-
Earn up to 15% annual interest with Nexo.Put idle assets to work with competitive interest rates, borrow without selling, and trade with precision. All in one platform. Geographic restrictions, eligibility, and terms apply.
-
Earn up to 15% annual interest with Nexo.Generate interest, borrow against your crypto, and trade a range of cryptocurrencies — all in one platform. Geographic restrictions, eligibility, and terms apply.
-
1
socket.io
Realtime application framework (Node.JS server)
socket.io is a JavaScript library that allows for realtime, bi-directional communication between web clients and servers. It is composed of two parts: a Node.js server and a JavaScript client library that runs in the browser. socket.io is focused on both reliability and speed, delivering an immensely powerful, fast and yet easy to use realtime engine that’s used by just about everyone: from Microsoft Office and Zendesk to hackathon winners and small startups. -
2
rpc-websockets
JSON-RPC 2.0 implementation over WebSockets for Node.js
The rpc-websockets library enables developers to easily implement their business logic that includes messaging between users, machines or any devices. It provides a possibility to send and receive JSON data through the WebSocket communication protocol in order to support two-way notification push, running RPC methods and firing any types of event signalling. Only clients can call RPC methods and not vice versa at the moment. Both frontend (HTML/JS-based) and backend (Node.js-based)... -
3
SockJS-client
WebSocket emulation and Javascript client
SockJS is a browser JavaScript library that provides a WebSocket-like object. SockJS gives you a coherent, cross-browser, Javascript API which creates a low latency, full duplex, cross-domain communication channel between the browser and the web server. Under the hood SockJS tries to use native WebSockets first. If that fails it can use a variety of browser-specific transport protocols and presents them through WebSocket-like abstractions. -
4
Rhubarb
A WebSocket library optimized for multiplayer JS games
Rhubarb is a lightweight WebSocket library for multiplayer HTML5 games. 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. -
PairSoft | AP Automation and Doc ManagementStreamline operations and elevate your team's efficiency with PairSoft. Our AP automation, procurement, and document management solutions eliminate manual processes, cut costs, and free your team to focus on strategic initiatives. Experience our state-of-the-art invoice-to-pay solution, now integrated with advanced AI technology for faster, smarter results. Our customers report a significant 70% reduction in approval times and annual savings of $62,000 in employee hours. At PairSoft, we aim to transform your business operations through automation. Explore the future of automation at pairsoft.com, where you can leverage cutting-edge features like invoice capture, OCR, and comprehensive AP automation to transform your workflow. Whether you are a small business or a large enterprise, our solutions are designed to scale with your needs, providing robust functionality and ease of use. Join the growing number of businesses that trust PairSoft.
-
5
Sockette
The cutest little WebSocket wrapper
Sockette is a tiny (367 bytes) wrapper around WebSocket that will automatically reconnect if the connection is lost. In addition to attaching additional API methods, Sockette allows you to reuse instances, avoiding the need to redeclare all event listeners. You have direct access to the (current) underlying WebSocket within every EventListener callback.
- Previous
- You're on page 1
- Next
