WebSocket Serialization Using AMF for Web Content
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web-based communication protocols, such as HTTP, restrict simultaneous communication between clients and servers, introducing latency, while new standards like WebSocket enable full duplex communication, but lack serialization formats for script-based web page content, like JavaScript.
Innovation Solution
Implementing script-based libraries to serialize web page content using ActionScript Message Format (AMF) and transmitting it over a WebSocket channel for efficient, bi-directional communication, allowing for real-time updates and reduced network utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If HTTP protocol is used for web communication, then connection establishment is simple, but communication is restricted and latency is introduced
Solution Approach 1:
The system dynamically switches from static HTTP connection model to dynamic WebSocket full-duplex connection model. The WebSocket protocol enables persistent connections that automatically adapt to real-time communication needs, transitioning from request-response cycles to continuous bidirectional communication channels, thereby reducing latency while maintaining ease of use through automated connection management.
Solution Approach 2:
The patent implements continuous communication by establishing persistent WebSocket connections that remain open throughout the session. Instead of opening and closing connections for each HTTP request, the system maintains continuous communication channels, enabling real-time data exchange without repeated connection establishment and teardown overhead, thus eliminating communication latency.
2Productivity
If WebSocket protocol is used for full duplex communication, then simultaneous communication is enabled, but serialization format compatibility with JavaScript is lacking
Solution Approach 1:
The system changes the data representation parameter by converting JavaScript objects into AMF (ActionScript Message Format) binary serialization. This parameter transformation enables WebSocket compatibility by converting the native JavaScript format into a format that can be efficiently transmitted over WebSocket channels, maintaining full-duplex communication capability while achieving format compatibility.
Solution Approach 2:
The patent introduces AMF serialization as an intermediary layer between JavaScript code and WebSocket communication. This intermediary converts JavaScript objects into AMF binary format for WebSocket transmission, and vice versa for reception, thereby enabling full-duplex communication while resolving the format compatibility issue between JavaScript and WebSocket protocols.
3Reliability
If web page content is transmitted in raw format, then data integrity is maintained, but network utilization is high and communication speed is reduced
Solution Approach 1:
The system changes the data encoding parameter from raw text format to AMF binary serialization. This parameter transformation compresses the data representation, reducing the number of bits required to transmit the same information. The binary AMF format maintains data integrity through structured serialization while significantly reducing network bandwidth consumption and improving communication speed.
Data Source
AI summary
One illustrative embodiment involves executing one or more script-based libraries to serialize an object comprising content that is displayed on a web page in a web browser on a client device. The serialization comprises identifying a string representing raw bytes that identify the object. The embodiment also involves establishing a connection between the client device and a server device, wherein the connection is a full duplex communication channel for communication between the client device and the server device. The embodiment further involves sending, from the client device, the serialized object over the full duplex communication channel to the server device and receiving the serialized object from the server device. The serialized object from the server device is serialized according to the string representing raw bytes. The embodiment further involves deserializing the object from the server device.


