Event message endpoints in a distributed computing environment

• US 8,001,232 B1
• Filed: 10/19/2000
• Issued: 08/16/2011
• Est. Priority Date: 05/09/2000
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Saulpaugh, Thomas E., Slaughter, Gregory L., Pouyoul, Eric
• Primary Examiner(s): Divecha; Kamal B
• Application Number:
  US09/692,765
• Time in Patent Office: 3,953 Days
• Field of Search: 709/203, 709/206, 709/232, 709/236, 709/246, 709/250, 709/200, 709/201, 709/226, 719/318, 719/328, 719/330
• US Class Current: 709/224
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Embodiments of event message endpoints in a distributed computing environment are described. A set of event messages that may be generated by a service in the distributed computing environment may be described in a data representation language event message schema for the service. For each event message in the schema, the endpoint may subscribe as a consumer of the event. A service may send a message including a data representation language representation of the event to each event message endpoint subscribed to the event. The event message endpoint may extract the representation of the event from the message and distribute it to clients with registered interest in the event type. The event message endpoint may type check the event message and/or the representation of the event against the message schema. Event messages endpoints may also authenticate the sender of the message and verify the integrity of message.

Claims

1. A method for handling events in a distributed computing system including a plurality of devices connected by a network, said method comprising:

obtaining, from a remote location, a markup language schema on a client platform,

wherein said markup language schema defines a message interface of a remote service for a plurality of events generated by the remote service and indicates the plurality of events to be published by the remote service;

obtaining an address for said remote service within the distributed computing system;

automatically constructing, by computer-executable message endpoint construction code on the client platform, an event message endpoint on the client platform according to the markup language schema and the obtained address for the remote service,

wherein said automatically constructing is performed within a runtime system of the client platform, and

wherein the event message endpoint implements an API to send and receive event messages to and from the service;

receiving, by the event message endpoint on the client platform in the distributed computing system, indications from one or more client processes registering interest in receiving one or more of the plurality of events generated by the remote service in the distributed computing system;

the event message endpoint automatically subscribing to the one or more events with the remote service in response to said indications registering interest in the one or more events received from the one or more client processes such that the event message endpoint becomes subscribed to the one or more events;

receiving, by the event message endpoint over a network, a message in a markup language sent to the client platform in the distributed computing system from the remote service in the distributed computing system,

wherein the message is received at the event message endpoint from the remote service over the network in the distributed computing system, and

wherein the message includes a markup language representation of one of the one or more events generated by the remote service to which the event message endpoint is subscribed; and

sending, from the event message endpoint, the markup language representation of the event to at least one of the one or more client processes registered with the event message endpoint to receive the event,

wherein said markup language representation is in a data representation format which is independent of said client platform.

2. The method as recited in claim 1, further comprising the service sending one or more messages each including a markup language representation of an event to subscribers to the event in response to generation of the event by the service.

3. The method as recited in claim 1, wherein the markup language message from the service includes an authentication credential for the service, the method further comprising the event message endpoint authenticating the markup language message as being from the service according to the authentication credential for the service.

4. The method as recited in claim 1, further comprising the event message endpoint verifying type correctness of the markup language message according to the markup language schema prior to said sending the markup language representation of the event to the at least one of the one or more client processes.

5. The method as recited in claim 1, wherein the markup language schema defines a plurality of messages including markup language representations of the plurality of events generated by the service, the method further comprising the event message endpoint verifying correctness of the markup language message from the service according to the markup language schema prior to said sending the markup language representation of the event to the at least one of the one or more client processes.

6. The method as recited in claim 1,

wherein said receiving indications from one or more client processes registering interest in receiving one or more of the plurality of events comprises receiving from each of the one or more client processes an event handler callback method for an event handler of the respective client process;

and

wherein said sending the markup language representation of the event to at least one of the one or more client processes registered with the event message endpoint to receive the event comprises;

the event message endpoint calling an event handler callback method of each client process registered with the event message endpoint to receive the event; and

the event message endpoint passing the markup language representation of the event to each called event handler.

7. The method as recited in claim 1, further comprising:

at least one client process unregistering interest in a first event of the service with the event message endpoint; and

the event message endpoint automatically unsubscribing to the first event with the service in response to said unregistering interest by the at least one client process;

wherein the service is configured to not send messages including markup language representations of the first event to event message endpoints that are unsubscribed to the first event.

8. The method as recited in claim 1, wherein said obtaining a markup language schema comprises receiving the markup language schema of the service in a service advertisement of the service, wherein the service advertisement is a markup language document that defines each event message generated by the service.

9. The method as recited in claim 1, wherein the one or more client processes are executing within the client platform.

10. The method as recited in claim 1, wherein the event is a Java event.

11. The method as recited in claim 1, wherein said markup language is eXtensible Markup Language (XML).

12. A device, comprising:

a processor; and

a memory coupled to said processor, wherein said memory comprises program instructions executable by said processor configured to;

obtain, from a remote location, a markup language schema on a client platform,

wherein said markup language schema defines a message interface of a remote service for a plurality of events generated by the remote service and indicates the plurality of events to be published by the remote service;

