Shared service messaging models

• US 20020010781A1
• Filed: 01/02/2001
• Published: 01/24/2002
• Est. Priority Date: 12/30/1999
• Status: Abandoned Application

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Tuatini, Jeffrey Taihana
• Application Number:
  US09/755,599
• Publication Number:
  US 20020010781A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

An application architecture is provided in which applications have action handler components to service requests from clients and view handler components to format responses to the clients. Application component can access functionality provided by remote shared services via a local messaging service of the application. To communicate with a shared service, the local messaging service identifies a proxy of the shared service and sends a message to the proxy for forwarding to the shared service. The local messaging service can receive requests to communicate using different messaging models. At least some of the remote services support multiple messaging models, some by having distinct proxies for each of the supported messaging models. The local messaging service will communicate with an appropriate proxy to communicate using a specified messaging models, and may simulate use of the messaging model if a proxy supporting the messaging model is not available.

Claims

1. A method in a computer system for executing applications to communicate with remote shared service providers using multiple messaging models, each remote shared service provider having for each of the multiple messaging models a distinct associated proxy component able to communicate with that remote shared service provider using that messaging model, the method comprising:

under control of a first of the executing applications having a local messaging component able to communicate with each of the associated proxy components,

notifying the local messaging component to send a specified first message to a specified first remote shared service provider using a specified first messaging model; and

under control of the local messaging component, sending the first message to the first remote shared service provider using the first messaging model by,

retrieving configuration information for the first remote shared service provider that identifies a first proxy component that is associated with the first remote shared service provider and is able to communicate with the first remote shared service provider using the first messaging model;

when the first proxy component is not already instantiated within the first application, instantiating the first proxy component;

sending a message to the first proxy component requesting that the first proxy component send the first message to the first remote shared service provider using the first messaging model; and

receiving a response from the first remote shared service provider via the first proxy component, and notifying the first application of the received response, so that an application can communicate with any of the remote shared service providers using any of the multiple messaging models via a local messaging component that identifies and uses a proxy component able to communicate with a specified remote shared service provider using a specified messaging model.

2. The method of claim 1 including, under control of the first application, communicating with the first remote shared service provider using a second messaging model by:

notifying the local messaging component to send a specified second message to the first remote shared service provider using a specified second messaging model; and

under control of the local messaging component, sending the second message to the first remote shared service provider using the second messaging model by,

retrieving configuration information for the first remote shared service provider that identifies a second proxy component that is associated with the first remote shared service provider and is able to communicate with the first remote shared service provider using the second messaging model, the second proxy component distinct from the first proxy component;

when the second proxy component is not already instantiated within the first application, instantiating the second proxy component;

sending a message to the second proxy component requesting that the second proxy component send the second message to the first remote shared service provider using the second messaging model; and

receiving a response from the first remote shared service provider via the second proxy component, and notifying the first application of the received response.

3. The method of claim 1 including, under control of the first application, communicating with a second of the remote shared service providers using the first messaging model by:

notifying the local messaging component to send a specified second message to a specified second remote shared service provider using the first messaging model; and

under control of the local messaging component, sending the second message to the second remote shared service provider using the first messaging model by,

retrieving configuration information for the second remote shared service provider that identifies a second proxy component that is associated with the second remote shared service provider and is able to communicate with the second remote shared service provider using the first messaging model, the second proxy component distinct from the first proxy component;

when the second proxy component is not already instantiated within the first application, instantiating the second proxy component;

sending a message to the second proxy component requesting that the second proxy component send the second message to the second remote shared service provider using the first messaging model; and

receiving a response from the second remote shared service provider via the second proxy component, and notifying the first application of the received response.

4. The method of claim 1 including:

under control of a second of the executing applications having a second local messaging component able to communicate with each of the associated proxy components,

notifying the second local messaging component to send a specified second message to the first remote shared service provider using the first messaging model; and

under control of the second local messaging component, sending the second message to the first remote shared service provider using the first messaging model by,

retrieving the configuration information for the first remote shared service provider that identifies the first proxy component;

instantiating the first proxy component;

sending a message to the first proxy component requesting that the first proxy component send the second message to the first remote shared service provider using the first messaging model; and

receiving a response from the first remote shared service provider via the first proxy component, and notifying the second application of the received response.

5. The method of claim 1 including, under control of the first proxy component:

receiving the sent message from the local messaging component;

