System and method to create bi-directional event subscriptions
System and method to create a bi-directional event subscription. The method includes responding to a request by providing a URI of the subscription factory of the first topic; receiving a request to create a bidirectional subscription; creating a first subscription resource to represent an outbound event flow from a first topic to a second topic; sending a discovery request to a remote host for a URI of a subscription factory of the second topic; receiving the URI of the subscription factory of the second topic; requesting creation of a second subscription resource, to represent an outbound event flow from the second topic to the first topic; receiving from the remote host a URI of the second subscription resource; entangling the first subscription resource with the second subscription to form the bi-directional event subscription; and providing to the web browser a URI of the first subscription.
1. A method to create a bi-directional event subscription, comprising:
receiving a discovery request from a web browser for a URI of a subscription factory of a first topic;
providing a URI of the subscription factory of the first topic;
receiving a request from the web browser to create a bidirectional subscription;
creating a first subscription resource to represent an outbound event flow from a first topic to a second topic;
sending a discovery request to a remote host for a URI of a subscription factory of the second topic;
receiving from the remote host the URI of the subscription factory of the second topic;
requesting that the remote host create a second subscription resource, to represent an inbound event flow from the second topic to the first topic, wherein the request further comprises a request to entangle the second subscription with the first subscription;
receiving from the remote host a URI of the second subscription resource;
entangling the first subscription with the second subscription to form the bi-directional event subscription, wherein entangled subscriptions are created in one transaction and deleted in one transaction, such that one subscription of the entangled subscriptions does not exist without the other subscription of the entangled subscriptions; and
providing to the web browser a URI of the first subscription.
2. The method of claim 1 , wherein the method is performed by a topic hub that provides RESTful web services.
3. The method of claim 1 , wherein the remote host comprises a topic hub that provides RESTful web services.
4. The method of claim 3 , wherein the remote host comprises a member of a topic web.
5. The method of claim 1 , further comprising filtering the bi-directional event subscription.
6. The method of claim 1 , further comprising providing the URI of the first subscription to an alternative listener.
7. The method of claim 1 , wherein the bi-directional event subscription further comprises a status indicator.
8. The method of claim 1 , wherein the web browser comprises an XMPP entity.
9. The method of claim 1 , wherein the remote host communicates with a remote web browser, the remote web browser comprising an XMPP entity.
10. The method of claim 1 , wherein the URI of the subscription factory of the first topic is provided from a cache.
11. A system to create bi-directional event subscriptions, comprising:
a first receiver configured to receive a discovery request from a web browser for a URI of a subscription factory of a first topic, and to receive a request from the web browser to create a bidirectional subscription;
a first transmitter configured to provide a URI of the subscription factory of the first topic;
a creation module configured to create a first subscription resource to represent an outbound event flow from a first topic to a second topic;
a second transmitter configured to send a discovery request to a remote host for a URI of a subscription factory of the second topic, and to send a request to the remote host that the remote host create a second subscription resource, to represent an inbound event flow from the second topic to the first topic, wherein the request further comprises a request to entangle the second subscription with the first subscription;
a second receiver configured to receive from the remote host the URI of the subscription factory of the second topic, and to receive from the remote host a URI of the second subscription resource;
an entanglement module configured to entangle the first subscription with the second subscription to form the bi-directional event subscription, wherein entangled subscriptions are created in one transaction and deleted in one transaction, such that one subscription of the entangled subscriptions does not exist without the other subscription of the entangled subscriptions,
wherein the first transmitter is further configured to provide to the web browser a URI of the first subscription.
12. The system of claim 11 , further comprising a topic hub that provides RESTful web services.
13. The system of claim 11 , wherein the remote host comprises a topic hub that provides RESTful web services.
14. The system of claim 13 , wherein the remote host comprises a member of a topic web.
15. The system of claim 11 , further comprising a filter configured to filter the bi-directional event subscription.
16. The system of claim 11 , further comprising a transmitter configured to provide the URI of the first subscription to an alternative listener.
17. The system of claim 11 , wherein the bi-directional event subscription further comprises a status indicator.
18. The system of claim 11 , wherein the first transmitter and the first receiver are further configured to communicate with an XMPP entity.
19. The system of claim 11 , wherein the remote host communicates with a remote web browser, the remote web browser comprising an XMPP entity.
20. The system of claim 11 , further comprising a cache configured to provide the URI of the subscription factory of the first topic.