Method for sending an electronic message utilizing connection information and recipient information

• US 8,375,306 B2
• Filed: 11/21/2007
• Issued: 02/12/2013
• Est. Priority Date: 08/28/2001
• Status: Active Grant

• Current Assignee: NVIDIA International Inc. (NVIDIA Corporation)
• Original Assignee: NVIDIA International Inc. (NVIDIA Corporation)
• Inventors: Zondervan, Quinton Y., Khan, Umair A., Harman, Gregory, Akhtar, Salman, Raza, Muhammad, Yepishin, Dmitriy V., Zaidi, Asad A., Haleem Vaince, Muhammad Atau Ul
• Primary Examiner(s): Tillery, Rashawn
• Application Number:
  US11/943,974
• Publication Number:
  US 20080071821A1
• Time in Patent Office: 1,910 Days
• Field of Search: 715/748, 715/764, 715/810, 715/835, 715/853
• US Class Current: 715/748
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]

Abstract

A method comprises displaying a mail server information screen, and receiving connection information via the mail server information screen. Further, the method comprises displaying an address page, and receiving recipient information via the address page. In addition, the method comprises displaying a content page, and receiving content in the content page. Additionally, an electronic mail message having the content is compiled, and the electronic mail message is sent to a recipient utilizing the connection information and recipient information.

Claims

1. A method for recording a transaction pattern utilizing a graphical user interface, comprising:

displaying an interface;

allowing a user to specify interactions with content via the interface;

recording the interactions;

generating a pattern based on the recorded interactions;

recognizing a portion of the pattern as a prefix of an already existing pattern, and creating a branching of the pattern from the already existing pattern;

displaying the pattern on a graphical user interface, wherein the pattern includes a graphical representation of each interaction; and

displaying a script view for allowing the user to utilize scripting to manipulate a data flow within the pattern;

wherein the pattern includes at least one connector that interfaces with a data source and determines at least one scripting state based on an output of an interaction with the data source;

wherein each of the at least one connector includes an error handling flow that represents an exception handling mechanism that is added to each state transition to handle at least one failure case.

2. The method as recited in claim 1, further comprising displaying a browser, wherein the user specifies interactions with web content using the browser.

3. The method as recited in claim 1, further comprising displaying a database view having database connection dialogs, wherein the user specifies interactions with a database using the dialogs.

4. The method as recited in claim 1, wherein the interface for allowing the user to specify interactions with content is a wizard.

5. The method as recited in claim 1, further comprising allowing the user to connect representations of the interactions via the graphical user interface for specifying an order of execution of the interactions in the pattern.

6. The method as recited in claim 1, wherein the pattern further includes prerecorded interactions.

7. The method as recited in claim 1, further comprising coupling the pattern to another pattern.

8. The method as recited in claim 1, further comprising receiving specifications of interactions relating to the pattern for multiple client devices.

9. The method as recited in claim 1, further comprising displaying a simulation of an output of a display of a client device during replay of the pattern.

20. The method as recited in claim 1, wherein the data flow within the pattern is manipulated by placing the at least one scripting state that decides a direction of the data flow, each scripting state including a straight thru state, a branching state or a looping state.

21. The method as recited in claim 20, wherein each scripting state is represented by an icon, and the user interacts with each scripting state by clicking on the icon representing the scripting state and specifying parameters of the scripting state.

22. The method as recited in claim 1, wherein the at least one scripting state is determined based on a structure of the output of the interaction with the data source.

10. A computer program product embodied on a non-transitory computer readable storage medium for recording a transaction pattern utilizing a graphical user interface, comprising:

computer code for displaying an interface;

computer code for allowing a user to specify interactions with content via the interface;

computer code for recording the interactions;

computer code for generating a pattern based on the recorded interactions;

computer code for recognizing a portion of the pattern as a prefix of an already existing pattern, and creating a branching of the pattern from the already existing pattern;

computer code for displaying the pattern on a graphical user interface, wherein the pattern includes a graphical representation of each interaction; and

computer code for displaying a script view for allowing the user to utilize scripting to manipulate a data flow within the pattern;

wherein the pattern includes at least one connector that interfaces with a data source and determines at least one scripting state based on an output of an interaction with the data source;

wherein each of the at least one connector includes an error handling flow that presents an exception handling mechanism that is added to each state transition to handle at least one failure case.

11. A system for recording a transaction pattern utilizing a graphical user interface, comprising:

a processor for;

displaying an interface;

allowing a user to specify interactions with content via the interface;

recording the interactions;

generating a pattern based on the recorded interactions;

recognizing a portion of the pattern as a prefix of an already existing pattern, and creating a branching of the pattern from the already existing pattern;

displaying the pattern on a graphical user interface, wherein the pattern includes a graphical representation of each interaction; and

displaying a script view for allowing the user to utilize scripting to manipulate a data flow within the pattern;

wherein the pattern includes at least one connector that interfaces with a data source and determines at least one scripting state based on an output of an interaction with the data source;

wherein each of the at least one connector includes an error handling flow that represents an exception handling mechanism that is added to each state transition to handle at least one failure case.

12. A method for recording a File Transfer Protocol (FTP) interaction, comprising:

displaying a connection type page for allowing selection of a mode of connection to a data source;