identifying based on the received message that the first messaging model is to be used for communicating;

sending the message to the first remote shared service provider;

receiving a response from the first remote shared service provider; and

sending the received response to the local messaging component using the first messaging model.

6. The method of claim 5 including, under control of the first remote shared service provider:

receiving the message sent from the first proxy component;

performing processing associated with the received message, the processing generating a response; and

sending the generated response to the first proxy component.

7. The method of claim 1 wherein the specifying of the first remote shared service provider in the notifying of the local messaging component includes a unique name for the first remote shared service provider, and wherein the retrieving of the configuration information for the first remote shared service provider is based at least in part on the included name.

8. The method of claim 1 wherein the specified first message is a request for one of multiple distinct services provided by the first remote shared service provider, wherein the notifying of the local messaging component further identifies a name of the one service, and wherein the identifying of the first proxy component from the retrieved configuration information is based at least in part on the identified name of the one service.

9. The method of claim 1 wherein the first proxy component is a software module, and wherein the instantiating of the first proxy component includes executing the software module.

10. The method of claim 1 wherein the first proxy component is an instance of an object class, and wherein the instantiating of the first proxy component includes creating the instance.

11. The method of claim 10 wherein the sending of the message to the first proxy component includes invoking an interface method of the first proxy component instance.

12. The method of claim 11 wherein the first proxy component instance has distinct interface methods corresponding to each of the messaging models with which the first proxy component is able to communicate, and wherein the request that the first proxy component use the first messaging model is based on selecting the interface method of the first proxy component that corresponds to the first messaging model as the interface method to be invoked.

13. The method of claim 11 wherein the request that the first proxy component use the first messaging model is based on specifying a parameter during the invoking of the interface method such that the specified parameter corresponds to the first messaging model.

14. The method of claim 1 wherein the local messaging component is an instance of an object class.

15. The method of claim 14 wherein the notifying of the local messaging component includes invoking an interface method of the local messaging component instance.

16. The method of claim 15 wherein the local messaging component instance has distinct interface methods corresponding to each of the messaging models with which the local messaging component is able to communicate, and wherein the specifying of the first messaging model during the notifying of the local messaging component is based on selecting the interface method of the local messaging component that corresponds to the first messaging model as the interface method to be invoked.

17. The method of claim 15 wherein the specifying of the first messaging model during the notifying of the local messaging component is based on specifying a parameter during the invoking of the interface method such that the specified parameter corresponds to the first messaging model.

18. The method of claim 1 wherein the configuration information is retrieved from storage via a directory service using a unique name of the first remote shared service provider.

19. The method of claim 18 including, before the executing of the first application, storing the configuration information using the directory service.

20. The method of claim 1 wherein the retrieved configuration information includes initialization information for the first proxy component, and wherein the instantiating of the first proxy component includes providing the initialization information to the first proxy component for use as part of its initialization.

21. The method of claim 1 wherein the message sent to the first proxy component is a version of the specified first message that is transformed under the control of the local messaging component before the sending.

22. The method of claim 1 wherein the first application includes multiple action handler components each for responding to requests from external clients with responses generated in a format used by the action handler component, and wherein the notifying of the local messaging component to send the specified first message is prompted by a request generated by one of the action handler components.

23. The method of claim 22 wherein the first application includes multiple view handler components each for transforming generated responses in formats used by action handler components into formats compatible with external clients, and including, after the notifying of the received response from the first remote shared service provider, using one of the view handler components to transform the received response into a format compatible with an external client.

24. The method of claim 1 wherein the first messaging model is synchronous communication.

25. The method of claim 1 wherein the first messaging model is asynchronous communication.

26. The method of claim 1 wherein the first messaging model is request-reply communication.

27. The method of claim 1 wherein the first messaging model is one-way communication.

28. The method of claim 1 wherein the first messaging model is store-and-forward communication.

29. The method of claim 1 wherein the first messaging model is queued communication.

30. The method of claim 1 wherein the first messaging model is publish-subscribe communication.

31. The method of claim 1 wherein the first messaging model is broadcast communication.

32. The method of claim 1 wherein the first messaging model is conversational communication.

33. The method of claim 1 wherein the first remote shared service provider does not provide a response that corresponds to the first messaging model, and wherein the first proxy component generates the response.

34. The method of claim 1 wherein the received response from the first remote shared service provider does not correspond to the first messaging model, and wherein the local messaging component generates a response that corresponds to the first messaging model to be used for the notifying of the first application.

