Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

System and Method of Dynamically Rendering XML-Defined Components as Peer-to-Peer Command Line TCP/IP Services

IP.com Disclosure Number: IPCOM000129298D
Original Publication Date: 2005-Oct-05
Included in the Prior Art Database: 2005-Oct-05
Document File: 1 page(s) / 31K

Publishing Venue

IBM

Abstract

Rather than explicitly implementing/compiling/etc. several components as STAF Command Line TCP/IP services, I had the idea of implementing a single STAF service that would automatically and dynamically render all my other components (defined in XML) as TCP/IP services. I can simply modify the XML or the underlying implementation, and that gets dynamically and instantaneously factored in and exposed to subsequent service calls (remote or otherwise).

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 75% of the total text.

Page 1 of 1

System and Method of Dynamically Rendering XML -Defined Components as Peer-to-Peer Command Line TCP/IP Services

Problem Solved Rather than explicitly implementing/compiling/etc. several components as STAF Command Line TCP/IP services, I had the idea of implementing a single STAF service that would automatically and dynamically render all my other components (defined in XML) as TCP/IP services. I can simply modify the XML or the underlying implementation, and that gets dynamically and instantaneously factored in and exposed to subsequent service calls (remote or otherwise).

Known Solutions Explicitly implementing/compiling/etc. the service interface for each component (1-1 relationship).

Drawbacks of Knows Solutions n number of service implementations (1 per component), thus implementation is much slower and far less cost-effective.

Services are static, rather than dynamic.

If the service interface should change, you would have to re-implement n number of services (1 per component).

Advantages The key advantage is dynamic rendering of TCP/IP services defined in XML. This is much quicker, flexible, and more efficient than implementing services in a 1-1 component relationship.

SERVER

TCP/IP SERVICES

FOO SWAP <one> WITH <other>

FOO2 STACK <stack> PUSH <item> | POP <item>

SELECT SOURCE <src> QUERY <query>

FILTER ADD <name> HOST <host> USER <id> PASSWD <pwd>

SERVER

TCP/IP SERVICES

FOO SWAP <one> WITH <other>

FOO2 STACK <stack> PUSH <item> | POP <item>

SELECT SOURCE <sr...