US20070256086A1 - Discovery and integration of jini services in non-java clients - Google Patents

Discovery and integration of jini services in non-java clients Download PDF

Info

Publication number
US20070256086A1
US20070256086A1 US11/685,117 US68511707A US2007256086A1 US 20070256086 A1 US20070256086 A1 US 20070256086A1 US 68511707 A US68511707 A US 68511707A US 2007256086 A1 US2007256086 A1 US 2007256086A1
Authority
US
United States
Prior art keywords
application
application service
client
programming interface
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/685,117
Inventor
Krishnamurthy Srinivasan
Edala Narasimha
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corp filed Critical Intel Corp
Priority to US11/685,117 priority Critical patent/US20070256086A1/en
Assigned to INTEL CORPORATION reassignment INTEL CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NARASIMHA, EDALA R., SRINIVASAN, KRISHNAMURTHY
Publication of US20070256086A1 publication Critical patent/US20070256086A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/465—Distributed object oriented systems

Definitions

  • Jini is an established specification which allows application services to announce their availability dynamically. Users of services can dynamically find an application service using Jini. Examples can include services providing freight rates, stock quotes, price inventory levels for products or modules (e.g., calculators) for applications.
  • Jini (TM) operates by registering services, and responding to client inquiries about one of these services. Jini (TM) also provides proxy code to the client allowing the client to communicate with the services. In this way, Jini (TM) acts as a broker between the client and the existing services.
  • Jini has been written in a way such that it can only be used by services written in Java. Many non-Java services (“legacy” services), however exist. These services cannot operate through Jini (TM).
  • FIG. 1 shows an operation of the bridge of the present system, forming an interface between non Java services and a Jini (TM) broker;
  • TM Jini
  • FIG. 2 shows a flowchart of operation of the system
  • FIG. 3 shows an example of encapsulating CORBA component.
  • the present application defines a bridge between non Java services and a client which is requesting such services. More specifically, the bridge provides a code generator to generate a proxy code that wraps the non-Java object, and hence enables communication between the client and the service.
  • a surrogate object publishes information about the service and proxy. The surrogate object maintains this information using the Jini (TM) protocol. In this way, Jini (TM) can be used in its normal way, but can used as a broker for non-Java services. Jini stores the code, by indexing the code directly, or by indexing proxy code.
  • TM Java Application Programming Interface
  • API Java Application Programming Interface
  • a Java service normally publishes itself or its proxy to Jini (TM), along with a set of search attributes that can be used by services that are searching among the services.
  • TM Jini
  • a non Java service 100 is published, using a Java compliant “wrapper”, as described.
  • the wrapper acts like Java proxy code, and points to the non Java service, in the same way that Java proxy code would point to the Java service.
  • a GUI Graphic User Interface
  • a user allows a user to point and click the location of a service interface file representing the non-Java component, here an ActiveX component.
  • this may be an OCX file for an activeX component 100 as shown in FIG. 1 .
  • the point and click operation is used to instruct the bridge 110 to publish the service.
  • the bridge 110 operates as shown in the flowchart of FIG. 2 .
  • the bridge performs run-time introspection of the service component 100 .
  • the bridge identifies the methods/functionality within the service. This can use dynamic inspection and/or keywords, metatags, or other kinds of application inspection.
  • these results are stated as a list of different functionalities and other relevant information.
  • FIG. 1 shows the functionalities graphically as 120 . This list will be used to form the eventual code.
  • this system forms middle tier tunneling proxy code 140 to form a bridge between the client and the service.
  • Other information obtained from introspection at 210 is used to generate search attributes. These form keywords which are used to supplement the keyword repository in Jini (TM).
  • TM Java
  • a user may also specify additional keywords in the Graphical User Interface (GUI).
  • GUI Graphical User Interface
  • Jini stores the proxy objects and a set of search attribute objects shown as 152 , 154 , shown in FIG. 1 .
  • the Jini (TM) service is shown as 150 .
  • a client or a service-proxy for the client, makes a call to the backend service wrapper object.
  • the wrapper object redirects the call to the actual Component Object Model (“COM”) or CORBA component.
  • COM Component Object Model
  • CORBA Component Object Model
  • the bridge 110 generates code that redirects the calls to the service 100 .
  • the generated code may be Java proxy code.
  • the bridge receives a Jini (TM) lease object based on the successful registration of the Jini (TM) object.
  • the lease object shown as 142 keeps the object definition up-to-date.
  • the bridge renews the lease from time to time, thereby insuring up-to-date information in Jini (TM).
  • a service is published to Jini (TM) in the following way.
  • the service is serialized as a Java object, if it can be so serialized.
  • Other, non Java compliant services are packaged as described above.
  • Services which are incapable of being serialized into Jini (TM) may publish their proxies instead. Constraints such as heaviness, native dependability, and the like may prevent the service from directly publishing to Jini (TM).
  • the proxy is a serializable lightweight Java object that acts as the service delegate.
  • the proxies act as middle tiered objects allowing access of services on the back end.
  • the object or proxy is sent to Jini (TM), along with a set of search attributes. Once the Java objects have been transported to Jini (TM), they are delivered to clients responsive to notifications of service matches.
  • Another aspect is to allow publishing either Jini or non Jini services. Any service that is capable of serialized in itself, and publishing itself to Jini (TM), would do so directly. This enables clients to directly use the service objects.
  • Non Jini (TM) services may not have a proxy, or such a proxy may need to be generated as part of the Jini (TM) registration process.
  • Certain distributed application environments allow services to register with them through an identifier.
  • One example is a GUID key for COM components.
  • FIG. 3 shows how the system could publish and obtain different information.
  • a service 300 e.g., a CORBA service is coupled to the code generator 305 which provides an wrapper around the CORBA shown as 310 .
  • the CORBA code appears to the broker or proxy as Java code, i.e., it is no different like any other Java application.
  • the application is published with the Jini (TM) broker.
  • FIG. 3B shows a client, which is a non Java client such as an Excel(TM) client asking for services.
  • the request for services is also placed in a wrapper at 335 and placed to Jini (TM). Jini (TM) returns the request.
  • TM Jini