obtain an address for said remote service within a distributed computing system;

automatically construct, using computer-executable message endpoint construction code on the client platform, an event message gate unit on the client platform according to the markup language schema and the obtained address for the remote service,

wherein the event message gate unit is configured to automatically construct the event message endpoint within a runtime system of the client platform, and

wherein the event message endpoint implements an API to send and receive event messages to and from the service;

receive indications from one or more client processes registering interest in receiving one or more of a plurality of events generated by the remote service in the distributed computing system;

automatically subscribe to the one or more events with the remote service in response to said indications registering interest in the one or more events received from the one or more client processes such that the event message gate unit becomes subscribed to the one or more events;

receive over a network a message in a markup language,

wherein the message is received at the event message gate unit from the remote service in the distributed computing system, and

wherein the message includes a markup language representation of one of the one or more events generated by the service to which the event message gate unit is subscribed; and

send the markup language representation of the event from the event message gate unit to at least one of the one or more client processes registered with the event message gate unit to receive the event,

wherein said markup language representation is in a data representation format which is independent of said client platform.

13. The device as recited in claim 12, wherein the event message gate unit is further configured to verify type correctness of the received markup language message according to the markup language schema prior to said sending the markup language representation of the event to the at least one of the one or more client processes.

14. The device as recited in claim 12, wherein the markup language schema defines a plurality of messages including markup language representations of the plurality of events generated by the service, and wherein the event message gate unit is further configured to verify correctness of the received markup language message according to the markup language schema prior to said sending the markup language representation of the event to the at least one of the one or more client processes.

15. The device as recited in claim 12, wherein, to obtain a markup language schema, the device is configured to receive the markup language schema of the service in a service advertisement of the service, wherein the service advertisement is a markup language document that defines each event message generated by the service.

16. The device as recited in claim 12, wherein the service is configured to send one or more messages each including a markup language representation of an event to subscribers to the event in response to generation of the event by the service.

17. The device as recited in claim 12, wherein the markup language message from the service includes an authentication credential for the service, wherein the event message gate unit is further configured to authenticate the markup language message as being from the service according to the authentication credential for the service.

18. The device as recited in claim 12, wherein, to implement the event message gate unit on the device, the program instructions are further executable by said processor to:

obtain an authentication credential indicating authorization to access said service; and

construct the event message gate unit according to the markup language schema, the obtained address for the service, and the obtained authentication credential for the service.

19. The device as recited in claim 12,

wherein, to receive indications from one or more client processes registering interest in receiving one or more of the plurality of events, the event message gate unit is configured to receive from each of the one or more client processes an event handler callback method for an event handler of the respective client process;

and

wherein, to send the markup language representation of the event to at least one of the one or more client processes registered with the event message gate unit to receive the event, the event message gate unit is further configured to;

call an event handler callback method of each client process registered with the event message gate unit to receive the event; and

pass the markup language representation of the event to each called event handler.

20. The device as recited in claim 12,

wherein the event message gate unit is further configured to:

receive an indication from at least one client process unregistering interest in a first event of the service with the event message gate unit; and

automatically unsubscribe to the first event with the service in response to said indication from the at least one client process unregistering interest in the first event; and

wherein the service is configured to not send messages including markup language representations of the first event to event message gate units that are unsubscribed to the first event.

21. The device as recited in claim 12, wherein the one or more client processes are executing on the device.

22. The device as recited in claim 12, wherein the event is a Java event.

23. The device as recited in claim 12, wherein said markup language is eXtensible Markup Language (XML).

24. A device, comprising:

a processor;

a memory coupled to said processor, wherein said memory comprises program instructions executable by said processor to implement a remote service process configured to;

provide a markup language schema within a distributed computing system, wherein said markup language schema defines a message interface for a plurality of events generated by the remote service process and indicates the plurality of events to be published by the remote service; and

provide an address for said remote service process within a distributed computing system

generate an event;

generate a message in a markup language, wherein the message includes a markup language representation of the event generated by the remote service process; and

send the message over a network to one or more event message gate units in a distributed computing system that have each automatically subscribed to the event with the remote service process in response to one or more client processes registering interest in the event with the respective event message gate unit;

wherein each of the one or more event message gate units is operable to distribute the markup language representation of the event sent in the message from the remote service process to the one or more client processes registered with the respective event message gate unit to receive the event from the remote service process, wherein to distribute the markup language representation of the event, each of the one or more event message gate units is operable to send the markup language representation of the event from the respective event message gate unit to the one or more client processes;

wherein each of the one or more event message gate constructed, using computer-executable message endpoint construction code on the client platform according to the markup language schema and the provided address for the remote service process,

wherein each of the event message gate units automatically constructed within a runtime system of the client platform, and

wherein each of the event message gate units implements an API to send and receive event messages to and from the service; and

wherein said markup language representation is in a data representation format which is independent of said client platform.

25. The device as recited in claim 24, wherein the device further comprises a service message gate unit, wherein said generating a message and said sending the message are performed by the service message gate unit on behalf of the service process.

