Problem Statement / scenario : deriving from a problem statement that was encountered at veritas software corp, viz. the company maintains a stack of it products ...in its portfolio. given the norm that each product uses a unique port for communications .... on a installation base at the client or consumers ...for each product installation, expecting the client to open-up a port for external communications ...viz. error reporting or product update's ...make's it a clumsy and cumber some scenario. also refer to the document "opportunity__MIME_design_computing_standard.txt", "opportunity_extensionto_network_protocols_applications.txt", Opportunity a): given the context of the generic nature of the problem ...encountered across the companies. usage of the XML-RPC ...data stream ...than can contain or encode parsable binary-data into the data stream, offer's ideal proposition. having a daemon on the fire-wall ...on the port opened for communication XML aware ...make's it easy to leverage ...NAT or other concepts present in the TCP/IP stack or OSI level. Opportunity b): deriving from a) as also ...further to as envisage in projects.pdf and elsewhere by this individual. using XML-rpc can be used to simulate or emulate ...socket programming in a innovative context ...that can circumvent many a...problem scenario...or limitations encountered in the OSI stack or layer level. Note: The above problem statement having been encountered in various scenarios and detailed in various 'Proof of concepts' as mentioned in 'http://uk.geocities.com/ravivenkatus/projects.pdf' ....apply appropriate 'use-case' modeling, rationalize and arrive at a workable and feasible solution both commercially and techinically viable. ------------------------------------------------------------------------------------------------