XML Key-Value Interprocess Message Protocol
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy data base management systems face inefficiencies due to incompatibilities between differing systems, requiring complex interfaces and dedicated connections for data access, which limits user flexibility and increases processing inefficiencies.
Innovation Solution
A generic messaging protocol is introduced, allowing client/server applications to operate on incompatible data bases through the CDACSMesage class and CDACSMsgPropIterator class, enabling message formatting and transmission across communications protocols, supporting various data types and XML, facilitating operations like log-on, update, and fetch without requiring co-location or proprietary knowledge.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proprietary data base management systems use dedicated connections and co-location for data access, then system reliability is improved, but device complexity and ease of operation deteriorate
Solution Approach 1:
The patent introduces a standardized message protocol as an intermediary layer between client applications and legacy database systems. This protocol translates diverse database operations into uniform message formats, eliminating the need for dedicated connections and co-location while maintaining system reliability through standardized communication interfaces.
Solution Approach 2:
The message protocol is designed to be universally applicable across multiple legacy database systems and client platforms. A single protocol implementation can handle various database operations (select, insert, update, delete) across different systems, replacing the need for system-specific interfaces and dedicated connections.
2Reliability
If proprietary data base management systems require dedicated connections for data access, then data security is improved, but ease of operation and user flexibility deteriorate
Solution Approach 1:
The standardized message protocol acts as a secure intermediary that maintains data security through controlled access mechanisms while enabling flexible remote operations. The protocol encapsulates authentication and authorization logic, allowing users to access legacy databases remotely without requiring dedicated physical connections.
3Reliability
If legacy data base systems use incompatible message types for data access, then system reliability is maintained, but productivity and ease of operation deteriorate
Solution Approach 1:
The patent transforms incompatible database message types into a standardized parameter-based message format. By changing the message structure from system-specific formats to a universal parameterized format, the system maintains reliability through accurate data representation while dramatically improving processing efficiency through standardized handling.
Solution Approach 2:
The message protocol enforces homogeneity in message formats across all database operations and systems. All data access requests follow the same structured format with standardized fields for operation type, parameters, and results, eliminating the inefficiencies of handling multiple incompatible message types.
4Reliability
If proprietary data base management systems require specialized command language knowledge, then system reliability is improved, but ease of operation deteriorates
Solution Approach 1:
The message protocol serves as an intermediary that abstracts away proprietary command languages. Client applications communicate using standardized messages rather than system-specific commands, eliminating the need for specialized knowledge while maintaining reliable data access through the protocol's structured format.
Data Source
AI summary
An apparatus for and method of utilizing an existing predefined messaging protocol to convey additional data in application-to-application communication. Instead of utilizing a plurality of the existing predefined messages or defining a new unique message type to convey the needed data, a single preexisting message type is used to define location and format of the data objects to be communicated. The receiving application unpacks these definitions from the single message received and accesses the defined data objects as required.