35. A computer-readable medium whose contents cause a computing device to execute applications able to communicate with remote shared service providers using multiple messaging models, each remote shared service provider having for each of the multiple messaging models a distinct associated proxy component able to communicate using that messaging model, by:

under control of a first of the executing applications having a local messaging component able to communicate with each of the associated proxy components,

notifying the local messaging component to send a specified first message to a specified first remote shared service provider using a specified first messaging model; and

under control of the local messaging component, sending the first message to the first remote shared service provider using the first messaging model by,

retrieving configuration information for the first remote shared service provider that identifies a first proxy component that is associated with the first remote shared service provider and is able to communicate using the first messaging model;

when the first proxy component is not already instantiated, instantiating the first proxy component; and

sending a message to the first proxy component requesting that the first messaging model be used by the first proxy component in sending the first message to the first remote shared service provider.

36. A computing device for executing applications to communicate with remote shared service providers using multiple messaging models, each remote shared service provider having for each of the multiple messaging models a distinct associated proxy component able to communicate with that remote shared service provider using that messaging model, comprising:

a first application capable of, during execution, notifying a local messaging component able to communicate with each of the associated proxies to send a specified first message to a specified first remote shared service provider using a specified first messaging model; and

the local messaging component capable of, during execution, retrieving configuration information for the first remote shared service provider that identifies a first proxy component that is associated with the first remote shared service provider and is able to communicate with the first remote shared service provider using the first messaging model, instantiating the first proxy component, and sending a message to the first proxy component requesting that the first proxy component send the first message to the first remote shared service provider using the first messaging model.

37. A method in a computer system for an executing application to communicate with remote services using multiple messaging models, each remote service having for each of the multiple messaging models an associated proxy able to communicate using that messaging model, the method comprising:

for each of multiple of the remote services,

notifying a local messaging service to send a message to the remote service using a specified messaging model;

under control of the local messaging service,

identifying the associated proxy for the remote service that is able to communicate with the remote service using the specified messaging model; and

sending the message to the identified proxy for communication to the remote service using the specified messaging model; and

receiving a response to the sent message from the local messaging service in accordance with the specified messaging model.

38. The method of claim 37 including, under control of each of the proxies:

receiving the sent message from the local messaging service; and

sending the message to the remote service in a manner specific to the remote service.

39. The method of claim 37 wherein each of the proxies are object instances, and including creating each of the proxies when the proxy is first identified.

40. The method of claim 39 wherein the sending of the messages to the proxies includes invoking interface methods of the instances.

41. The method of claim 40 wherein at least one of the proxies has distinct interface methods corresponding to each of the messaging models with which the proxy is able to communicate, and wherein the sent message to those proxies identifies the specified messaging model based on selecting the interface method of the proxy that corresponds to the specified messaging model as the interface method to be invoked.

42. The method of claim 40 wherein the sent messages to the proxies identify the specified messaging model based on specifying a parameter during the invoking of the interface method such that the specified parameter corresponds to the specified messaging model.

43. The method of claim 37 wherein the local messaging service is an object instance.

44. The method of claim 43 wherein the notifying of the local messaging service includes invoking an interface method of the local messaging service instance.

45. The method of claim 44 wherein the local messaging service instance has distinct interface methods corresponding to each of the messaging models with which the local messaging service is able to communicate, and wherein the specifying of a messaging model during the notifying of the local messaging service is based on selecting the interface method of the local messaging service that corresponds to the specified messaging model as the interface method to be invoked.

46. The method of claim 44 wherein the specifying of a messaging model during the notifying of the local messaging service is based on specifying a parameter during the invoking of the interface method such that the specified parameter corresponds to the specified messaging model.

47. The method of claim 37 wherein the application includes multiple action handler components each for responding to requests from external clients with responses generated in a format used by the action handler component, and wherein each notifying of the local messaging service to send a message is prompted by a request generated by one of the action handler components.

48. The method of claim 47 wherein the application includes multiple view handler components each for transforming generated responses in formats used by action handler components into formats compatible with external clients, and including receiving responses from remote services and using view handler components to transform the received responses into formats compatible with external clients.

49. The method of claim 37 wherein at least one of the remote services does not provide a response that corresponds to the specified messaging model for the communication, and wherein the identified proxy generates the received response in accordance with the specified messaging model.

