SYSTEMS, METHODS, AND APPARATUSES FOR IMPLEMENTING THE SIMULTANEOUS DISPLAY OF MULTIPLE BROWSER CLIENT CURSORS AT EACH BROWSER CLIENT COMMON TO A SHARED BROWSING SESSION

• US 20150058407A1
• Filed: 10/13/2014
• Published: 02/26/2015
• Est. Priority Date: 02/11/2011
• Status: Abandoned Application

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: GoInstant Incorporated (Salesforce.com, Inc.)
• Inventors: Uhma, Gavin Andrew Ross, MacDonald, Jevon
• Application Number:
  US14/513,109
• Publication Number:
  US 20150058407A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: G06F 9/45529 Embedded in an application, e.g. JavaScript in a Web browser
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

A system incorporating techniques described in this paper includes a shared session server system that enables clients to view and interact with content simultaneously. The system enables a first shared session client to send an event stream sufficient to depict results of interaction with the content at a second shared session client.

Claims

1. A method at a shared session server having at least a processor and a memory therein for enabling a plurality of shared session clients to view and interact with content simultaneously within a shared browsing session common to the plurality of shared session clients, wherein the method comprises:

creating the shared browsing session at the shared session server;

connecting the shared browsing session with at least a first shared session client and a second shared session client communicatively interfaced with the shared session server via a network;

receiving a request from the first shared session client for a URL;

downloading, at the shared session server, a webpage corresponding to the URL;

modifying source code of the webpage at the shared session server; and

returning the webpage having the modified source code therein to the first and second shared session clients for display.

2. The method of claim 1, wherein modifying source code of the webpage at the shared session server comprises modifying the source code of the webpage to embed code that enables a user interface for collaborating on the webpage by the first and second shared session clients.

3. The method of claim 1, wherein modifying source code of the webpage at the shared session server comprises converting all URLs within the webpage which are capable of changing location.

4. The method of claim 3, wherein converting all URLs within the webpage which are capable of changing location comprises converting any of links, forms, URLs, and URLs within scripts to of the webpage to direct the first and second shared session clients to download resources from the shared session server.

5. The method of claim 1, wherein modifying source code of the webpage at the shared session server comprises modifying the source code of the webpage to direct any shared session client of the shared browsing session to download the webpage'"'"'s resources from the shared session server in place of a content server referenced by the URL requested.

6. The method of claim 5, wherein modifying source code of the webpage at the shared session server further comprises:

removing or modifying any source code from the webpage that prevents the content from displaying or behaving at the first and second shared session clients as it would if such content were downloaded from a content server referenced by the URL requested during an unshared session rather than having been downloaded at the shared session server on behalf of the first and second shared session clients during the shared browsing session.

7. The method of claim 1, wherein modifying source code of the webpage at the shared session server comprises adding collaboration features and user interface features to the source code at the shared session server prior to returning the webpage having the modified source code therein to the first and second shared session clients for display.

8. The method of claim 1, wherein modifying source code of the webpage at the shared session server comprises performing frame busting operations to prevent the webpage, as modified and returned to the first and second shared session clients for display, from loading into another party'"'"'s framed webpage.

9. The method of claim 1, further comprising:

storing the modified source code as cached content at the shared session server for later retrieval; and

wherein returning the webpage having the modified source code therein to the first and second shared session clients for display comprises sending the cached content to at least one of the plurality of shared session clients in the shared browsing session.

10. The method of claim 1, further comprising:

notifying the plurality of shared session clients of changes to the content being shared via the shared browsing session; and

instructing the plurality of shared session clients to make a request to the shared session server with a URL structured to download the shared content from a cache at the shared session server.

11. Non-transitory computer readable storage media having instructions stored thereon that, when executed by a processor of a shared session server, the instructions cause the shared session server to perform operations for enabling a plurality of shared session clients to view and interact with content simultaneously within a shared browsing session common to the plurality of shared session clients, the operations comprising:

creating the shared browsing session at the shared session server;

connecting the shared browsing session with at least a first shared session client and a second shared session client communicatively interfaced with the shared session server via a network;

receiving a request from the first shared session client for a URL;

downloading, at the shared session server, a webpage corresponding to the URL;

modifying source code of the webpage at the shared session server; and

returning the webpage having the modified source code therein to the first and second shared session clients for display.

12. The non-transitory computer readable storage media of claim 11, wherein modifying source code of the webpage at the shared session server comprises modifying the source code of the webpage to embed code that enables a user interface for collaborating on the webpage by the first and second shared session clients.

13. The non-transitory computer readable storage media of claim 11, wherein modifying source code of the webpage at the shared session server comprises converting all URLs within the webpage which are capable of changing location.

14. The non-transitory computer readable storage media of claim 11, wherein modifying source code of the webpage at the shared session server comprises modifying the source code of the webpage to direct any shared session client of the shared browsing session to download the webpage'"'"'s resources from the shared session server in place of a content server referenced by the URL requested.

15. The non-transitory computer readable storage media of claim 14, wherein modifying source code of the webpage at the shared session server further comprises:

removing or modifying any source code from the webpage that prevents the content from displaying or behaving at the first and second shared session clients as it would if such content were downloaded from a content server referenced by the URL requested during an unshared session rather than having been downloaded at the shared session server on behalf of the first and second shared session clients during the shared browsing session.

16. The non-transitory computer readable storage media of claim 11, wherein modifying source code of the webpage at the shared session server comprises adding collaboration features and user interface features to the source code at the shared session server prior to returning the webpage having the modified source code therein to the first and second shared session clients for display.

17. The non-transitory computer readable storage media of claim 11, wherein the instructions cause the shared session server to perform operations further comprising:

storing the modified source code as cached content at the shared session server for later retrieval; and

wherein returning the webpage having the modified source code therein to the first and second shared session clients for display comprises sending the cached content to at least one of the plurality of shared session clients in the shared browsing session.

18. The non-transitory computer readable storage media of claim 11, wherein the instructions cause the shared session server to perform operations further comprising:

notifying the plurality of shared session clients of changes to the content being shared via the shared browsing session; and

instructing the plurality of shared session clients to make a request to the shared session server with a URL structured to download the shared content from a cache at the shared session server.

19. The non-transitory computer readable storage media of claim 11, wherein modifying source code of the webpage at the shared session server comprises performing frame busting operations to prevent the webpage, as modified and returned to the first and second shared session clients for display, from loading into another party'"'"'s framed webpage.

20. A shared session server to enable a plurality of shared session clients to view and interact with content simultaneously within a shared browsing session common to the plurality of shared session clients, wherein the shared session server comprises:

a processor;

a memory;

a shared content synchronization server engine to create the shared browsing session at the shared session server;

a load balancing engine to connect the shared browsing session with at least a first shared session client and a second shared session client communicatively interfaced with the shared session server via a network;

a core-server to receive a request from the first shared session client for a URL;

a web client engine to download, at the shared session server, a webpage corresponding to the URL;

a real-time server engine to modify source code of the webpage at the shared session server; and

the core-server to further return the webpage having the modified source code therein to the first and second shared session clients for display.

21. The shared session server of claim 20, wherein the core-server is to further respond to port 80 requests from clients and serve web pages to the first and second shared session clients.