METHOD AND APPARATUS FOR BROWSING NETWORK RESOURCES USING AN ASYNCHRONOUS COMMUNICATIONS PROTOCOL

• US 20070005725A1
• Filed: 06/30/2005
• Published: 01/04/2007
• Est. Priority Date: 06/30/2005
• Status: Abandoned Application

• Current Assignee: Scenera Technologies LLC (Scenera Research LLC)
• Original Assignee: Scenera Technologies LLC (Scenera Research LLC)
• Inventors: Morris, Robert
• Application Number:
  US11/160,612
• Publication Number:
  US 20070005725A1
• Time in Patent Office: Days
• US Class Current: 709/218
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users

Abstract

A method and system are described for browsing network resources using an asynchronous communications protocol. According to an exemplary embodiment, a method in a client is described for receiving an identifier of a tuple associated with a network resource, the tuple including information related to the resource and a link to other information related to the resource. The identifier is used for requesting a subscription to the tuple associated with the network resource. A notification is received including the information related to the network resource and the link based on the subscription to the tuple associated with the network resource.

Claims

1. A method for browsing network resources using an asynchronous communications protocol, the method comprising:

in a client;

receiving an identifier of a tuple associated with a network resource, the tuple including information related to the resource and a link to other information related to the resource;

using the identifier for requesting a subscription to the tuple associated with the network resource; and

receiving a notification including the information related to the network resource and the link based on the subscription to the tuple associated with the network resource.

2. The method of claim 1, comprising at least one of:

presenting at least some of the information related to the network resource and/or the link in a presentation space of the client; and

converting at least some of the information related to the network resource and/or the link into a format usable by a principal associated with the client.

3. The method of claim 2, wherein the presenting and/or converting is/are based on information included in the tuple associated with the network resource describing a type of the tuple.

4. The method of claim 1, comprising:

receiving a form object having a form field element included in the information related to the network resource;

presenting the form field element in a presentation space of the client;

receiving form input corresponding to the form field element;

associating the received form input with the form field element; and

detecting an action for submitting the received form input.

5. The method of claim 4, wherein in response to detecting the action, the method comprises publishing the received form input to at least one of the tuple associated with the network resource, another tuple associated with the link, and a tuple associated with the form object.

6. The method of claim 5, wherein when the form input is published to the tuple associated with the network resource, the method comprises receiving a notification including a result of the form submission based on the subscription to the tuple associated with the resource.

7. The method of claim 5, wherein when the form input is published to the tuple associated with the form object, the method comprises:

using an identifier associated with the form object included in the information related to the network resource for requesting a subscription to the tuple associated with the form object; and

receiving a notification including a result of the form submission based on the subscription to the tuple associated with the form object.

8. The method of claim 5, wherein the tuple associated with the form object is shared between a principal associated with the client and a principal associated with the network resource.

9. The method of claim 5, wherein in response to detecting the action, the method comprises sending the received form input to a network server using a synchronous communications protocol.

10. The method of claim 1, comprising using a link type associated with the link included in the tuple to determine a relationship between the network resource and the other information related to the resource.

11. The method of claim 1, comprising using and/or maintaining a list of identifiers of tuples associated with a plurality of related network resources.

12. The method of claim 1, wherein an identity of the client and/or a principal associated with the client is/are authenticated and the requesting of the subscription to the tuple associated with the network resource and/or the receiving of the notification is/are authorized based on the authenticated identity prior to the requesting of the subscription and/or receiving of the notification by the client.

13. The method of claim 12, wherein the identity of the client and/or the principal associated with the client is/are included in a tuple associated with a roster list including identities of clients and/or principals authorized to access the tuple associated with the network resource.

14. The method of claim 1, comprising providing a synchronous communications protocol along with the asynchronous communications protocol for browsing the network resources.

15. The method of claim 14, wherein the synchronous communications protocol includes at least one of a request/response protocol and a HyperText Transport Protocol (HTTP).

16. The method of claim 1, wherein the asynchronous communications protocol includes at least one of a publish/subscribe (pub/sub) protocol, a presence protocol, an Extensible Messaging and Presence Protocol (XMPP), and a Simple Instant Messaging and Presence Protocol (SIMPLE).

17. The method of claim 1, wherein the identifier is received in response to an entering of the identifier in a control component of the client or in response to a selection of a link displayed in a presentation space of the client.

18. The method of claim 1, wherein a plurality of clients and/or associated principals each receive the notification including the information related to the network resource and the link based on respective subscriptions to the tuple associated with the network resource.

19. A client for browsing network resources using an asynchronous communications protocol, the client comprising:

a user interface component configured to receive an identifier of a tuple associated with a network resource, the tuple including information related to the resource and a link to other information related to the resource;

a protocol agent component coupled to the user interface component configured to use the identifier for requesting a subscription to the tuple associated with the network resource and configured to receive the information related to the network resource and the link based on the subscription to the tuple associated with the network resource; and

a communications protocol stack component coupled to the protocol agent component configured to allow the protocol agent component to request the subscription to the tuple associated with the network resource and receive the information related to the network resource and the link using an asynchronous communications protocol.

20. The client of claim 19, comprising a content handler component configured to process the information related to the network resource and the link based on the type of the information.