displaying a connection information page for receiving connection parameters of the data source;

displaying an action selection page for allowing selection of an FTP interaction with the data source;

displaying an action parameter page for receiving parameters relating to performing the selected FTP interaction;

generating a transaction pattern from the displaying of the connection type page, the displaying of the connection information page, the displaying of the action selection page, and the displaying of the action parameter page;

recognizing a portion of the transaction pattern as a prefix of an already existing transaction pattern, and creating a branching of the transaction pattern from the already existing transaction pattern; and

displaying a script view for allowing a user to utilize scripting to manipulate a data flow within the transaction pattern;

wherein the transaction pattern includes at least one connector that interfaces with the data source and determines at least one scripting state based on an output of an interaction with the data source;

wherein each of the at least one connector includes an error handling flow that represents an exception handling mechanism that is added to each state transition to handle at least one failure case.

13. The method as recited in claim 12, wherein the user is allowed to connect to the data source anonymously.

14. The method as recited in claim 12, further comprising displaying a data transfer mode selection page for allowing specification of a mode for data transfer.

15. The method as recited in claim 12, wherein the FTP interaction is at least one of retrieving a directory listing of the data source, uploading a file to the data source, downloading a file from the data source, and deleting a file from the data source.

16. A computer program product embodied on a non-transitory computer readable storage medium, comprising:

computer code for displaying a connection type page for allowing selection of a mode of connection to a data source;

computer code for displaying a connection information page for receiving connection parameters of the data source;

computer code for displaying an action selection page for allowing selection of an FTP interaction with the data source;

computer code for displaying an action parameter page for receiving parameters relating to performing the selected FTP interaction;

computer code for generating a transaction pattern from the displaying of the connection type page, the displaying of the connection information page, the displaying of the action selection page, and the displaying of the action parameter page;

computer code for recognizing a portion of the transaction pattern as a prefix of an already existing transaction pattern, and creating a branching of the transaction pattern from the already existing transaction pattern; and

computer code for displaying a script view for allowing a user to utilize scripting to manipulate a data flow within the transaction pattern;

wherein the transaction pattern includes at least one connector that interfaces with the data source and determines at least one scripting state based on an output of an interaction with the data source;

wherein each of the at least one connector includes an error handling flow that represents an exception handling mechanism that is added to each state transition to handle at least one failure case.

17. The computer program product as recited in claim 16, wherein the user is allowed to connect to the data source anonymously.

18. The computer program product as recited in claim 16, further comprising displaying a data transfer mode selection page for allowing specification of a mode for data transfer.

19. The computer program product as recited in claim 16, wherein the FTP interaction is at least one of retrieving a directory listing of the data source, uploading a file to the data source, downloading a file from the data source, and deleting a file from the data source.

23. A method for recording a transaction pattern utilizing a graphical user interface, comprising:

displaying an interface;

allowing a user to specify interactions with content via the interface;

recording the interactions;

generating a pattern based on the recorded interactions;

recognizing a portion of the pattern as a prefix of an already existing pattern, and creating a branching of the pattern from the already existing pattern;

displaying the pattern on a graphical user interface, wherein the pattern includes a graphical representation of each interaction; and

displaying a script view for allowing the user to utilize scripting to manipulate a data flow within the pattern;

wherein the pattern includes at least one connector that interfaces with a data source and determines at least one scripting state based on an output of an interaction with the data source;

wherein each of the at least one connector is implemented as a separate DLL and has a specified interface that allows for the connector to be plugged-in at run-time to extend the interface.

24. A computer program product embodied on a non-transitory computer readable storage medium for recording a transaction pattern utilizing a graphical user interface, comprising:

computer code for displaying an interface;

computer code for allowing a user to specify interactions with content via the interface;

computer code for recording the interactions;

computer code for generating a pattern based on the recorded interactions;

computer code for recognizing a portion of the pattern as a prefix of an already existing pattern, and creating a branching of the pattern from the already existing pattern;

computer code for displaying the pattern on a graphical user interface, wherein the pattern includes a graphical representation of each interaction; and

computer code for displaying a script view for allowing the user to utilize scripting to manipulate a data flow within the pattern;

wherein the pattern includes at least one connector that interfaces with a data source and determines at least one scripting state based on an output of an interaction with the data source;

wherein each of the at least one connector is implemented as a separate DLL and has a specified interface that allows for the connector to be plugged-in at run-time to extend the interface.

25. A system for recording a transaction pattern utilizing a graphical user interface, comprising:

a processor for;

displaying an interface;

allowing a user to specify interactions with content via the interface;

recording the interactions;

generating a pattern based on the recorded interactions;

recognizing a portion of the pattern as a prefix of an already existing pattern, and creating a branching of the pattern from the already existing pattern;

displaying the pattern on a graphical user interface, wherein the pattern includes a graphical representation of each interaction; and

displaying a script view for allowing the user to utilize scripting to manipulate a data flow within the pattern;

wherein the pattern includes at least one connector that interfaces with a data source and determines at least one scripting state based on an output of an interaction with the data source;

wherein each of the at least one connector is implemented as a separate DLL and has a specified interface that allows for the connector to be plugged-in at run-time to extend the interface.