Method and system for communication using published events
AssigneeEMC IP Holding Company LLC
InventorsSachin Gopaldas Totale, Naveen K. Vidyananda, Jobin John
Life of this patent
Estimating the term…
Abstract
A method and system for communication using published events. Specifically, the disclosed method and system entail implementing a publication-subscription paradigm to enable communication event exchange in a device-independent manner. The publication-subscription paradigm may also enable communication event exchange in real-time, thereby avoiding web traffic intensive polling that often leads to server-overloading.
Claims17
A method for web applications to communicate using published events, comprising:
- implementing a communication event to be published in a web application, comprising:
- specifying a name of the communication event to be published;
- and
- specifying a qualifier of the communication event to be published, wherein the qualifier of the communication event to be published is a type of a qualified recipient of the communication event to be published;
- implementing a subscribed communication event in the web application, comprising:
- specifying a name of the subscribed communication event, wherein the name of the subscribed communication event is identical to the name of the communication event to be published;
- after implementing the communication event to be published and the subscribed communication event:
- obtaining, from a subscribing recipient of the web application, a communication event subscription request, wherein the communication event subscription request comprises a type of the subscribing recipient and a name of the subscribed communication event;
- obtaining, from a publishing client application, the communication event to be published, wherein the communication event to be published comprises the name of the communication event to be published and the qualifier of the communication event to be published;
- identifying a first match between the name of the subscribed communication event and the name of the communication event to be published;
- identifying a second match between the type of the subscribing recipient and the qualifier of the communication event to be published;
- making a determination, based on the first match and the second match, that the subscribing recipient is the qualified recipient of the communication event to be published;
- and
- providing, based on the determination, the communication event to be published to the subscribing recipient via a receiving element.
A non-transitory computer readable medium (CRM) storing instructions for web applications to communicate using published events, the instructions comprising functionality for:
- implementing a communication event to be published in a web application, comprising:
- specifying a name of the communication event to be published;
- and
- specifying a qualifier of the communication event to be published, wherein the qualifier of the communication event to be published is a type of a qualified recipient of the communication event to be published;
- implementing a subscribed communication event in the web application, comprising:
- specifying a name of the subscribed communication event, wherein the name of the subscribed communication event is identical to the name of the communication event to be published;
- after implementing the communication event to be published and the subscribed communication event:
- obtaining, from a subscribing recipient of the web application, a communication event subscription request, wherein the communication event subscription request comprises a type of the subscribing recipient and a name of the subscribed communication event;
- obtaining, from a publishing client application, the communication event to be published, wherein the communication event to be published comprises the name of the communication event to be published and the qualifier of the communication event to be published;
- identifying a first match between the name of the subscribed communication event and the name of the communication event to be published;
- identifying a second match between the type of the subscribing recipient and the qualifier of the communication event to be published;
- making a determination, based on the first match and the second match, that the subscribing recipient is the qualified recipient of the communication event to be published;
- and
- providing, based on the determination, the communication event to be published to the subscribing recipient via a receiving element.
A system for web applications to communicate using published events, comprising:
- a computing device comprising a computer processor;
- an application server, executing on the computer processor, and configured to:
- obtain an implementation of a communication event to be published in a web application, comprising:
- a name of the communication event to be published;
- and
- a qualifier of the communication event to be published, wherein the qualifier of the communication event to be published is a type of a qualified recipient of the communication event to be published;
- obtain an implementation of a subscribed communication event in the web application, comprising:
- a name of the subscribed communication event, wherein the name of the subscribed communication event is identical to the name of the communication event to be published;
- after obtaining the implementation of the communication event to be published and the subscribed communication event:
- obtain, from a subscribing recipient of the web application, a communication event subscription request, wherein the communication event subscription request comprises a type of the subscribing recipient and a name of the subscribed communication event;
- obtain, from a publishing client application, the communication event to be published, wherein the communication event to be published comprises the name of the communication event to be published and the qualifier of the communication event to be published;
- identify a first match between the name of the subscribed communication event and the name of the communication event to be published;
- identify a second match between the type of the subscribing recipient and the qualifier of the communication event to be published;
- make a determination, based on the first match and the second match, that the subscribing recipient is the qualified recipient of the communication event to be published;
- and
- provide, based on the determination, the communication event to be published to the subscribing recipient via a receiving element.
Dependencies are inferred from the claim text.