50. The method of claim 37 wherein at least one of the identified proxies does not provide a response that corresponds to the specified messaging model for the communication, and wherein the local messaging service generates the received response in accordance with the specified messaging model.

51. The method of claim 37 wherein a response generated by at least one of the remote services does not correspond to the specified messaging model, and wherein the identified proxy generates the received response in accordance with the specified messaging model.

52. The method of claim 37 wherein a response generated by at least one of the identified proxies does not correspond to the specified messaging model, and wherein the local messaging service generates the received response in accordance with the specified messaging model.

53. A computer-readable medium whose contents cause a computing device to execute an application able to communicate with remote services using multiple messaging models, each remote service having for each of the multiple messaging models an associated proxy able to communicate using that messaging model, by:

for each of multiple of the remote services,

notifying a local messaging service to send a message to the remote service using a specified messaging model;

under control of the local messaging service,

identifying the associated proxy for the remote service that is able to communicate with the remote service using the specified messaging model; and

sending the message to the identified proxy for communication to the remote service using the specified messaging model; and

receiving a response to the sent message from the local messaging service in accordance with the specified messaging model.

54. The computer-readable medium of claim 53 wherein the computer-readable medium is a data transmission medium transmitting a generated data signal containing the contents.

55. The computer-readable medium of claim 53 wherein the computer-readable medium is a memory of a computer system.

56. A computing device for executing an application to communicate with remote services using multiple messaging models, each remote service having for each of the multiple messaging models an associated proxy able to communicate using that messaging model, comprising:

an application capable of, for each of multiple of the remote services, notifying a local messaging service to send a message to the remote service using a specified messaging model; and

the local messaging service capable of identifying the associated proxy for the remote service that is able to communicate with the remote service using the specified messaging model, and of sending the message to the identified proxy for communication to the remote service using the specified messaging model.

57. A computing device for executing an application to communicate with remote services using multiple messaging models, each remote service having for each of the multiple messaging models an associated proxy able to communicate using that messaging model, comprising:

means for, for each of multiple of the remote services, notifying a local messaging service to send a message to the remote service using a specified messaging model and receiving a response to the sent message from the local messaging service in accordance with the specified messaging model; and

means for identifying the associated proxy for the remote service that is able to communicate with the remote service using the specified messaging model, and for sending the message to the identified proxy for communication to the remote service using the specified messaging model.

58. A method in a computer system for sending messages to remote applications using multiple messaging models, each remote application having at least one associated proxy able to communicate using at least one of the messaging models, the method comprising:

for each of multiple of the remote applications,

receiving a request from a client to send a message to the remote application using a specified messaging model;

retrieving information associated with the remote application that identifies at least one proxy associated with the remote application;

when one of the identified proxies is able to communicate using the specified messaging model,

sending the message to that one proxy for communication to the remote application using the specified messaging model; and

providing a response to the client in accordance with the sending of the message using the specified messaging model; and

when none of the identified proxies are able to communicate using the specified messaging model,

selecting one of the identified proxies that is able to communicate using a messaging model distinct from the specified messaging model;

sending the message to the selected proxy for communication to the remote application using the distinct messaging model; and

providing a response to the client in such a manner as to simulate using the specified messaging model for the sending of the message.

59. The method of claim 58 including, under control of each of the proxies:

receiving the sent message; and

sending the message to the remote application in a manner specific to the remote application.

60. The method of claim 58 wherein each of the proxies are object instances, and including creating each of the proxies when the proxy is first identified.

61. The method of claim 60 wherein the sending of the messages to the proxies includes invoking interface methods of the instances.

62. The method of claim 61 wherein at least one of the proxies has distinct interface methods corresponding to each of the messaging models with which the proxy is able to communicate, and wherein the sent messages to those proxies identify the specified messaging model based on selecting the interface method of the proxy that corresponds to the specified messaging model as the interface method to be invoked.

63. The method of claim 61 wherein the sent messages to the proxies identify the specified messaging model based on specifying a parameter during the invoking of the interface method such that the specified parameter corresponds to the specified messaging model.

64. The method of claim 58 wherein the application includes multiple action handler components each for responding to requests from external clients with responses generated in a format used by the action handler component, and wherein the clients from whom the requests are received are each one of the action handler components.

