J2EE Server Telnet Adapter Protocol Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems lack the ability for a single application server to efficiently serve applications to multiple client devices using different communication protocols, such as telnet and HTTP, leading to redundancy and inefficiency in managing multiple application models and server procedures.
Innovation Solution
A J2EE-compliant application server is configured with a Telnet resource adapter and Message Driven Bean (MDB) to maintain persistent connections with telnet clients, discretizing continuous data streams into discrete requests, allowing the server to communicate with both telnet and HTTP clients using a single application model.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single application server serves multiple client devices using different communication protocols, then device compatibility and infrastructure efficiency are improved, but system complexity and protocol translation requirements increase
Solution Approach 1:
The patent introduces a protocol translation layer that acts as an intermediary between clients using different communication protocols (Telnet, HTTP, HTTPS) and the application server. This translation layer converts protocol-specific requests into a unified internal format, allowing the application server to handle multiple protocols without increasing its inherent complexity. The translation layer absorbs the protocol variation complexity while presenting a consistent interface to the application logic.
Solution Approach 2:
The application server is designed with universal handling capabilities that enable it to process requests from multiple different communication protocols through a single unified interface. The server implements protocol-agnostic request processing logic that can accommodate Telnet, HTTP, and HTTPS clients simultaneously, making the server multi-functional rather than requiring separate specialized servers for each protocol type.
2Reliability
If separate application servers are deployed for different protocols, then protocol-specific optimization is improved, but infrastructure redundancy and resource utilization worsen
Solution Approach 1:
The patent merges multiple protocol-specific server functions into a single unified application server. Instead of deploying separate Telnet servers, HTTP servers, and HTTPS servers, the invention combines all protocol handling capabilities within one server instance. This consolidation eliminates infrastructure redundancy while maintaining the ability to optimize for each protocol through the translation layer's protocol-aware request processing.
3Stability of the object's composition
If legacy applications continue to use persistent connections, then connection stability is improved, but request discretization and state management complexity increase
Solution Approach 1:
The patent extracts the connection management complexity from the application server by implementing a dedicated translation layer that handles persistent connection state management. This layer maintains connection state information and discretizes continuous persistent connection data streams into discrete requests that the application server can process. By separating connection management from application logic, the system maintains stable persistent connections while reducing the application server's state management burden.
Data Source
AI summary
A system and method for serving an application to different types of client devices. The application is served from a J2EE-compliant application server, to clients operating a variety of communication protocols (e.g., HTTP, Telnet). The application is developed according to a single application model, but can be served to heterogeneous clients. The application communicates via a request/response format (e.g., HTTP), thereby requiring clients communicating via other formats or protocols (e.g., Telnet byte streams) to connect to the application via one or more other components of the application server. Illustratively, the application server includes a Telnet resource adapter for maintaining persistent communication connections with Telnet clients, and an EJB (Enterprise Java Bean) configured to discretize continuous Telnet data streams into discrete application requests.