Method and system of maintaining a browser in a design application workflow

• US 8,751,579 B1
• Filed: 03/02/2006
• Issued: 06/10/2014
• Est. Priority Date: 03/02/2006
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Dayon, Alexandre
• Primary Examiner(s): Chan, Wing F
• Assistant Examiner(s): Thieu, Benjamin M
• Application Number:
  US11/366,920
• Time in Patent Office: 3,022 Days
• Field of Search: 709217-219, 709223-225, 709/235, 709200-206, 370/310, 370/352, 370/238, 370/229, 370/235
• US Class Current: 709/205
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures

Abstract

A system for maintaining consistent workflow is disclosed. The system includes a browser, a local application, a server application, and protocol logic configured to coordinate interactions between the local application and the server application and control the browser. Upon detecting the local application becoming active, the protocol logic freezes the browser until an event with respect to the local application is detected. The protocol logic is further configured to utilize a plurality of browser network parameters shared with a number of other protocols in order to ensure that the protocol logic is compatible with different network security devices.

Claims

1. A system for maintaining consistent workflow, the system comprising:

a processor; and

a machine-readable storage medium including instructions that, when executed by the processor, cause the processor to implement a browser, a local application, and protocol logic, wherein the instructions further cause the protocol logic to;

establish a line of communication between the local application and the browser;

control the browser;

upon detecting the local application becoming active, freeze the browser until an event with respect to the local application is detected; and

utilize a plurality of browser network parameters shared with a plurality of other protocols in order to ensure that the protocol logic is compatible with different network security devices,

wherein the local application is a non-browser application and the local application is a non-browser embedded application, and the event includes closing of the local application.

2. The system of claim 1 wherein when the browser is frozen pursuant to the protocol logic, the browser remains alive in that the browser and the local application are capable of interacting with one another.

3. The system of claim 2, wherein when the browser is frozen pursuant to the protocol logic, a user is not allowed to interact with the browser directly.

4. The system of claim 1 wherein when the browser is frozen pursuant to the protocol logic, the browser is prevented from reacting to user-initiated events, and wherein the user-initiated events comprise one or more of a mouse click and a menu command.

5. The system of claim 1 wherein the protocol logic works with a plurality of application types, the local application belonging to one of the plurality of application types.

6. The system of claim 1, wherein a primary purpose of the local application is a word processor.

7. A system for maintaining consistent workflow, the system comprising:

a processor; and

a machine-readable storage medium including instructions that, when executed by the processor, cause the processor to implement a browser, a local application, and protocol logic, wherein the instructions further cause the protocol logic to;

synchronize behavior among the browser, the local application and the server application by establishing a line of communication between the browser, the local application and the server application;

upon detecting a first event with respect to the local application, freeze the browser until a second event with respect to the local application is detected; and

utilize plurality of browser network parameters shared with a plurality of other protocols in order to ensure that the protocol logic is compatible with different network security devices, and wherein the elements are implemented by a computer

wherein the local application is a non-browser application and the local application is a non-browser embedded application, and the second event includes closing of the local application.

8. The system of claim 7 wherein when the browser is frozen pursuant to the protocol logic, a browser session associated with the browser remains alive allowing the browser and the local application to interact with one another.

9. The system of claim 8, wherein when the browser is frozen pursuant to the protocol logic, a user is not allowed to interact with the browser directly.

10. The system of claim 7 wherein the first event includes opening of the local application.

11. The system of claim 7 wherein the protocol logic works with a plurality of browser types, the browser belonging to one of the plurality of browser types.

12. The system of claim 7 wherein the protocol logic works with a plurality of application types, the local application belonging to one of the plurality of browser types.

13. A method of maintaining consistent workflow between a browser and an application by a processor executing the browser and the application, the method comprising:

activating the browser to establish a browser session;

initiating launch of the application;

establishing a line of communication between the browser and the application;

upon detecting that the application is to be launched, freezing the browser until an event with respect to the application is detected; and

using a plurality of browser network parameters shared with a plurality of other protocols to ensure compatibility with different network security devices;

wherein the application is a non-browser application and the application is a non-browser embedded application and the event includes closing of the application.

14. The method of claim 13 wherein when the browser is frozen, the browser remains alive in that the browser and the application are capable of interacting with one another.

15. The method of claim 14, wherein when the browser is frozen, a user is not allowed to interact with the browser directly.

16. The method of claim 13, wherein the protocol works with a plurality of browser types, the browser belonging to one of the plurality of browser types.

17. The method of claim 13, wherein the protocol works with a plurality of application types, the application belonging to one of the plurality of browser types.