65. The method of claim 64 wherein the application includes multiple view handler components each for transforming generated responses in formats used by action handler components into formats compatible with external clients, and including, after the providing of each response to one of the action handler components, using one of the view handler components to transform the received response into a format compatible with one of the external clients.

66. A computer-readable medium whose contents cause a computing device to send messages to remote applications using multiple messaging models, each remote application having at least one associated proxy able to communicate using at least one of the messaging models, by:

for each of multiple of the remote applications,

receiving a request from a client to send a message to the remote application using a specified messaging model;

retrieving information associated with the remote application that identifies at least one proxy associated with the remote application;

when one of the identified proxies is able to communicate using the specified messaging model,

sending the message to that one proxy for communication to the remote application using the specified messaging model; and

providing a response to the client in accordance with the sending of the message using the specified messaging model; and

when none of the identified proxies are able to communicate using the specified messaging model,

selecting one of the identified proxies that is able to communicate using a messaging model distinct from the specified messaging model;

sending the message to the selected proxy for communication to the remote application using the distinct messaging model; and

providing a response to the client in such a manner as to simulate using the specified messaging model for the sending of the message.

67. A computing device for sending messages to remote applications using multiple messaging models, each remote application having at least one associated proxy able to communicate using at least one of the messaging models, comprising:

an first component capable of, for each of multiple of the remote applications, receiving a request from a client to send a message to the remote application using a specified messaging model, of retrieving information associated with the remote application that identifies at least one proxy associated with the remote application, of, when one of the identified proxies is able to communicate using the specified messaging model, sending the message to that one proxy for communication to the remote application using the specified messaging model and providing a response to the client in accordance with the sending of the message using the specified messaging model, and of, when none of the identified proxies are able to communicate using the specified messaging model, selecting one of the identified proxies that is able to communicate using a messaging model distinct from the specified messaging model and sending the message to the selected proxy for communication to the remote application using the distinct messaging model; and

multiple proxy copies each capable of receiving a sent message for communication to one of the remote applications and communicating the received message to the one remote application.

68. A method in a computer system for components of an executing application to communicate with remote services using multiple messaging models, each remote service having at least one associated proxy able to communicate using at least one of the messaging models, the executing application having a messaging service component for communicating with the associated proxies, having multiple action handler components each for responding to requests with responses generated in a format used by the action handler component, and having multiple view handler components each for transforming generated responses in formats used by action handler components into formats compatible with external clients, the method comprising:

under control of each of multiple of the action handler components,

receiving a request from a remote client to provide a service; and

providing the requested service by,

determining a need for functionality available from one of the remote services;

notifying the local messaging component to request the needed functionality from the one remote service using a specified messaging model;

receiving a response from the one remote service via the local messing component;

generating a response to the remote client in a format used by the action handler component;

determining a view handler component able to transform the generated response from the format used by the action handler component to a format compatible with the remote client; and

providing the generated response to the determined view handler component for the transforming;

under control of the local messaging component,

receiving notifications from multiple action handler components each to request functionality from a remote service using a specified messaging model; and

for each received notification,

identifying a proxy associated with the remote service such that the identified proxy is able to communicate using a messaging model that is compatible with the specified messaging model; and

sending a request for the functionality to the identified proxy using the compatible messaging model for communication to the remote service;

receiving a response to the sent request from the remote service via the identified proxy; and

notifying the action handler component of the received response; and

under control of each of multiple of the view handler components,

receiving responses generated by at least one action handler component in a format used by the action handler component; and

for each received response, transforming the received response into a format that is compatible with the remote client for whom the received response was generated.

69. A method in a computer system for an executing application to communicate with remote services using multiple messaging models, the executing application having a local messaging service able to communicate with each of the remote services using at least one of the multiple messaging models, the method comprising:

for each of multiple of the remote services,

receiving an indication to send a specified message to the remote service using a specified messaging model;

notifying the local messaging service to send the message to the remote service using the specified messaging model;

under control of the local messaging service,

determining whether the remote service supports communication using a messaging model that is compatible with the specified messaging model;

when the remote service does support the compatible messaging model communication,

sending the message to the remote service using the compatible messaging model; and

receiving a response from the remote service in accordance with the compatible messaging model; and

when the remote service does not support the compatible messaging model communication,

sending the message to the remote service using a messaging model that is incompatible with the specified messaging model; and

simulating a response to the sent message in accordance with the specified messaging model; and

receiving a response to the sent message from the local messaging service in accordance with the specified messaging model.