Abstract

A system of forming a bridge between non Java services and a Jini (™) interface. A non Java service is encapsulated using special code which makes it look like a Java service. Other aspects are also automatically formed. The Java service is automatically published with a broker such as a Jini (™) broker.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation application of and claims priority to U.S. patent application Ser. No. 09/734,333, filed Nov. 30, 2000. The disclosure of the prior application is considered part of (and is incorporated by reference in) the disclosure of this application.
    • BACKGROUND
  • Jini (™) is an established specification which allows application services to announce their availability dynamically. Users of services can dynamically find an application service using Jini. Examples can include services providing freight rates, stock quotes, price inventory levels for products or modules (e.g., calculators) for applications. Jini (™) operates by registering services, and responding to client inquiries about one of these services. Jini (™) also provides proxy code to the client allowing the client to communicate with the services. In this way, Jini (™) acts as a broker between the client and the existing services.
  • Jini (™) has been written in a way such that it can only be used by services written in Java. Many non-Java services (“legacy” services), however exist. These services cannot operate through Jini (™).
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • These and other aspects will now be described in detail with reference to the accompanying drawings.
  • FIG. 1 shows an operation of the bridge of the present system, forming an interface between non Java services and a Jini (™) broker;
  • FIG. 2 shows a flowchart of operation of the system;
  • FIG. 3 shows an example of encapsulating CORBA component.
    • DETAILED DESCRIPTION
  • The present application defines a bridge between non Java services and a client which is requesting such services. More specifically, the bridge provides a code generator to generate a proxy code that wraps the non-Java object, and hence enables communication between the client and the service. A surrogate object publishes information about the service and proxy. The surrogate object maintains this information using the Jini (™) protocol. In this way, Jini (™) can be used in its normal way, but can used as a broker for non-Java services. Jini stores the code, by indexing the code directly, or by indexing proxy code.
  • The current Jini (™) interface will register services which have a Java Application Programming Interface (“API”). Services without a Java API cannot be registered with Jini (™). While the present application specifically describes using Jini (™), it should be understood that any service requiring a Java API could be similarly used.
  • The operation is shown in FIG. 1. A Java service normally publishes itself or its proxy to Jini (™), along with a set of search attributes that can be used by services that are searching among the services. According to the present system, a non Java service 100 is published, using a Java compliant “wrapper”, as described. The wrapper acts like Java proxy code, and points to the non Java service, in the same way that Java proxy code would point to the Java service.
  • A GUI (Graphical User Interface) allows a user to point and click the location of a service interface file representing the non-Java component, here an ActiveX component. For example, this may be an OCX file for an activeX component 100 as shown in FIG. 1. The point and click operation is used to instruct the bridge 110 to publish the service.
  • The bridge 110 operates as shown in the flowchart of FIG. 2. At 200, the bridge performs run-time introspection of the service component 100. At 210, the bridge identifies the methods/functionality within the service. This can use dynamic inspection and/or keywords, metatags, or other kinds of application inspection. At 220, these results are stated as a list of different functionalities and other relevant information. FIG. 1 shows the functionalities graphically as 120. This list will be used to form the eventual code.
  • At 230, this system forms middle tier tunneling proxy code 140 to form a bridge between the client and the service. Other information obtained from introspection at 210 is used to generate search attributes. These form keywords which are used to supplement the keyword repository in Jini (™). In addition to the keywords identified by introspection, a user may also specify additional keywords in the Graphical User Interface (GUI).
  • Jini (™) stores the proxy objects and a set of search attribute objects shown as 152, 154, shown in FIG. 1.
  • The Jini (™) service is shown as 150. A client, or a service-proxy for the client, makes a call to the backend service wrapper object. The wrapper object redirects the call to the actual Component Object Model (“COM”) or CORBA component. Each time such a call is made, the bridge 110 generates code that redirects the calls to the service 100. The generated code may be Java proxy code.
  • At 260, the bridge receives a Jini (™) lease object based on the successful registration of the Jini (™) object. The lease object shown as 142 keeps the object definition up-to-date. The bridge renews the lease from time to time, thereby insuring up-to-date information in Jini (™).
  • A service is published to Jini (™) in the following way. First, the service is serialized as a Java object, if it can be so serialized. Other, non Java compliant services are packaged as described above. Services which are incapable of being serialized into Jini (™) may publish their proxies instead. Constraints such as heaviness, native dependability, and the like may prevent the service from directly publishing to Jini (™). The proxy is a serializable lightweight Java object that acts as the service delegate. The proxies act as middle tiered objects allowing access of services on the back end. The object or proxy is sent to Jini (™), along with a set of search attributes. Once the Java objects have been transported to Jini (™), they are delivered to clients responsive to notifications of service matches.
  • Another aspect is to allow publishing either Jini or non Jini services. Any service that is capable of serialized in itself, and publishing itself to Jini (™), would do so directly. This enables clients to directly use the service objects.
  • Non Jini (™) services may not have a proxy, or such a proxy may need to be generated as part of the Jini (™) registration process.
  • Certain distributed application environments allow services to register with them through an identifier. One example is a GUID key for COM components.
  • As an example of operation, FIG. 3 shows how the system could publish and obtain different information. A service 300, e.g., a CORBA service is coupled to the code generator 305 which provides an wrapper around the CORBA shown as 310. Once in the wrapper, the CORBA code appears to the broker or proxy as Java code, i.e., it is no different like any other Java application. At 315, the application is published with the Jini (™) broker. FIG. 3B, shows a client, which is a non Java client such as an Excel(™) client asking for services. At 330, the request for services is also placed in a wrapper at 335 and placed to Jini (™). Jini (™) returns the request.
  • Although only a few embodiments have been disclosed in detail above, other modifications are possible.