21. The client of claim 20, wherein the content handler component comprises a presentation manager component configured to perform at least one of presenting at least some of the information related to the network resource and/or the link in a presentation space of the client, and converting at least some of the information related to the network resource and/or the link into a format usable by a principal associated with the client.

22. The client of claim 21, wherein the content handler component comprises a parser component configured to perform at least one of receiving the information related to the network resource and the link, parsing and/or converting the information and/or link into a format usable by the presentation manager component, and identifying a form object having a form field element included in the information related to the network resource.

23. The client of claim 22, wherein the content handler component comprises an input manager component configured to perform at least one of receiving the identifier from the user interface component in response to an entering of the identifier in a control component of the client or a selection of a link displayed in the presentation space of the client, and receiving form input corresponding to the form field element.

24. The client of claim 23, wherein the content handler component comprises a forms manager component configured to perform at least one of managing the form object and the form field element identified by the parser component, receiving the form input corresponding to the form field element from the input manager component, and associating the received form input with the form field element.

25. The client of claim 24, wherein the protocol agent component is configured to publish the form input to at least one of the tuple associated with the network resource, another tuple associated with the link, and a tuple associated with the form object in response to the user interface component detecting an action for submitting the received form input.

26. The client of claim 25, wherein the protocol agent component is coupled to the content handler component and is configured to receive a notification including a result of the form submission based on the subscription to the tuple associated with the resource.

27. The client of claim 19, comprising one or more additional content handler components each configured to process the information related to the network resource and other content received by the client based on a respective type the information and other content.

28. The client of claim 27, comprising a content manager component coupled between the communications protocol stack component and each of the content handler components, the content manager component configured to route the information related to the network resource and other content to at least one of the content handler components based on the type of the information and other content.

29. The client of claim 27, comprising a second communications protocol stack component coupled to at least one of the additional content handler components, the second communications protocol stack component configured to exchange information with the at least one additional content handler component using a synchronous communications protocol.

30. The client of claim 29, wherein the synchronous communications protocol includes at least one of a request/response protocol and a HyperText Transport Protocol (HTTP).

31. The client of claim 19, wherein the asynchronous communications protocol includes at least one of a publish/subscribe (pub/sub) protocol, a presence protocol, an Extensible Messaging and Presence Protocol (XMPP), and a Simple Instant Messaging and Presence Protocol (SIMPLE).

32. A server allowing for browsing network resources using an asynchronous communications protocol, the server comprising:

at least one network resource;

a resource agent component coupled to the network resource configured to receive a notification to publish information related to the resource and a link to other information related to the resource to a tuple associated with the resource and to publish the information and the link based on a subscription to the tuple; and

a communications protocol stack component coupled to the resource agent component configured to allow the resource agent component to receive the notification and publish the information related to the resource and the link using an asynchronous communications protocol.

33. The server of claim 32, comprising a second communications protocol stack component coupled to a second network resource, the second communications protocol stack component configured to exchange information with the second network resource using a synchronous communications protocol.

34. The server of claim 33, wherein the synchronous communications protocol includes at least one of a request/response protocol and a HyperText Transport Protocol (HTTP).

35. The server of claim 32, wherein the asynchronous communications protocol includes at least one of a publish/subscribe (pub/sub) protocol, a presence protocol, an Extensible Messaging and Presence Protocol (XMPP), and a Simple Instant Messaging and Presence Protocol (SIMPLE).

36. A computer readable medium containing a computer program for browsing network resources using an asynchronous communications protocol, the computer program comprising instructions executable in a client for:

receiving an identifier of a tuple associated with a network resource, the tuple including information related to the resource and a link to other information related to the resource;

using the identifier for requesting a subscription to the tuple associated with the network resource; and

receiving a notification including the information related to the network resource and the link based on the subscription to the tuple associated with the network resource.

37. The medium of claim 36, wherein the computer program comprises instructions executable in the client for at least one of:

presenting at least some of the information related to the network resource and/or the link in a presentation space of the client; and

converting at least some of the information related to the network resource and/or the link into a format usable by a principal associated with the client.

38. The medium of claim 36, wherein the computer program comprises instructions executable in the client for:

receiving a form object having a form field element included in the information related to the network resource;

presenting the form field element in a presentation space of the client;

receiving form input corresponding to the form field element;

associating the received form input with the form field element; and

detecting an action for submitting the received form input.

39. The medium of claim 38, wherein in response to detecting the action, the computer program comprises instructions executable in the client for publishing the received form input to at least one of the tuple associated with the network resource, another tuple associated with the link, and a tuple associated with the form object.

40. The medium of claim 39, wherein when the form input is published to the tuple associated with the network resource, the computer program comprises instructions executable in the client for receiving a notification including a result of the form submission based on the subscription to the tuple associated with the resource.

41. The medium of claim 39, wherein when the form input is published to the tuple associated with the form object, the computer program comprises instructions executable in the client for:

using an identifier associated with the form object included in the information related to the network resource for requesting a subscription to the tuple associated with the form object; and

receiving a notification including a result of the form submission based on the subscription to the tuple associated with the form object.

42. The medium of claim 39, wherein in response to detecting the action, the computer program comprises instructions executable in a client for sending the received form input to a network server using a synchronous communications protocol.

43. The medium of claim 36, wherein the computer program comprises instructions executable in the client for using a link type associated with the link included in the tuple to determine a relationship between the network resource and the other information related to the resource.