26. The device as recited in claim 24, wherein the markup language schema defines a plurality of messages including markup language representations of the plurality of events generated by the service process.

27. The device as recited in claim 24, wherein the service process is further configured to provide the markup language schema in a service advertisement, wherein the service advertisement is a markup language document that defines each event message generated by the service process.

28. The device as recited in claim 24, wherein the service process is further configured to send one or more messages each including a markup language representation of an event to event message gate units subscribed to the event in response to generation of the event by the service process.

29. The device as recited in claim 24, wherein the service process is further configured to attach an authentication credential for the service process to the markup language message, wherein the event message gate units that receive the markup language message are configured to authenticate the markup language message as being from the service process according to the authentication credential attached to the message.

30. The device as recited in claim 24, wherein the events are Java events.

31. The device as recited in claim 24, wherein said markup language is eXtensible Markup Language (XML).

32. A non-transitory computer readable storage medium comprising program instructions, wherein the program instructions are computer-executable to implement an event message gate unit on a client platform in a distributed computing system, wherein the program instructions are configured to:

obtain, from a remote location, a markup language schema on a client platform,

wherein said markup language schema defines a message interface of a remote service for a plurality of events generated by the remote service and indicates the plurality of events to be published by the remote service;

obtain an address for said remote service within a distributed computing system;

automatically construct, using computer-executable message endpoint construction code on the client platform, an event message endpoint on the client platform according to the markup language schema and the obtained address for the remote service,

wherein said automatically constructing is performed within a runtime system of the client platform, and

wherein the event message endpoint implements an API to send and receive event messages to and from the service;

receive indications from one or more client processes registering interest in receiving one or more of a plurality of events generated by the remote service in the distributed computing system;

automatically subscribe to the one or more events with the remote service in response to said indications registering interest in the one or more events received from the one or more client processes such that the event message endpoint becomes subscribed to the one or more events;

receive over a network a message in a markup language sent to the client platform in the distributed computing system from the service in the distributed computing system, wherein the message is received at the event message endpoint from the service over the network in the distributed computing system, and wherein the message includes a markup language representation of one of the one or more events generated by the service to which the event message endpoint is subscribed; and

send the markup language representation of the event from the event message endpoint to at least one of the one or more client processes registered with the event message endpoint to receive the event, wherein said markup language representation is in a data representation format which is independent of said client platform.

33. The non-transitory computer readable storage medium as recited in claim 32, wherein the service is configured to send one or more messages each including a markup language representation of an event to subscribers to the event in response to generation of the event by the service.

34. The non-transitory computer readable storage medium as recited in claim 32, wherein the markup language message from the service includes an authentication credential for the service, wherein the event message endpoint is configured to authenticate the markup language message as being from the service according to the authentication credential for the service.

35. The non-transitory computer readable storage medium as recited in claim 32, wherein the event message endpoint is configured to verify type correctness of the markup language message according to the markup language schema prior to said sending the markup language representation of the event to the at least one of the one or more client processes.

36. The non-transitory computer readable storage medium as recited in claim 32, wherein the markup language schema defines a plurality of messages including markup language representations of the plurality of events generated by the service, wherein the event message endpoint is configured to verify correctness of the markup language message from the service according to the markup language schema prior to said sending the markup language representation of the event to the at least one of the one or more client processes.

37. The non-transitory computer readable storage medium as recited in claim 32, wherein, to implement the event message endpoint on the client platform, the program instructions are further computer-executable to:

obtain an authentication credential indicating authorization to access said service; and

construct the event message endpoint according to the markup language schema, the obtained address for the service, and the obtained authentication credential for the service.

38. The non-transitory computer readable storage medium as recited in claim 32,

wherein, to receive indications from one or more client processes registering interest in receiving one or more of the plurality of events, the event message endpoint is configured to receive from each of the one or more client processes an event handler callback method for an event handler of the respective client process;

wherein, to send the markup language representation of the event to at least one of the one or more client processes registered with the event message endpoint to receive the event, the event message endpoint is configured to;

call an event handler callback method of each client process registered with the event message endpoint to receive the event; and

pass the markup language representation of the event to each called event handler.

39. The non-transitory computer readable storage medium as recited in claim 32,

wherein the event message endpoint is further configured to:

receive an indication from at least one client process unregistering interest in a first event of the service with the event message endpoint; and

automatically unsubscribe to the first event with the service in response to said indication from the at least one client process unregistering interest in the first event;

wherein the service is configured to not send messages including markup language representations of the first event to event message endpoints that are unsubscribed to the first event.

40. The non-transitory computer readable storage medium as recited in claim 32, wherein, to obtain a markup language schema, the program instructions are further computer-executable to receive the markup language schema of the service in a service advertisement of the service, wherein the service advertisement is a markup language document that defines each event message generated by the service.

41. The non-transitory computer readable storage medium as recited in claim 32, wherein the one or more client processes are executing within the client platform.

42. The non-transitory computer readable storage medium as recited in claim 32, wherein the event is a Java event.

43. The non-transitory computer readable storage medium as recited in claim 32, wherein said markup language is eXtensible Markup Language (XML).