Claims (19)

1. A system comprising:
a collection of clients that receive services;
a client/server broker configured to register application services that have a first application programming interface and identify the registered application services to the clients;
a first application service that has the first application programming interface and is configured to publish an announcement of an availability of the first application service;
a second application service that has a second application programming interface and is configured to publish an announcement of an availability of the second application service; and
a bridge configured to wrap the announcement of the availability of the second application service in a wrapper that is compliant with the first application programming interface so that the client/server broker can register both the first application service and the second application service.
2. The system of claim 1, wherein the bridge comprises a proxy code generator and is configured to wrap the announcement of the availability of the second application service in the proxy code.
3. The system of claim 1, wherein the bridge is configured to inspect the second application service to identify functionality of the second application service and to identify the functionality to the client/server broker.
4. The system of claim 3, wherein the bridge is configured to inspect the second application service using dynamic inspection.
5. The system of claim 1, wherein the client/server broker is configured to identify functionality of the registered application services to the clients.
6. The system of claim 1, further comprising a memory associated with the client/server broker, wherein the memory includes information describing the registered application services.
7. The system of claim 6, wherein the information describing the registered application services comprises a keyword repository.
8. The system of claim 1, wherein:
the client/server broker comprises a Jini™ interface;
the first application programming interface comprises a Java™ application programming interface; and
the second application programming interface comprises a non-Java™ application programming interface.
9. The system of claim 1, further comprising a third application service proxy that has the first application programming interface and is configured to publish an announcement of an availability of the first application service.
10. A method comprising:
inspecting an application service;
identifying that the application service has a functionality;
forming proxy code describing the identified functionality; and
forming a bridge between the application service and a client using the proxy code.
11. The method of claim 10, wherein forming the proxy code comprises middle tier tunneling proxy code.
12. The method of claim 10, wherein forming the proxy code comprises forming Java™ proxy code.
13. The method of claim 10, wherein forming the bridge between the application service and the client comprises registering the application service with a client/server broker.
14. The method of claim 13, wherein:
the client/server broker is configured to register application services that have a first application programming interface; and
registering the application service comprises wrapping an announcement of an availability of the application service in a wrapper that is compliant with the first application programming interface.
15. The method of claim 14, further comprising receiving a lease object from the client/server broker indicating that the application service has been registered.
16. The method of claim 14, wherein:
the client/server broker comprises a Jini™ interface; and
the first application programming interface comprises a Java™ application programming interface.
17. The method of claim 10, further comprising:
generating a collection of search attributes based on results of inspecting the application service; and
making the collection of search attributes available to the client/server broker.
18. The method of claim 10, wherein inspecting the application service comprises dynamically inspecting the application service.
19. The method of claim 10, wherein inspecting the application service comprises identifying a metatag associated with the application service.
US11/685,117 2000-11-30 2007-03-12 Discovery and integration of jini services in non-java clients Abandoned US20070256086A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/685,117 US20070256086A1 (en) 2000-11-30 2007-03-12 Discovery and integration of jini services in non-java clients

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/734,333 US7191453B2 (en) 2000-11-30 2000-11-30 Discovery and integration of Jini services in non-Java clients
US11/685,117 US20070256086A1 (en) 2000-11-30 2007-03-12 Discovery and integration of jini services in non-java clients

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/734,333 Continuation US7191453B2 (en) 2000-11-30 2000-11-30 Discovery and integration of Jini services in non-Java clients

