# websockets Published articles for websockets. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mercure Broadcasting in Laravel 13.32 DevFeed: [Mercure Broadcasting in Laravel 13.32]() Original publisher: [Read original article]() Author: Paul Redmond Published: 2026-09-16T02:44:52Z Content type: release Language: en Sources: [Laravel]() Topics: [Laravel](), [releases](), [Release notes](), [real-time](), [enum](), [WebSocket]() Tags: [enums](), [features](), [github](), [laravel](), [laravel-releases](), [news](), [queue](), [real-time](), [release](), [release-notes](), [storage](), [update](), [websockets]() ### AI overview Laravel 13.32 adds a Mercure broadcast driver, filesystem methods for copying and moving files between disks, and enum support for queue pause and resume methods. The release also includes additional fixes and updates. ### Source excerpt Laravel 13.32 adds a Mercure broadcast driver, Storage::copyToDisk() and moveToDisk(), enum support in queue pause/resume, and more. The post Mercure Broadcasting in Laravel 13.32 appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## Gemini Live audio DevFeed: [Gemini Live audio]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-09-15T22:47:07Z Content type: tutorial Language: en Sources: [Simon Willison's Weblog]() Topics: [speech-to-speech](), [WebSocket](), [Google AI](), [browser](), [Playback](), [implementation](), [API]() Tags: [api](), [audio](), [browser](), [gemini](), [gemini-196](), [generative-ai](), [generative-ai-1-982](), [google](), [google-416](), [llm-release](), [llm-release-231](), [llms](), [llms-1-948](), [model](), [models](), [openai](), [playback](), [release](), [speech-to-speech](), [speech-to-text](), [speech-to-text-21](), [tools](), [tools-78](), [ui](), [voice](), [websocket](), [websockets](), [websockets-21]() ### AI overview The article describes a browser-based web UI for trying Google's Gemini 3.8 Live and Gemini 3.8 Live Extended Thinking speech-to-speech models. The implementation supports model and voice selection, an optional system prompt, voice conversations, and interruption while the model is speaking. It uses no libraries, connecting to a WebSocket endpoint and using the Web Audio API for capture and playback. ### Source excerpt Tool: Gemini Live audio Google released Gemini 3.8 Live and 3.8 Live Extended Thinking today - two new speech-to-speech models that are a similar shape to OpenAI's GPT-Live family. I pointed GPT-6 Astra Extra High at the documentation and had it build me this web UI for trying out the new models. You can select a model and voice preset, enter an optional system prompt and then start a voice conversation through your browser, including the ability to interrupt the model while it is talking. The implementation uses no libraries. It connects to the wss://generativelanguage.googleapis.com/ws/google.ai.generativelanguage.v1alpha.GenerativeService.BidiGenerateContent?key=... WebSocket endpoint and uses a Web Audio API AudioContext for both capture and playback. Here's the Gemini Live tutorial for getting started with that WebSockets API. Tags: google, tools, websockets, generative-ai, llms, gemini, llm-release, speech-to-text ## Durable Objects are Made for Agents DevFeed: [Durable Objects are Made for Agents]() Original publisher: [Read original article]() Author: Calvin French-Owen Published: 2026-07-22T12:00:00Z Content type: opinion Language: en Sources: [Calvin French-Owen]() Topics: [Cloudflare](), [Serverless](), [SQLite](), [V8](), [event driven](), [WebSocket](), [wasm]() Tags: [cloudflare](), [event-driven](), [serverless](), [sqlite](), [v8](), [websockets]() ### AI overview An opinionated technical article explains why Cloudflare Durable Objects can be a strong primitive for building agents and other stateful products. It describes their serverless V8 execution model, per-object SQLite storage, ID-based request routing, event-driven structure, and potential shortcomings. ### Source excerpt I've spent the last few months building almost exclusively on Cloudflare Durable Objects. They're a near-perfect primitive for building agents--here's where they shine, and where they fall short. ## Streaming with WebRTC and Mediasoup DevFeed: [Streaming with WebRTC and Mediasoup]() Original publisher: [Read original article]() Published: 2025-08-15T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [WebRTC](), [Streaming](), [real-time](), [servers](), [WebSocket](), [P2P]() Tags: [channel](), [http](), [server](), [streaming](), [video](), [webcam](), [webrtc](), [websockets]() ### AI overview This tutorial introduces Mediasoup, an open-source server-side WebRTC library that functions as a Selective Forwarding Unit (SFU). It explains SFUs alongside MCU and peer-to-peer alternatives, then outlines a basic producer-consumer setup in NodeJS using a server, a client, WebSockets, and webcam and audio streams. ### Source excerpt . [Streaming with WebRTC and Mediasoup](streaming-with-webrtc-and-mediasoup-cover... ## Designing a minimal, local-first version of lichess. DevFeed: [Designing a minimal, local-first version of lichess.]() Original publisher: [Read original article]() Author: Pranshu Raj Published: 2025-05-10T15:22:00Z Content type: article Language: en Sources: [Pranshu Raj - blog on backend systems, performance and sidequests]() Topics: [Local-First](), [Go](), [WebSocket](), [real-time](), [SQLite](), [JavaScript](), [Requirements](), [Latency](), [Persistence](), [Concurrency](), [rate-limiting]() Tags: [concurrency](), [go](), [javascript](), [latency](), [local-first](), [persistence](), [rate-limiting](), [real-time](), [requirements](), [sqlite](), [websockets]() ### AI overview The author outlines a plan for tinychess, a smaller local-first version of Lichess intended as a learning project. The planned system includes real-time gameplay, game validation and persistence, matchmaking, spectators, leaderboards, rate limiting, and scoring, using Go, WebSockets, JavaScript, and SQLite or a flat file. ### Source excerpt How I'm planning to build tinychess, and what I've learnt so far while preparing to build it. ## Cancellation in Kotlin Coroutines DevFeed: [Cancellation in Kotlin Coroutines]() Original publisher: [Read original article]() Published: 2024-06-10T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [cancellation](), [Kotlin](), [kotlin-coroutines](), [Coroutines]() Tags: [android](), [application](), [backend](), [cancellation](), [coroutines](), [kotlin](), [kotlin-coroutines](), [thread](), [websockets](), [workshop-learning-programming]() ### AI overview A tutorial on cancellation in Kotlin Coroutines, explaining how cancellation propagates through coroutine hierarchies, changes coroutine state, raises cancellation exceptions at suspension points, and helps release resources in Android and backend applications. ### Source excerpt Everything you need to know about the cancellation mechanism in Kotlin Coroutines. ## Year in Review: 2023 DevFeed: [Year in Review: 2023]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2024-01-20T00:00:00Z Content type: opinion Language: en Sources: [Tania Rascia]() Topics: [coding](), [Web](), [React](), [Redux](), [GraphQL]() Tags: [burnout](), [career](), [coding](), [graphql](), [life](), [review](), [websockets](), [year-in-review]() ### AI overview A personal review of 2023 and the author's ten years as a developer, covering career history, burnout from writing for DigitalOcean, recent software-related posts, and plans to write more about personal interests. ### Source excerpt It's 2024, y'all. We're 20 days into the year, so I'm running out of time to write that end of year post I always do. I haven't quite known... ## How to Use WebSockets in a Redux Application DevFeed: [How to Use WebSockets in a Redux Application]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2023-02-15T00:00:00Z Content type: tutorial Language: en Sources: [Tania Rascia]() Topics: [WebSocket](), [Redux](), [middleware](), [React](), [browser](), [API]() Tags: [api](), [chat](), [dashboard](), [how-to](), [javascript](), [react](), [redux](), [websockets]() ### AI overview A tutorial on integrating WebSockets into a React/Redux application by using Redux middleware to manage connection events, state access, and dispatched actions. It demonstrates a browser WebSocket client and discusses initializing and closing connections for use cases such as chat and live dashboards. ### Source excerpt At some point, you might work on a React/Redux application that requires the use of WebSockets, such as for chat or live updates on a... ## Creating a chat application from scratch using Rails and WebSockets DevFeed: [Creating a chat application from scratch using Rails and WebSockets]() Original publisher: [Read original article]() Author: Lazarus Lazaridis Published: 2019-04-04T20:00:00Z Content type: tutorial Language: en Sources: [Lazarus Lazaridis]() Topics: [WebSocket](), [Rails](), [web applications](), [Ruby](), [Web Development]() Tags: [actioncable](), [application](), [bootstrap](), [chat](), [code](), [devise](), [featured](), [programming](), [rails](), [redis](), [ruby](), [tutorial](), [websocket](), [websockets]() ### AI overview A tutorial for building a chat web application from scratch with Rails and WebSockets. It explains WebSocket bidirectional communication and real-time data transfer, then introduces the Ruby and Rails versions used for the application. ### Source excerpt Hey! It's been a while since my last post. I recently familiarized myself with the awesomeness of WebSockets and I finally found the time to write a tutorial about it. I hope you find it helpful. Update: I also published another post for dockerizing the application of this tutorial, you can find it here. Introduction In this tutorial we are going to create a chat web application from scratch using Rails and WebSockets. Code and comments You can find the code of this tutorial on GitHub. For feedback, comments, typos etc. please open an issue in the repository. What are WebSockets WebSocket is actually a protocol that enables bidirectional communication between the client and the server of a web application over a single long living TCP connection. The WebSocket protocol enables interaction between a web browser (or other client application) and a web server with lower overheads, facilitating real-time data transfer from and to the server. This is made possible by providing a standardized way for the server to send content to the client without being first requested by the client, and allowing messages to be passed back and forth while keeping the connection open. In this way, a two-way ongoing conversation can take place between the client and the server. The communications are done over TCP port number 80 (or 443 in the case of TLS-encrypted connections), which is of benefit for those environments which block non-web Internet connections using a firewall. Similar two-way browser-server communications have been achieved in non-standardized ways using stopgap technologies such as Comet. - WebSocket @ Wikipedia Why WebSockets Suppose you have to create a web page that shows the statuses of running processes. Without WebSockets you would have to either: Use AJAX with Javascript intervals to request and render the latest state of the processes or Automatically reload the page every x seconds () or Add a message on the page "The stat ## WebSockets, caution required! DevFeed: [WebSockets, caution required!]() Original publisher: [Read original article]() Author: Sam Saffron Published: 2015-12-29T23:25:05Z Content type: opinion Language: en Sources: [Sam Saffron]() Topics: [WebSocket](), [realtime](), [Rails](), [web applications](), [HTTP](), [middleware]() Tags: [http](), [middleware](), [rails](), [realtime](), [rest](), [web-applications](), [websockets]() ### AI overview The article cautions that WebSockets are not automatically a clear win for most realtime web applications. It highlights operational and development concerns, including debugging, logging, profiling, rate limiting, database connection exhaustion, and the choice between WebSockets and REST for client-to-server communication. It suggests WebSockets are more appropriate for specialized high-concurrency cases such as managing 10k interactive console sessions. ### Source excerpt When developers hear that WebSockets are going to land in the near future in Rails they get all giddy with excitement. minions.jpg492x219 23.2 KB But your users don't care if you use WebSockets: Users want "delightful realtime web apps". Developers want "delightfully easy to build realtime web apps". Operations want "delightfully easy to deploy, scale and manage realtime web apps". If WebSockets get us there, great, but it is an implementation detail that comes at high cost. Do we really need ultra high performance, full duplex Client-Server communication? WebSockets provides simple APIs to broadcast information to clients and simple APIs to ship information from the clients to the web server. A realtime channel to send information from the server to the client is very welcome. In fact it is a part of HTTP 1.1. However, a brand new API for shipping information to the server from web browsers introduces a new decision point for developers: When a user posts a message on chat, do I make a RESTful call and POST a message or do I bypass REST and use WebSockets? If I use the new backchannel, how do I debug it? How do I log what is going on? How do I profile it? How do I ensure it does not slow down other traffic to my site? Do I also expose this endpoint in a controller action? How do I rate limit this? How do I ensure my background WebSocket thread does not exhaust my db connection limit? If an API allows hundreds of different connections concurrent access to the database, bad stuff will happen. Introducing this backchannel is not a clear win and comes with many caveats. I do not think the majority of web applications need a new backchannel into the web server. On a technical level you would opt for such a construct if you were managing 10k interactive console sessions on the web. You can transport data more efficiently to the server, in that the web server no longer needs to parse HTTP headers, Rails does not need to do a middleware crawl and so on. But the majority of ## How we scaled Wisembly's infrastructure : moving from our Elephant to RabbitMQ DevFeed: [How we scaled Wisembly's infrastructure : moving from our Elephant to RabbitMQ]() Original publisher: [Read original article]() Author: Guillaume POTIER Published: 2015-07-02T13:31:56Z Content type: article Language: en Sources: [eFounders]() Topics: [RabbitMQ](), [Socket.IO](), [WebSocket](), [real-time](), [MySQL](), [Node.js](), [PHP](), [Redis](), [Software as a service]() Tags: [backend](), [growth](), [mysql](), [node-js](), [php](), [rabbitmq](), [real-time](), [redis](), [saas](), [startup](), [tech](), [websockets]() ### AI overview This article describes how Wisembly evolved its infrastructure as usage grew. It focuses on using RabbitMQ on the backend to communicate between application components and servers, after earlier use of Node.js, Socket.IO, PHP, MySQL, Redis, and WebSockets. ### Source excerpt Hi, I'm Guillaume, I am the CTO and co-founder of Wisembly, a SaaS solution facilitating interactions during your big meetings and events. We recently launched a beta of our new product: Solid to help you make your every-day-meetings more productive and actionable. This is the story of how we improved our performance by changing and adding elements to our stack over the time. I'll particularly focus on how using RabbitMQ on the backend to communicate between different stack and servers improved our life. Where we once were Here are the building blocks for our tech team's philosophy: start small, DRY (Don't Repeat Yourself) and YAGNI (You Ain't Gonna Need It). Back in 2012, when we implemented real-time websockets communications with Node.js and Socket.io, we had a pretty small stack: everything fullstack on Symfony2 with MySQL as single storage and some tiny parts of Backbone.js here and there to power up our application. One year later I presented these slides at the Symfony2 Live Paris 2013 explaining how we implemented Elephant in raw PHP to communicate from our Symfony2 backend with our distant socket.io push server. https://medium.com/media/dfdfc12635e346b3ceb1b2838fda5808/href As I said, our stack was pretty minimal at the time. We didn't feel the need to complexify it for the sake of the socket.io push server. So we looked at websockets and found a pretty way to implement them, connect and emit events with our Open Source library. It did the job, we open-sourced something cool (more than 500 stargazers now and still active!), on our way to live happily ever after :)... Or did we? Where we are now Quite recently, as the business was growing, more and more push events were sent every minute on the various customer meetings we handle daily. For example, we have a specific feature for very interactive seminars where more than 500 users can answer a live poll. Oftentimes, all the attendees submit their answers during the same 10-to-20-second time window, right after ## Websockets In Python + Flask On Heroku DevFeed: [Websockets In Python + Flask On Heroku]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2015-03-10T00:00:00Z Content type: tutorial Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [WebSocket](), [Flask](), [Heroku](), [Python](), [web applications]() Tags: [applications](), [flask](), [heroku](), [python](), [websocket](), [websockets]() ### AI overview This article explains how WebSockets enable two-way communication between clients and servers, then describes getting a basic WebSocket example running with Python's Flask framework hosted on Heroku. ### Source excerpt Websockets change the shape of Internet development by allowing communication both ways -- not only can the client send messages to the server, but with a websocket the server can at any time push information to the client (not just when the client decides to connect to the server). In effect this brings us back to the convenient world of desktop applications where the program and the user interface have two-way communication. ## Websockets Are Not Magical DevFeed: [Websockets Are Not Magical]() Original publisher: [Read original article]() Published: 2015-03-01T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [WebSocket](), [Internet of things](), [Protocol (disambiguation)](), [Art-Net]() Tags: [internet-of-things](), [misconceptions](), [protocol](), [tcp](), [udp](), [websockets]() ### AI overview This commentary examines misconceptions about WebSockets, especially their use in the Internet of Things. It explains that WebSockets add framing overhead, are message-oriented, and provide TCP delivery guarantees and congestion control while avoiding TCP's stream orientation. ### Source excerpt A couple months ago I was talking to a high-ranking engineer from an embedded RTOS vendor. He was insisting that websockets are going to be one of the most important standards for the Internet of Things. Unfortunately, the conversation was cut short too soon for me to get a better understanding of his reasons. ## lsof: can't identify protocol DevFeed: [lsof: can't identify protocol]() Original publisher: [Read original article]() Author: Marek Published: 2012-12-08T23:00:00Z Content type: article Language: en Sources: [Marek Majkowski]() Topics: [WebSocket](), [Linux](), [Library](), [debug]() Tags: [crash](), [debug](), [library](), [linux](), [socket](), [websockets]() ### AI overview The article examines a SockJS-node issue in which enabling WebSockets appears to leak file descriptors and can lead to crashes. It reports that lsof handles the resulting half-closed sockets differently on FreeBSD and Linux, making the issue difficult to debug. ### Source excerpt lsof: can't identify protocol SockJS-node users noticed that the server seems to be leaking file descriptors when websockets are enabled. The problem resulted in the usual crash. Additionally, was producing weird output, with line instead of a normal tcp/ip description. Where it should say something like: it said: The issue was hard to track, but eventually Yury Michurin found a culprit. It was a library which seems to be leaking sockets in state but didn't close them.