Removing WebSocket Support for a Smoother Editor Experience

By Adam Tue Mar 25 2025 09:18:01 GMT+0800 (Malaysia Time)

In our continuous effort to enhance user experience and optimize performance, we have decided to remove WebSocket support from our editor. This strategic move will provide a smoother, more stable, and more responsive environment for users working on their projects. In this post, we'll delve into why this change was necessary and how it improves the overall experience.


Why We Removed WebSocket Support

WebSockets are a powerful technology that enables real-time, bidirectional communication between a client and a server. However, despite their advantages, they come with several challenges when implemented in an editor environment.


1. Performance Issues


2. Inconsistent Connectivity


3. Increased Server Load


4. Better Compatibility


The Alternative: Optimized HTTP-based Communication

To replace WebSockets, we have implemented a highly optimized HTTP-based long polling system. This new approach ensures:


Technical Explanation of Long Polling

Long polling is a technique where the client makes an HTTP request to the server, and instead of responding immediately, the server holds the request open until new data is available. Once the server responds with the latest data, the client immediately makes another request, creating a near real-time experience without maintaining a persistent connection.

Unlike WebSockets, which keep an open, bidirectional channel, long polling operates over standard HTTP(S) and is inherently more compatible with existing security infrastructures. By leveraging asynchronous request handling and efficient connection management, long polling minimizes redundant traffic while maintaining responsiveness.

Security Benefits of HTTP-based Polling

Security is a crucial factor when choosing a communication method. HTTP-based polling offers several advantages over WebSockets:


By adopting HTTP-based polling, we enhance not just performance but also security, making the editor safer for users.

How This Change Benefits Users


Conclusion

The removal of WebSocket support is a well-thought-out decision to ensure a seamless and efficient editing experience. By switching to optimized HTTP-based communication, we are providing a more stable, reliable, and high-performance environment for our users.

We are committed to continuously improving our platform and appreciate user feedback. If you have any questions or suggestions, feel free to reach out!

Stay tuned for more updates as we keep enhancing your experience!

Back to blog