Publications (1)

Publication Number Publication Date
US20070256086A1 true US20070256086A1 (en) 2007-11-01

Family

ID=24951246

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/734,333 Expired - Fee Related US7191453B2 (en) 2000-11-30 2000-11-30 Discovery and integration of Jini services in non-Java clients
US11/685,117 Abandoned US20070256086A1 (en) 2000-11-30 2007-03-12 Discovery and integration of jini services in non-java clients

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/734,333 Expired - Fee Related US7191453B2 (en) 2000-11-30 2000-11-30 Discovery and integration of Jini services in non-Java clients

Country Status (1)

Country Link
US (2) US7191453B2 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013101770A1 (en) * 2011-12-29 2013-07-04 Oracle International Corporation Virtual channel for embedded process communication
US10572297B2 (en) 2017-03-31 2020-02-25 International Business Machines Corporation Attach an interpreter-based TPM into a cluster of inter-connected multi-process based compiler-based TPMs to achieve global transaction

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030192038A1 (en) * 2002-04-09 2003-10-09 Thomas Hagmann Linking data objects to a project development system
US7114148B2 (en) * 2002-09-30 2006-09-26 Microsoft Corporation Runtime services for network software platform
US7424722B2 (en) * 2003-08-29 2008-09-09 International Business Machines Corporation Method and system for creating a dynamic OGSI service proxy framework using runtime introspection of an OGSI service
US7428729B2 (en) * 2004-01-30 2008-09-23 International Business Machines Corporation Methods, systems, and computer program products for integrating legacy applications into a platform-independent environment
US7168513B2 (en) * 2004-02-27 2007-01-30 The Regents Of The University Of California Dynamic legged robot
US7496585B2 (en) * 2004-04-23 2009-02-24 International Business Machines Corporation Methods and apparatus for discovering data providers satisfying provider queries
US7487142B2 (en) 2004-06-10 2009-02-03 International Business Machines Corporation Methods and apparatus for specifying and processing descriptive queries for data sources
US8141070B2 (en) * 2005-05-24 2012-03-20 International Business Machines Corporation Bridging class loader name spaces
US8762976B2 (en) * 2007-03-09 2014-06-24 Microsoft Corporation Static extensibility models with dynamic languages and scripts
US8560713B2 (en) * 2008-07-31 2013-10-15 Sap Ag Method and system for mediating enterprise service access for smart devices
US20110165667A1 (en) * 2009-07-02 2011-07-07 The University Of Chicago Method and System for Converting Electricity Into Alternative Energy Resources
US11809839B2 (en) 2022-01-18 2023-11-07 Robert Lyden Computer language and code for application development and electronic and optical communication

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5913061A (en) * 1997-01-08 1999-06-15 Crossroads Software, Inc. Modular application collaboration
US5995506A (en) * 1996-05-16 1999-11-30 Yamaha Corporation Communication system
US6230160B1 (en) * 1997-07-17 2001-05-08 International Business Machines Corporation Creating proxies for distributed beans and event objects
US6253122B1 (en) * 1999-06-14 2001-06-26 Sun Microsystems, Inc. Software upgradable dashboard
US6253367B1 (en) * 1998-11-18 2001-06-26 Micrografx, Inc. Method and system for transforming dynamic content for use on the internet
US6263498B1 (en) * 1998-12-03 2001-07-17 International Business Machines Corporation Method and apparatus for enabling server side distributed object modification
US6330711B1 (en) * 1998-07-30 2001-12-11 International Business Machines Corporation Method and apparatus for dynamic application and maintenance of programs
US6430570B1 (en) * 1999-03-01 2002-08-06 Hewlett-Packard Company Java application manager for embedded device
US6442748B1 (en) * 1999-08-31 2002-08-27 Accenture Llp System, method and article of manufacture for a persistent state and persistent object separator in an information services patterns environment
US6473759B1 (en) * 1999-01-12 2002-10-29 International Business Machines Corporation Method and system for accessing java applications
US6594700B1 (en) * 1999-06-14 2003-07-15 International Business Machines Corporation System and method for implementing a universal service broker interchange mechanism
US6609158B1 (en) * 1999-10-26 2003-08-19 Novell, Inc. Component architecture in a computer system
US6654801B2 (en) * 1999-01-04 2003-11-25 Cisco Technology, Inc. Remote system administration and seamless service integration of a data communication network management system
US6675159B1 (en) * 2000-07-27 2004-01-06 Science Applic Int Corp Concept-based search and retrieval system
US6859931B1 (en) * 1999-01-05 2005-02-22 Sri International Extensible software-based architecture for communication and cooperation within and between communities of distributed agents and distributed objects

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5995506A (en) * 1996-05-16 1999-11-30 Yamaha Corporation Communication system
US5913061A (en) * 1997-01-08 1999-06-15 Crossroads Software, Inc. Modular application collaboration
US6230160B1 (en) * 1997-07-17 2001-05-08 International Business Machines Corporation Creating proxies for distributed beans and event objects
US6330711B1 (en) * 1998-07-30 2001-12-11 International Business Machines Corporation Method and apparatus for dynamic application and maintenance of programs
US6253367B1 (en) * 1998-11-18 2001-06-26 Micrografx, Inc. Method and system for transforming dynamic content for use on the internet
US6263498B1 (en) * 1998-12-03 2001-07-17 International Business Machines Corporation Method and apparatus for enabling server side distributed object modification
US6654801B2 (en) * 1999-01-04 2003-11-25 Cisco Technology, Inc. Remote system administration and seamless service integration of a data communication network management system
US6859931B1 (en) * 1999-01-05 2005-02-22 Sri International Extensible software-based architecture for communication and cooperation within and between communities of distributed agents and distributed objects
US6473759B1 (en) * 1999-01-12 2002-10-29 International Business Machines Corporation Method and system for accessing java applications
US6430570B1 (en) * 1999-03-01 2002-08-06 Hewlett-Packard Company Java application manager for embedded device
US6594700B1 (en) * 1999-06-14 2003-07-15 International Business Machines Corporation System and method for implementing a universal service broker interchange mechanism
US6253122B1 (en) * 1999-06-14 2001-06-26 Sun Microsystems, Inc. Software upgradable dashboard
US6442748B1 (en) * 1999-08-31 2002-08-27 Accenture Llp System, method and article of manufacture for a persistent state and persistent object separator in an information services patterns environment
US6609158B1 (en) * 1999-10-26 2003-08-19 Novell, Inc. Component architecture in a computer system
US6675159B1 (en) * 2000-07-27 2004-01-06 Science Applic Int Corp Concept-based search and retrieval system

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013101770A1 (en) * 2011-12-29 2013-07-04 Oracle International Corporation Virtual channel for embedded process communication
US8856805B2 (en) 2011-12-29 2014-10-07 Oracle International Corporation Virtual channel for embedded process communication
CN104094234A (en) * 2011-12-29 2014-10-08 甲骨文国际公司 Virtual channel for embedded process communication
US8863126B2 (en) 2011-12-29 2014-10-14 Oracle International Corporation Java virtual machine embedded in a native mobile application
US8978023B2 (en) 2011-12-29 2015-03-10 Oracle International Corporation Canonical mechanism for securely assembling features into a mobile application
US10572297B2 (en) 2017-03-31 2020-02-25 International Business Machines Corporation Attach an interpreter-based TPM into a cluster of inter-connected multi-process based compiler-based TPMs to achieve global transaction

