Search Results for "browsers"

Whenever you’re writing more than a little snippet of code anywhere on the web, activate GhostText to open your preferred text editor and enjoy your own development environment. GhostText is a browser extension that connects to your editor via its own extension. Install both extensions and, if necessary, start the GhostText server in the editor’s extension. Most editor extensions are authored by third parties. You can create more extensions for your favorite editor! Refer to the protocol...

A simple WebSocket server.

...If that fails it can use a variety of browser-specific transport protocols and presents them through WebSocket-like abstractions. SockJS is intended to work for all modern browsers and in environments which don't support the WebSocket protocol, for example, behind restrictive corporate proxies. SockJS-client does require a server counterpart, such as SockJS-node, which is a SockJS server for Node.js. The API should follow HTML5 Websockets API as closely as possible. All the transports must support cross domain connections out of the box. ...

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

The maintainers of SockJS and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open-source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. SockJS is a JavaScript library (for browsers) 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, with WebSockets or without. This necessitates the use of a server, which this is one version of, for Node.js.

websocketd is the WebSocket daemon. It takes care of handling the WebSocket connections, launching your programs to handle the WebSockets, and passing messages between programs and web-browser. 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...

...download link (and notes) : https://sourceforge.net/projects/websocketserverinapatch/files/ "websocket-server in a patch.pd" single Pd file contains a reusable and fully documented websocket server, meant as an easy way to experiment with Pure Data <-> web-browsers communications through websockets, without the need of other software (like node.js or python) or any specific external to compile (just one deken library is required). 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 !