Also Published As

Publication number Publication date
US20020092000A1 (en) 2002-07-11
US7191453B2 (en) 2007-03-13

Similar Documents

Publication Publication Date Title
US20070256086A1 (en) Discovery and integration of jini services in non-java clients
Becker et al. Base-a micro-broker-based middleware for pervasive computing
US7475058B2 (en) Method and system for providing a distributed querying and filtering system
US7412518B1 (en) Method and apparatus for proximity discovery of services
US6862594B1 (en) Method and apparatus to discover services using flexible search criteria
US6868447B1 (en) Mechanism and apparatus for returning results of services in a distributed computing environment
US6970869B1 (en) Method and apparatus to discover services and negotiate capabilities
US6792466B1 (en) Trusted construction of message endpoints in a distributed computing environment
US8135796B1 (en) Mechanism and apparatus for accessing and addressing services in a distributed computing environment
US6789077B1 (en) Mechanism and apparatus for web-based searching of URI-addressable repositories in a distributed computing environment
US6918084B1 (en) Spawning new repository spaces using information provided in advertisement schema messages
US7395333B1 (en) Method and apparatus to obtain negotiated service advertisement
US8789073B2 (en) Proxy object creation and use
US6973493B1 (en) Mechanism and apparatus for security of newly spawned repository spaces in a distributed computing environment
US8239877B2 (en) Pre-population of meta data cache for resolution of data marshaling issues
US20070011126A1 (en) Service-oriented architecture
US7370091B1 (en) Method and apparatus for obtaining space advertisements
EP1321853A2 (en) Dynamic component transfer based on resource negotiations between computer systems
US7689430B2 (en) Access to web services
JP2002505466A (en) Remote method invocation method and apparatus
US20050198206A1 (en) Method and apparatus for dynamically selecting functionally equivalent Web services through a single autonomic proxy
US7319979B2 (en) Dynamically interacting with an internet service using a client-specified communication proxy and protocol
KR100901281B1 (en) Method for ubiquitous web service
US20050198336A1 (en) Methods and apparatuses for automatic adaptation of different protocols
Harrison et al. Introduction to OGC web services

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTEL CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SRINIVASAN, KRISHNAMURTHY;NARASIMHA, EDALA R.;REEL/FRAME:019569/0868

Effective date: 20010328

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION