E-mail embedded textual hyperlink object

Information

  • Patent Grant
  • 9092535
  • Patent Number
    9,092,535
  • Date Filed
    Tuesday, September 21, 1999
    24 years ago
  • Date Issued
    Tuesday, July 28, 2015
    8 years ago
  • CPC
  • Field of Search
    • US
    • 707 501100
    • 715 501100
    • 715 207000
    • 715 208000
    • 715 752000
    • 715 760000
    • 715 203000
    • 715 108000
    • 715 109000
    • 717 108000
    • 717 109000
    • CPC
    • G06F17/3089
    • G06F8/24
  • International Classifications
    • G06F17/00
    • G06F17/30
    • Term Extension
      1121
Abstract
The present invention includes a method and article of manufacture for a computer implemented textual hyperlink. A string of text is first displayed. Upon receipt of an indication of a selection of the string of text, a link is effected to a predetermined site. The string of text is then automatically entered as a parameter of input to the site upon linking thereto.
Description
RELATED APPLICATIONS

The present application relates to applications entitled “Electronic Message Payload for Interfacing with Text Contained in the Message” (Ser. No. 09/400,781, filed Sep. 21, 1999, currently pending), “System, Method and Article of Manufacture for Preventing the Proliferation of Unwanted Electronic Messages” (Ser. No. 09/401,028, filed Sep. 21, 1999, currently pending), “Method and Article of Manufacture for a Sub-Browser Application Program Stored in an Electronic Message” (Ser. No. 09/400,708, filed Sep. 21, 1999, currently pending), “Method and Article of Manufacture for Delaying Advertisement Execution in a Geometric Electronic Media Distribution Framework” (Ser. No. 09/400,711, filed Sep. 21, 1999, currently pending), and “Method and Apparatus for the Production, Delivery, and Receipt of Enhanced E-Mail” (Ser. No. 09/401,026, filed Sep. 21, 1999, now issued as U.S. Pat. No. 6,360,221) which were filed concurrently herewith and are incorporated herein in their entirety.


FIELD OF THE INVENTION

The present invention relates to hyperlinks and more particularly to linking to sites over a network using textual hyperlinks.


BACKGROUND OF THE INVENTION

The term “hypertext” is used to describe text, or strings, with links to other documents. For example, a string may include the word “Keats”; this word could then have a link to another document with the title “English Poets”. These links are referred to herein as “hyperlinks”. Hyperlinks are used between computers in computer networks.


A notable use of hyperlinks is on the World Wide Web (WWW). In this context, the operator of an end-user computer uses a “browser” to view a published page received from a first web computer. The published page may have a “hyperlink”, which, when activated, results in a call to a second web computer, or server. More particularly, the published page may have the hyperlink “Keats”, which, when activated, causes the transfer of control to a specified university computer with a file providing information on “English Poets”.


Thus, each hyperlink includes the name of an associated file and on which computer that file is stored. The name of the computer and the file are combined into a Uniform Resource Locator (URL). A typical URL is http://SU/123. This URL is an instruction to retrieve the file 123 from the State University computer “SU” using a method called Hypertext Transport Protocol “HTTP”. A URL may also be used to invoke a specified function on a remote computer, with the remote computer returning the results of the invoked and executed function.


Often this function is limited to simplistic functions that, in some systems, may vary based on a profile of a user. Such profile parameter may be included with metadata such as a “cookie” and is entered automatically upon hyperlinking. To date, this is often the only type of parameter that is transmitted during the execution of a hyperlink. Once the hyperlink is executed, the user must often interact with the linked file, or site, to manually enter any parameters required by the site.


SUMMARY OF THE INVENTION

The present invention includes a method and article of manufacture for a computer implemented textual hyperlink. A string of text is first displayed. Upon receipt of an indication of a selection of the string of text, a link is effected to a predetermined site. The string of text is then automatically entered as a parameter of input to the site upon linking thereto.


By this feature, there is less need to interact with the predetermined site by obviating the requirement of manually entering the string of text as a parameter. This saves time and constitutes a significant convenience.


In one aspect of the present invention, the site is linked to over a network, where the site is a search engine. In such embodiment, the search engine may be capable of performing a search of the network with the text as a search parameter. Further, the displaying, receiving, linking, and entering may be carried out by an application program. In one embodiment, the application program may include an applet. Further, the application program may be attached to an electronic message.


In still yet another aspect of the present invention, the present invention may take the form of a hyperlink implemented on a computer. Such hyperlink may include a data object including a string of text, and an application program object. Such application program object is adapted for receiving an indication of a selection of the string of the text, linking to a site over a network upon receiving the indication that the string of text is selected, and automatically entering the string of text as a parameter of input to the site upon linking thereto.


These and other advantages of the present invention will become apparent to those skilled in the art upon a reading of the following descriptions of the invention and a study of the several figures of the drawing.





BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects are better understood from the following detailed description of one embodiment of the invention with reference to the drawings, in which:



FIG. 1 is an illustration of the geometric manner in which an electronic message may be distributed over a network in accordance with the prior art;



FIG. 2 is a graph depicting the geometric nature illustrated in FIG. 1;



FIG. 3 is a schematic diagram of one exemplary hardware implementation of the present invention;



FIG. 4 is a flowchart illustrating the execution of the first application program of one embodiment of the present invention;



FIG. 5 is an illustration of a graphical user interface of the present invention that is displayed upon the execution of the first application program, and which is used to display the text of the first electronic message and any functionality associated therewith;



FIG. 6 illustrates one example of the functionality displayed upon execution of the first application program in accordance with one embodiment of the present invention;



FIG. 7 illustrates the execution of the second application program of the present invention, or in an alternate embodiment, interaction with a site on the network which is initiated upon the selection of one of the “FORWARD”, “REPLY”, or “NEW” icons displayed in the graphical user interface of FIG. 5;



FIG. 8 is an illustration of a graphical user interface initiated after selection of one of the “FORWARD”, “REPLY”, or “NEW” icons in accordance with one embodiment of the present invention;



FIG. 9 is a flowchart illustrating the continued operation of the present invention upon the selection of the “SEND” or other similar icon on the graphical user interface of FIG. 8;



FIG. 10 is a flowchart illustrating the operations associated with the fetch e-mail operation of FIG. 9;



FIG. 11 is a flowchart illustrating the operations associated with the format and send message operation of FIG. 9;



FIG. 12 is a graphical user interface similar to that of FIG. 5 with the exception of an additional “unwanted electronic message” icon; and



FIG. 13 is a flowchart illustrating a server-based process initiated upon the selection of the additional “unwanted electronic message” icon of FIG. 12.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS


FIGS. 1 and 2 illustrate the geometric manner in which an electronic message may be distributed over a network in accordance with the prior art. FIGS. 3-13 illustrate a system for providing an application program adapted to be incorporated as a “payload” of an electronic message. Such application program is automatically initialized after the electronic message is selected by a user. After initialization, the application program is executed. The execution of the application program includes various features.


For example, such execution may include displaying text included with the first electronic message, displaying indicia, allowing entry of text, and sending the entered text and the application program over a network in a second electronic message to a second user upon selection of the indicia. In one embodiment, a code segment may be executed which includes as a parameter at least a portion of the text included with the electronic message, thus incorporating the text with any type of functionality, i.e. graphic, etc. Still yet, other features may be included such as an advertisement that is displayed only after the electronic message is forwarded a predetermined number of instances. Also, the text included with the electronic message may constitute a hyperlink which, when selected, links to a site and enters the text as a parameter upon such linking.


As will become apparent, the personal text of the electronic message may induce the user to open the mail while the functionality may serve as an inducement to send the electronic message to another user. This in turn may be used to incur visits to a particular site on the network. In the alternative, it may serve to afford widespread exposure of advertisements or any other feature that supports e-Commerce.



FIG. 3 illustrates an exemplary hardware configuration in accordance with one embodiment having a central processing unit 310, such as a microprocessor, and a number of other units interconnected via a system bus 312. The hardware configuration shown in FIG. 3 includes Random Access Memory (RAM) 314, Read Only Memory (ROM) 316, an I/O adapter 318 for connecting peripheral devices such as disk storage units 320 to the bus 312, a user interface adapter 322 for connecting a keyboard 324, a mouse 326, a speaker 328, a microphone 332, and/or other user interface devices such as a touch screen (not shown) to the bus 312, communication adapter 334 for connecting the hardware configuration to a communication network 335 (e.g., a wide area network) and a display adapter 336 for connecting the bus 312 to a display device 338.


The hardware configuration typically has resident thereon an operating system such as the Microsoft Windows NT or Windows/98/2000 Operating System (OS), the IBM OS/2 operating system, the MAC OS, or UNIX operating system. Those skilled in the art will appreciate that the present invention may also be implemented on platforms and operating systems other than those mentioned.



FIG. 4 is a flowchart illustrating the execution of the first application program associated with the first electronic message that is sent to a first user. The first electronic message may be received over any network such as a wide area network. In one embodiment, such wide area network may include the Internet and the first electronic message may be transmitted using a protocol such as TCP/IP and/or IPX. The first electronic message includes a first application program incorporated therein by any desired technique, along with a message, i.e. graphic, textual, audible, etc., generated by a previous user. In one embodiment, at least a portion of the first application program includes a JAVA APPLET. In the alternative, such first application program may include code segments written in any desired object-oriented computer programming or markup language.


As shown in operation 400 of FIG. 4, the first application program of the first electronic message is automatically initialized upon being selected, or “opened”, by a user on an electronic mail browser, i.e. NETSCAPE COMMUNICATOR, MICROSOFT OUTLOOK, etc. Such selection may include “clicking” on an identifier of the first electronic message, or any other technique enabled by the electronic mail browser. Upon such user action, the first electronic message is initialized immediately in an automated manner. To accomplish this, the first application program may depart from an “attachment” in the traditional sense, and be included in the first electronic message itself. Further, the electronic mail browser must be capable of automatically recognizing and executing the computer or markup language employed by the application program, a common capability among electronic mail browsers.


Initialization of the first application program may include determining various variables and other parameters required to execute the application program, or any other “pre-execution” duties. For example, one of such parameters may comprise the body of text included with the first electronic message.


In one embodiment, hypertext markup language may be included with the first electronic message to contain the parameters and call another portion of the first application program such as a JAVA APPLET located at another site on the network. It should be noted, however, that the hypertext markup language itself or any other computer or markup language included with first electronic message may constitute a component or an entirety of the first application program. In other words, any desired portion (including no portion) of the first application program may be positioned at a separate location on the network.


Following is an example of hypertext markup language for containing the parameters and calling another portion of the first application program. In the present embodiment, a portion of the first application program is called using a URL on the network.

    • <HTML>
    • <HEAD>
    • <TITLE>Practice Applets</TITLE>
    • </HEAD>
    • <BODY>
    • <APPLET CODEBASE=“http://www.esprinkles.com” CODE=“HelloAgainWorld.class” ARCHIVE=“eyejar.jar” WIDTH=1000 HEIGHT=1000 ALIGN=left>
    • <PARAM NAME=info VALUE=“ . . . body of text . . . ”>
    • <PARAM NAME=keystring VALUE=“I”>
    • </APPLET>
    • </BODY>
    • </HTML>


In operation 402 of FIG. 4, execution of the first application program has commenced and a layout manager is instantiated and installed. Layout managers are well known to those of ordinary skill in the art, and function to define the graphical framework during execution. Specifics regarding the graphical framework will be set forth in greater detail in the description of FIG. 5.


Thereafter, in operation 404, a particular key string parameter is retrieved in addition to the entire body of text. The key string parameter may include a particular string of text that is included in the body of text. In one embodiment, the word “I” may be retrieved as the key string parameter. In still other embodiments, any other letter, expression, word, phrase, pattern, format, etc. may be used as a key string parameter.


Next, each word and/or phrase of the body of text is retrieved in operation 405, and compared with the key string parameter to determine whether there is a match in decision 406. To accomplish this, a parser such as ANTLR may be employed to identify the designated letter, expression, word, phrase, pattern, format, etc. If it is determined that a match does not exist, a convention label is instantiated for simply displaying the current word and/or phrase in operation 408. On the other hand, if it is determined that a match does indeed exist, a functionality is instantiated which incorporates the key string parameter in operation 410. It is then determined in decision 412 whether all of the words and/or phrases of the body of text have been compared. If not, the process operations 405-410 are repeated.



FIG. 5 is an illustration of a graphical user interface of the present invention that is displayed upon the execution of the first application program, and which is used to display the text of the first electronic message and any functionality associated therewith. As shown, a frame 500 of the network browser encompasses a text box 502. Such text box includes the body of text 504. Further, a plurality of first indicia 506 is displayed in or around the text box. In one embodiment, the first indicia may include a “FORWARD”, “REPLY”, and/or a “NEW” icon.



FIG. 6 illustrates one example of the functionality displayed upon execution of the first application program. In such embodiment, the key string parameter is “I”, and an eyeball 600 is graphically depicted in place of the key string parameter within the textbox 502. During use, the movement of the eyeball 600 may be adapted to coincide with the movement of a mouse cursor 602. This may be accomplished using a “mouse listener” which may interface with the first application program. Mouse listeners track a current position of mouse cursors. It should be noted that in various alternate embodiments, any type of user input may be used to change various aspects, i.e. graphic, textual, layout, color, sound, etc. of the first electronic message.


Programs that execute the foregoing eyeball graphic feature are commonly known to those of ordinary skill. Such programs commonly use atan2 in order to compute the angle between the eyeball and the mouse cursor. An example of a code segment that executes the mouse listener feature, and that calls the eyeball graphic feature is as follows:

















import java.applet.*;




import java.awt.*;




import java.lang.*;




import java.util.*;




import java.awt.event.*;




import java.net.*;




public class HelloAgainWorld extends Applet




{




 Image backBuffer;




 Graphics backG;




 String s = ″null″;




 public void init( )




 {




  //this.setLayout(null);




  this.setLayout(new FlowLayout(FlowLayout.LEFT));




  s= getParameter(″info″);




  StringTokenizer parser = new StringTokenizer(s);




  try




  {




   while(parser.hasMoreTokens( ))




    {




     String a = parser.nextToken( );




     if (a.equals(″I″))




     {




      Eyeball2 eye = new Eyeball2(this);




      eye.setSize(30, 30);




      add(eye);




      Clicker click = new Clicker(this);




      eye.addMouseListener(click);




     }




     else




     {




      Label helloLabel = new Label( );




      helloLabel.setText(a);




      helloLabel.setForeground(new Color(170, 27, 140));




      add(helloLabel);




     }




    }




   }




   catch (NoSuchElementException e)




   {




   }




 }




 public void paint(Graphics g)




 {




      maintain( );




      super.paint(backG);




       g.drawImage(backBuffer, 0, 0, null);




 }




 public void update(Graphics g)




 {




       maintain( );




       super.update(backG);




       g.drawImage(backBuffer, 0, 0, null);




 }




 void maintain( )




 {




       // Maintain the back buffer and the graphics




context that is directed towards the back buffer.




       {




        int w = getBounds( ).width;




        int h = getBounds( ).height;




        // If there is no buffer or it is the wrong width,




or it is the wrong height, then adjust the back buffer.




        if ( backBuffer == null | | backBuffer.




getWidth(null) != w | | backBuffer.getHeight(null) != h )




        {




         // Adjust the back buffer.




         backBuffer = createImage( w, h );




         // If we have a backBuffer, then make a




graphics context that is directed towards the back buffer.




         if (backBuffer != null)




         {




          // Dispose of any previous graphics context




that may have pointed to a previous back buffer.




          if( backG != null )




          {




           backG.dispose( );




          }




          // Now create the graphics context that is




directed to the back buffer.




          backG = backBuffer.getGraphics( );




         }




       }




     }




   }




}




class Clicker implements MouseListener




{




 Applet a;




 URL url;




  Clicker(Applet _a)




  {




   a = _a;




  }




  public void mouseClicked(MouseEvent evt)




  {




  }




  public void mousePressed(MouseEvent evt)




  {




  }




 public void mouseReleased(MouseEvent evt)




 {




  AppletContext ac = a.getAppletContext( );




  try




  {




   url = new URL(″http://207.82.252.253/cgi-bin/linkrd?




lang=&hm action=http%3a%2f%2fwww%2eneostar%2ecom″);




  }




  catch (MalformedURLException e)




  {




   System.out.println(″I was a malformed url″);




  }




  ac.showDocument(url);




 }




 public void mouseEntered(MouseEvent evt)




 {




 }




 public void mouseExited(MouseEvent evt)




 {




 }




}









It should be noted that any type of functionality may be incorporated during the execution of the first application program. For example, advertisements may be displayed, etc.



FIG. 7 illustrates the execution of the second application program of the present invention which is initiated upon the selection of one of the first indicia 506, i.e. the “FORWARD”, “REPLY”, and/or “NEW” icon, displayed in the graphical user interface of FIG. 5. It should be noted that, in a “server-based” embodiment, selection of one of the first indicia 506 may initiate a link to a site on the network, thus allowing interaction with the site to afford functionality similar to that afforded by the second application program. To accomplish this, each button may be generated using HTML and have a unique URL associated therewith. As an option, a user may simply access the site on the network to send an electronic message without having to first receive a message.


In particular, it will be assumed in the present description that the “NEW” icon has been selected. It should be noted, however, that given the present description it would be well within the ability of one of ordinary skill to implement the “FORWARD” and “REPLY” functions. With respect to the “REPLY” icon, there may be a need for a mechanism of transferring the body of text from the first application program to the second application program. This may be accomplished by a “cookie” or similar metadata-type information.


As shown in FIG. 7, a second application program is initialized upon the selection of the first indicia 506 in operation 700. It should be noted that, in one embodiment, the second application program may be a component of the first application program thus rendering a single application program. In one embodiment, the first application program includes an un-signed application program and the second application program includes a signed application program. Still yet, in the server-based embodiment, interaction with the site on the network is effected in lieu of the initialization of the second application program.


Similar to the first application program, initialization of the second application program may include determining various variables, and other parameters required to execute the application program. Next, in operation 702, text fields are installed for allowing entry of text by the first user.



FIG. 8 is an illustration of a graphical user interface associated with the continued operation of the present invention after the selection of one of the first indicia 506 of FIG. 5. As shown, a plurality of text fields 801 are displayed within the frame 500 of the network browser. Included are a destination text box 800 for allowing the insertion of an electronic mail address of a desired destination, a subject text box 802 for allowing entry of a subject of a message, a body text box 804 for allowing entry of a body of text or message, and a key word text box 806 which is adapted for allowing entry of the key string parameter. Also included is second indicia 808 which may take the form of a “SEND” icon or the like.



FIG. 9 is a flowchart illustrating the continued operation of the present invention upon the selection of the second indicia 808, i.e. “SEND”, on the graphical user interface of FIG. 8. As shown, in operation 900, the text is first retrieved from the text fields 801 of the graphical user interface of FIG. 8. Next, in operation 902, the text is verified to ensure that each of the necessary text fields are filled and valid. For example, the text boxes 800 and 804 may be required.


If it is determined by decision 903 that the verification of operation 902 fails, a complaint is issued in operation 904. Such complaint may take the form of a pop-up window or the like, and may describe the nature of any defects. On the other hand, if the verification of operation 902 succeeds and all of the necessary fields are filled, information associated with an electronic mail server of the first user is retrieved in operation 905. This may be accomplished by accessing a hard drive of a computer of the first user which is running the network browser and electronic mail browser. The purpose of obtaining this information is to identify a server from which the information in the text fields 801 may be sent in the form of a second message. In the alternative, a single designated server may be automatically identified by the second application program, thus obviating the need to access the hard drive of the computer of the first user.


Upon identifying a server from which the second message is to be sent, the second electronic message may be formatted and sent to a second user in operation 906. Upon being sent, another verification may be executed in decision 908 in order to ensure that the second electronic message was sent in a satisfactory manner. If successful transmittal of the message is not verified, a complaint may be issued in a manner similar to that discussed hereinabove with respect to operation 904.


If, on the other hand, successful transmittal of the message is verified in decision 908, the second application program may optionally link the first user to a site on the network in operation 910. Such site may be identified by the second application program. This feature may thus be used to increase a number of visits, or “hits”, on a particular site which in itself may warrant substantial consideration.



FIG. 10 is a flowchart illustrating the operations associated with the fetch e-mail operation 905 of FIG. 9. As mentioned earlier, this may be accomplished by accessing a hard drive of a computer of the first user which is running the network browser and electronic mail browser. Before this may be effected, in operation 1000, the browser(s) that is currently in use may be detected after which the appropriate information may be accessed in operation 1002. As an option, permission to retrieve such information may be gained from the first user prior to any action being taken.



FIG. 11 is a flowchart illustrating the operations associated with the format and send message operation 906 of FIG. 9. The format refers to the hypertext mark-up language of which an example was provided earlier. In order to generate such format, a string is first created in operation 1100. Thereafter, a preamble is appended to the string in operation 1102. Thereafter, the body of text and key string parameters are appended in operations 1104 and 1106 after which a postscript is appended in operation 1108. An example of each of the foregoing appended elements are outlined as follows using the example set forth earlier:


Preamble





    • <HTML>

    • <HEAD>

    • <TITLE>Practice Applets</TITLE>

    • </HEAD>

    • <BODY>

    • <APPLET CODEBASE=“http://www.esprinkles.com” (*1st app. program*) CODE=“HelloAgainWorld.class” ARCHIVE=“eyejar.jar” WIDTH=1000 HEIGHT=1000 ALIGN=left>





Parameter





    • <PARAM NAME=info VALUE=“ . . . body of text . . . ”>





Parameter





    • <PARAM NAME=keystring VALUE=“I”>





Note: multiple key strings and adaptive keys may be used to identify the letter, expression, word, phrase, pattern, format, etc.


Postscript





    • </APPLET>

    • </BODY>

    • </HTML>





With continuing reference to FIG. 11, a message object is then created in operation 1110. Thereafter, the string and appendages, or message data, is attached to the object in operation 1112 using the JAVA mail API. Using the information collected about the server, a connection is then effected with the desired host mail server (SMTP or the like) in operation 1114 after which the message object and data are sent in operation 1116. In the case of multiple electronic mail destinations, this operation may be repeated as many times as required. An error status is then retrieved in operation 1118 to enable the decision 908 of FIG. 9. Next, the server is disconnected in operation 1120 and the error status is returned in operation 1122. It should be noted that submission of the data may be accomplished in any form submit-type process.


One example of functionality that may be implemented by the first application program was shown in FIG. 6. It should be noted, however, that any type of functionality may be employed by running a code segment including as a parameter at least a portion of the text included with the electronic message.


In various embodiments, the functionality may include the incorporation of an image, video, a specific graphic feature, or any other type of object for that matter. For example, any type of theme such as rabbits, earthquakes, time, popular icons and trademarks may be employed during the display of the text associated with the electronic message. As an option, such graphics may in some way interact with the text of the electronic message.


For example, where the theme is earthquakes, the text may be shown to shutter or the like. Or, where the theme is rabbits, the rabbits may be shown hopping from word to word. Still yet another example includes dressing or undressing an icon in various attire or providing any other type of feedback based on user input. Further, where the theme is time, a format of a time, i.e. “7:00”, may be detected in order to replace the same with an analog clock graphic which corresponds with the detected time.


As an option, the selection of the graphic or icon may initiate a link to a predetermine site on the network. Still yet, the application program may be adapted to allow the object to be substituted with any of the strings of the text while it is being shown. This may be accomplished with a select and “drag” feature.


In another embodiment, the execution of the first application program may include linking a string of the text of the first electronic message with a site on the network. In other words, such string constitutes a hyperlink. In such embodiment, the execution of the first application program may further include automatically inputting the string as a parameter to the site on the network upon selection of the hyperlink for various purposes. In the case where the site is a search engine, the string may be automatically entered as a search term in the search engine upon the selection of the hyperlink, thus prompting immediate reaction by the search engine. One example of an implementation of this concept is as follows:


http://www.search_engine.com/?MT=keystring&SM=MC&DV=0&LG=any&DC=10&DE=2&_v=2&OPs=MDRTP


In still another embodiment, the functionality associated with the electronic messages provides an inducement for sending them to additional users. With this exposure, the present invention may be used to propagate advertisements over the network. First, the electronic message is provided with the application program attached thereto which is capable of displaying an advertisement. As the message is communicated over the network, each instance of such communication is detected.


As such, the number of the instances that the electronic message is communicated over the network may be traced. The advertisement is then displayed after a predetermined number of the instances greater than one has been tracked. By employing this technique, the users will not be thwarted from forwarding the electronic message until after a predetermined geometric propagation has already taken place. It should be noted that the foregoing tracking ability may also be used to base a determination of compensation from the advertiser.


As an option, the predetermined number may be based on a Fibonacci sequence for optimized perpetuance of the electronic message. Further, the predetermined number may be based on a generation of the electronic message. As an option, the advertisement may be displayed by automatically linking to a site on the network.



FIG. 12 is a graphical user interface similar to that of FIG. 5 with the exception of an additional “unwanted electronic message” icon 1200, or indicia, that is displayed upon execution of the first application program. Upon selection of such indicia, a server-based process is initiated to help preclude unwanted electronic messages, or “spam”, from being sent on a network.


To facilitate this, each message that is received by the user is assigned a unique identifier by the server by way of a common gateway interface (CGI) or the like. In one embodiment, such identifier may include a domain name. In yet another embodiment, the identifier may be a number that is randomly generated, but large enough to ensure uniqueness. This number may be stored in the first application as a parameter, or incorporated into the HTML associated with generating the “unwanted electronic message” icon 1200.


Upon selection of the “unwanted electronic message” icon 1200, the identifier of the electronic message is communicated on the network to a designated server. For reasons that will soon become apparent, content of the electronic message may optionally also be sent.



FIG. 13 is a flowchart illustrating a server-based process initiated upon the selection of the additional “unwanted electronic message” icon of FIG. 12 and the receipt of the identifier and content by the server. As shown, the identifier and content of the unwanted message are received in operation 1300. Thereafter, the unique number is looked-up in operation 1302 in order to retrieve associated information on the source of the unwanted electronic message in operation 1304. In the case where the identifier is a number, such number may be used to ascertain the domain name of the message which may be stored with the identifier at the time of transmission. A counter associated with the domain name or the electronic message itself is then incremented in operation 1305.


Thereafter, in decision 1306, a number of identifiers identifying the same unwanted message or messages from the same source (domain name) is tracked for the purpose of determining whether a tolerance has been exceeded. In other words, it is determined whether such occurrences have exceeded a predetermined level. If not, the identifiers are continuously tracked.


If, however, the tolerance has been exceeded, the unwanted electronic message is reported in operation 1308 for preventing proliferation of the electronic message, similar messages, and/or messages from a similar source. In addition to reporting the message, the server itself may even take active measures to filter or eliminate the electronic message, similar messages, and/or messages from a similar source.


As an option, the content of the electronic message may also be reported in operation 1310 to the list, thus allowing the prevention of transmission of any subsequent electronic messages having content substantially similar to the received content. It should be noted that “lists” are commonly known as a means of preventing the proliferation of already identified unwanted electronic messages. Still yet another option may include sending the user a notice that the report has been received.


While this invention has been described in terms of several preferred embodiments, it is contemplated that alternatives, modifications, permutations, and equivalents thereof will become apparent to those skilled in the art upon a reading of the specification and study of the drawings. It is therefore intended that the true spirit and scope of the present include all such alternatives, modifications, permutations, and equivalents.

Claims
  • 1. A method, comprising: at a computer with a processor and a display: receiving an electronic message that is sent over a network, the electronic message including a body of text including one or more words to be displayed to a receiving user, anda first portion of a first application program, the first application program including functionality for displaying advertisements on the display;after receiving the electronic message, detecting selection of the electronic message; and,in response to detecting selection of the electronic message: opening the electronic message,displaying the body of text on the display, andexecuting the first portion of the first application program, which calls a second portion of the first application program using as a parameter at least a portion of the one or more words displayed to the receiving user, the second portion of the first application program being located at a site on the network that is remote from the computer, thereby retrieving an advertisement and displaying the advertisement on the display.
  • 2. The method of claim 1, wherein the first portion of the first application program is included in the electronic message and is not an attachment to the electronic message.
  • 3. The method of claim 1, wherein executing the first application program in response to detecting selection of the electronic message includes displaying an object on the display.
  • 4. The method of claim 3, wherein the object is an image or video.
  • 5. The method of claim 3, wherein the object is a graphic or icon and selection of the object initiates linking to a predetermined site on the network.
  • 6. The method of claim 3, wherein the object interacts with the body of text on the display.
  • 7. The method of claim 6, wherein the object moves from word to word in the body of text on the display.
  • 8. A non-transitory computer readable medium containing a computer program, the computer program including instructions for: at a computer with a processor and a display:receiving an electronic message that is sent over a network, the electronic message including a body of text including one or more words to be displayed to a receiving user, anda first portion of a first application program, the first application program including functionality for displaying advertisements on the display;after receiving the electronic message, detecting selection of the electronic message; and,in response to detecting selection of the electronic message: opening the electronic message,displaying the body of text on the display, andexecuting the first portion of the first application program, which calls a second portion of the first application program using as a parameter at least a portion of the one or more words displayed to the receiving user, the second portion of the first application program being located at a site on the network that is remote from the computer, thereby retrieving an advertisement and displaying the advertisement on the display.
  • 9. The non-transitory computer readable medium of claim 8, wherein the first portion of the first application program is included in the electronic message and is not an attachment to the electronic message.
  • 10. The non-transitory computer readable medium of claim 8, wherein executing the first application program in response to detecting selection of the electronic message includes displaying an object on the display.
  • 11. The non-transitory computer readable medium of claim 10, wherein the object is an image or video.
  • 12. The non-transitory computer readable medium of claim 10, wherein the object is a graphic or icon and selection of the object initiates linking to a predetermined site on the network.
  • 13. The non-transitory computer readable medium of claim 10, wherein the object interacts with the body of text on the display.
  • 14. The non-transitory computer readable medium of claim 13, wherein the object moves from word to word in the body of text on the display.
  • 15. A computer system, comprising one or more processors; andmemory for storing a computer program for execution by the one or more processors, the computer program including instructions for:receiving an electronic message that is sent over a network, the electronic message including a body of text including one or more words to be displayed to a receiving user, anda first portion of a first application program, the first application program including functionality for displaying advertisements on the display;after receiving the electronic message, detecting selection of the electronic message; and,in response to detecting selection of the electronic message: opening the electronic message,displaying the body of text on the display, andexecuting the first portion of the first application program, which calls a second portion of the first application program using as a parameter at least a portion of the one or more words displayed to the receiving user, the second portion of the first application program being located at a site on the network that is remote from the computer system, thereby retrieving an advertisement and displaying the advertisement on the display.
  • 16. The system of claim 15, wherein the first portion of the first application program is included in the electronic message and is not an attachment to the electronic message.
  • 17. The system of claim 15, wherein executing the first application program in response to detecting selection of the electronic message includes displaying an object on the display.
  • 18. The system of claim 17, wherein the object is an image or video.
  • 19. The system of claim 17, wherein the object is a graphic or icon and selection of the object initiates linking to a predetermined site on the network.
  • 20. The system of claim 17, wherein the object interacts with the body of text on the display.
  • 21. The system of claim 20, wherein the object moves from word to word in the body of text on the display.
US Referenced Citations (218)
Number Name Date Kind
5283856 Gross Feb 1994 A
5297143 Fridrich et al. Mar 1994 A
5396588 Froessl Mar 1995 A
5428784 Cahill, Jr. Jun 1995 A
5513126 Harkins et al. Apr 1996 A
5548745 Egan et al. Aug 1996 A
5557320 Krebs Sep 1996 A
5572648 Bibayan Nov 1996 A
5619648 Canale et al. Apr 1997 A
5634005 Matsuo May 1997 A
5659729 Nielsen Aug 1997 A
5694616 Johnson et al. Dec 1997 A
5724521 Dedrick Mar 1998 A
5740252 Minor et al. Apr 1998 A
5740374 Raffali-Schreinemachers Apr 1998 A
5754939 Herz et al. May 1998 A
5774170 Hite et al. Jun 1998 A
5774534 Mayer Jun 1998 A
5781901 Kuzma Jul 1998 A
5790789 Suarez Aug 1998 A
5790793 Higley Aug 1998 A
5793972 Shane Aug 1998 A
5799267 Siegel Aug 1998 A
5806043 Toader Sep 1998 A
5809242 Shaw et al. Sep 1998 A
5815830 Anthony Sep 1998 A
5818447 Wolf et al. Oct 1998 A
5825865 Oberlander et al. Oct 1998 A
5826023 Hall et al. Oct 1998 A
5826062 Fake, Jr. et al. Oct 1998 A
5832208 Chen et al. Nov 1998 A
5832502 Durham et al. Nov 1998 A
5838790 McAuliffe et al. Nov 1998 A
5848397 Marsh Dec 1998 A
5856825 Yumoto et al. Jan 1999 A
5859636 Pandit Jan 1999 A
5867494 Krishnaswamy et al. Feb 1999 A
5870549 Bobo, II Feb 1999 A
5884246 Boucher et al. Mar 1999 A
5897635 Torres et al. Apr 1999 A
5903269 Poreh et al. May 1999 A
5909545 Frese, II et al. Jun 1999 A
5918014 Robinson Jun 1999 A
5937160 Davis et al. Aug 1999 A
5937162 Funk et al. Aug 1999 A
5937392 Alberts Aug 1999 A
5946386 Rogers et al. Aug 1999 A
5948061 Merriman et al. Sep 1999 A
5950215 Tabuchi Sep 1999 A
5956486 Hickman et al. Sep 1999 A
5983190 Trower, II et al. Nov 1999 A
5983200 Slotznick Nov 1999 A
6002393 Hite et al. Dec 1999 A
6009410 LeMole et al. Dec 1999 A
6009462 Birrell et al. Dec 1999 A
6011537 Slotznick Jan 2000 A
6014134 Bell et al. Jan 2000 A
6014502 Moraes Jan 2000 A
6014688 Venkatraman et al. Jan 2000 A
6014689 Budge et al. Jan 2000 A
6014698 Griffiths Jan 2000 A
6016520 Facq et al. Jan 2000 A
6021427 Spagna et al. Feb 2000 A
6023729 Samuel et al. Feb 2000 A
6026437 Muschett et al. Feb 2000 A
6035104 Zahariev Mar 2000 A
6047310 Kamakura et al. Apr 2000 A
6049778 Walker et al. Apr 2000 A
6052709 Paul Apr 2000 A
6055510 Henrick et al. Apr 2000 A
6061698 Chadha et al. May 2000 A
6061719 Bendinelli et al. May 2000 A
6064990 Goldsmith May 2000 A
6065001 Ohkubo et al. May 2000 A
6067570 Kreynin et al. May 2000 A
6073167 Poulton et al. Jun 2000 A
6078320 Dove et al. Jun 2000 A
6092101 Birrell et al. Jul 2000 A
6092104 Kelly Jul 2000 A
6101532 Horibe et al. Aug 2000 A
6108709 Shinomura et al. Aug 2000 A
6134243 Jones et al. Oct 2000 A
6134532 Lazarus et al. Oct 2000 A
6138149 Ohmura Oct 2000 A
6141684 McDonald et al. Oct 2000 A
6144987 Niemi Nov 2000 A
6154764 Nitta et al. Nov 2000 A
6157721 Shear et al. Dec 2000 A
6161130 Horvitz et al. Dec 2000 A
6167251 Segal et al. Dec 2000 A
6167395 Beck et al. Dec 2000 A
6167434 Pang Dec 2000 A
6173337 Akhond et al. Jan 2001 B1
6185605 Kowaguchi Feb 2001 B1
6199103 Sakaguchi et al. Mar 2001 B1
6199106 Shaw et al. Mar 2001 B1
6205432 Gabbard et al. Mar 2001 B1
6208998 Marcus Mar 2001 B1
6212554 Roskowski Apr 2001 B1
6219054 Komoda et al. Apr 2001 B1
6223213 Cleron et al. Apr 2001 B1
6225993 Lindblad et al. May 2001 B1
6233317 Homan et al. May 2001 B1
6233600 Salas et al. May 2001 B1
6249805 Fleming, III Jun 2001 B1
6252588 Dawson Jun 2001 B1
6253231 Fujii Jun 2001 B1
6256663 Davis Jul 2001 B1
6272493 Pasquali Aug 2001 B1
6272593 Dujari Aug 2001 B1
6275849 Ludwig Aug 2001 B1
6301710 Fujiwara Oct 2001 B1
6305942 Block et al. Oct 2001 B1
6311211 Shaw et al. Oct 2001 B1
6317722 Jacobi et al. Nov 2001 B1
6323853 Hedloy Nov 2001 B1
6327612 Watanabe Dec 2001 B1
6332156 Cho et al. Dec 2001 B1
6336216 Curtis et al. Jan 2002 B1
6351763 Kawanaka Feb 2002 B1
6353926 Parthesarathy et al. Mar 2002 B1
6356937 Montville et al. Mar 2002 B1
6360221 Gough et al. Mar 2002 B1
6361326 Fontana et al. Mar 2002 B1
6366949 Hubert Apr 2002 B1
6381592 Reuning Apr 2002 B1
6381634 Tello et al. Apr 2002 B1
6385644 Devine et al. May 2002 B1
6389455 Fuisz May 2002 B1
6393463 Fuchigami May 2002 B1
6393465 Leeds May 2002 B2
6400810 Skladman et al. Jun 2002 B1
6405243 Nielsen Jun 2002 B1
6405244 Bando et al. Jun 2002 B1
6415332 Tuel, Jr. Jul 2002 B1
6427164 Reilly Jul 2002 B1
6438583 McDowell et al. Aug 2002 B1
6442600 Anderson Aug 2002 B1
6449635 Tilden, Jr. et al. Sep 2002 B1
6449657 Stanbach, Jr. et al. Sep 2002 B2
6463463 Godfrey et al. Oct 2002 B1
6499108 Johnson Dec 2002 B1
6510438 Hasegawa Jan 2003 B2
6516351 Borr Feb 2003 B2
6529936 Mayo et al. Mar 2003 B1
6529946 Yokono et al. Mar 2003 B2
6549612 Gifford et al. Apr 2003 B2
6593973 Sullivan et al. Jul 2003 B1
6609196 Dickinson, III et al. Aug 2003 B1
6611812 Hurtado et al. Aug 2003 B2
6633316 Maddalozzo, Jr. et al. Oct 2003 B1
6636888 Bookspan et al. Oct 2003 B1
6651087 Dennis Nov 2003 B1
6654779 Tsuei Nov 2003 B1
6654787 Aronson et al. Nov 2003 B1
6668278 Yen et al. Dec 2003 B1
6684332 Douglas Jan 2004 B1
6697842 Smith et al. Feb 2004 B1
6721784 Leonard et al. Apr 2004 B1
6731314 Cheng et al. May 2004 B1
6732149 Kephart May 2004 B1
6745226 Guedalia Jun 2004 B1
6757714 Hansen Jun 2004 B1
6757720 Weschler, Jr. Jun 2004 B1
6760750 Boneh et al. Jul 2004 B1
6769130 Getsin et al. Jul 2004 B1
6775689 Raghunandan Aug 2004 B1
6779178 Lloyd et al. Aug 2004 B1
6785867 Shaffer et al. Aug 2004 B2
6792082 Levine Sep 2004 B1
6873982 Bates et al. Mar 2005 B1
6892226 Tso et al. May 2005 B1
6944621 Collart Sep 2005 B1
6964012 Zirngibl et al. Nov 2005 B1
6981214 Miller et al. Dec 2005 B1
7051019 Land et al. May 2006 B1
7089194 Berstis et al. Aug 2006 B1
7158986 Oliver et al. Jan 2007 B1
7222159 Miller et al. May 2007 B2
7356332 Pell et al. Apr 2008 B2
7493390 Bobde et al. Feb 2009 B2
20010044828 Kikinis Nov 2001 A1
20020007356 Rice et al. Jan 2002 A1
20020010794 Stanbach, Jr. et al. Jan 2002 A1
20020032738 Foulger et al. Mar 2002 A1
20020056123 Liwerant et al. May 2002 A1
20020059347 Shaffer et al. May 2002 A1
20020075305 Beaton et al. Jun 2002 A1
20020112005 Namias Aug 2002 A1
20020112007 Wood et al. Aug 2002 A1
20020138588 Leeds Sep 2002 A1
20020152272 Yairi Oct 2002 A1
20020188683 Lytle et al. Dec 2002 A1
20020199095 Bandini et al. Dec 2002 A1
20030018816 Godfrey et al. Jan 2003 A1
20030095642 Cloutier et al. May 2003 A1
20030126215 Udell et al. Jul 2003 A1
20030135567 Reilly Jul 2003 A1
20030135853 Goldman et al. Jul 2003 A1
20030217005 Drummond et al. Nov 2003 A1
20050081059 Bandini et al. Apr 2005 A1
20050204011 Velayudham Sep 2005 A1
20050228899 Wendkos et al. Oct 2005 A1
20050246752 Liwerant et al. Nov 2005 A1
20050256929 Bartol et al. Nov 2005 A1
20050261011 Scott Nov 2005 A1
20060009249 Fu et al. Jan 2006 A1
20060010214 McDowell et al. Jan 2006 A1
20060026438 Stem et al. Feb 2006 A1
20060168346 Chen et al. Jul 2006 A1
20070087766 Hardy et al. Apr 2007 A1
20070250586 Kirsch Oct 2007 A1
20080071612 Mah et al. Mar 2008 A1
20080133716 Rao et al. Jun 2008 A1
20080195953 Sen Aug 2008 A1
20090100378 Klassen et al. Apr 2009 A1
20100017864 Codignotto Jan 2010 A1
20100325728 Pang Dec 2010 A1
Foreign Referenced Citations (4)
Number Date Country
0 631 419 Mar 1996 EP
2001111601 Apr 2001 JP
WO 9858321 Dec 1998 WO
WO 9858332 Dec 1998 WO
Non-Patent Literature Citations (106)
Entry
Yourdon, Java, The Web and Software Development, IEEE 1996.
World Wide Web e-mail service provider Hotmail (hereinafter “Hotmail”) available through the web site http://www.msn.com provided by the Microsolft Corporation, Exhibit A pp. 1 through 3 3nclosed herewith is a print out of displays of another feature of Hotmail called Mail Handling.
Real Networks, Inc. (hereinafter “RealNetworks”) a corporation with headquarters at 2601 Elliott Avenue, Suite 1000, Seattle, WA 98121, offers a line of products that include Real Player and Real Audio and the like. Versions of these products may be downloaded from the Internet at http://www.real.com.
Exhibit B is a print out of a page from Activegrams with the address: http://www.activegrams.com?cgi-bin/viewactivegrams.cgi?dadbday on Sep. 26, 1999.
Exhibit C, which is a print out of apage from Activegrams with the address: http://www.activegrams.com?cgi-bin/viewactivegrams?cgi?1411215ki on Sep. 21, 1999.
The Internet article, “Death to Spam, A Guide to Dealing with Unwanted E-Mail” (herein after Death to Spam) obtained from the World Wide Web Address http://www.mindworkshop.com/alchemy/nospam.html on Sep. 21, 1999.
The Internet article, “What can you do about bad email?” (herein after “Bad Email”) obtained from the World Wide Web address http://www.oitc.com/Disney/WhatToDo.html, on Sep. 21, 1999.
The Internet article, “The Anti-Spam HOWTO” obtained from the World Wide Web address http://www.zikzak.zikzak.net/˜acb/features/anit-spam-howto.html on Sep. 21, 1999.
The Internet article, “no Junk E-Mail Database” (herein after “No Junk E-Mail”) obtained from the World Wide Web address http://www.glr.com/nojunk.html on Sep. 21, 1999.
The pages obtained on Sep. 21, 1999 from the website entitled “Do-Not-Spam.com” located at the World Wide Web address http://www.do-not-spam.com/.
An Access Control System for Multimedia Applications—Alexandros Kadoglou; poseidon.csd.auth.gr/papers/PUBLISHED/CONFERENCE/Kadoglou97a/Kadoglou97a.ps.Z.
World Wide Web Security; www.cs.jmu.edu/common/coursedocs/cs685c/...b—security.html, May 1999.
Alvear J., “Streaming E-Mail”, Web Oevelopper.Com Guide to Streaming Multimedia, New York: John Wiley & Sons, US, pp. 304-317 (1998), XP-002150023.
Tolba et aL, “Pure Java-based Streaming MPEG Player”, part ofthe SPIE Conference on Multimedia Systems and Applications, Boston Massachusetts, Nov. 1998. SPIE vol. 3528, pp. 216-224.
Tech Web Encyclopedia, “Streaming” definition, 1 page.
Heinz Tschabitcher; How to mail all address book entries in windown live mail or outlook express; About.com; 2 Pages.
The article, “Enhancing documents with embedded programs: How Ness extends insets in the Andrew ToolKit” obtained from CH2854-8/90/0000/0023$01.00 1990 IEEE.
The article, “Object-oriented design of a Message Handling System protocol”, obtained from CCECE/CCGEI'95.
The article, “Secure Offical Document Mail Systems for Office Automation”, obtained from 0/7803-3913-4-9/$4.00, 1997 IEEE.
The Internet article, “Digital Multimedia Content Management for Networked Information Access: Issues and Discussion” obtained from heathery@research.panasonic.com.
The article, “Consumer Electronics” obtained from IEEE Spectrum Jan. 1997.
The Internet article, “Windows 98 Installation & Configuration Handbook” obtained from website address http://cma.zdnet.com/book/win98config/ch17/ch17.htm.
Presentation on “JavaOS Based Network Computing”, from Sun's 1997 Worldwide Java Developer Conference.
A PhoneBoy Primer on: Tracking Down Spammers, Jul. 26, 1997, 2 pgs.
Erradey, Object-oriented design of a Message Handling System protocol, Canadian Conference on Electrical and Computer Engineering, 1995, vol. 2, Sep. 5-8, 1995, pates 842-845.
Gough, Decision on Appeal, U.S. Appl. No. 09/721,552, Sep. 25, 2012, 12 pgs.
Gough, Decision on Appeal, U.S. Appl. No. 09/997,322, Sep. 17, 2012, 18 pgs.
Gough, Examiner's Answer, U.S. Appl. No. 09/721,552, Dec. 20, 2010, 23 pgs.
Gough, Examiner's Answer, U.S. Appl. No. 09/997,322, Jun. 23, 2010, 26 pgs.
Gough, Examiner's Answer, U.S. Appl. No. 12/142,764, Feb. 16, 2012, 27 pgs.
Gough, Final Office Action, U.S. Appl. No. 09/400,708, Jul. 11, 2005, 6 pgs.
Gough, Final Office Action, U.S. Appl. No. 09/400,708, Nov. 21, 2002, 9 pgs.
Gough, Final Office Action, U.S. Appl. No. 09/400,711, Sep. 10, 2003, 7 pgs.
Gough, Final Office Action, U.S. Appl. No. 09/401,026, Jan. 4, 2001, 8 pgs.
Gough, Final Office Action, U.S. Appl. No. 09/401,028, Nov. 18, 2002, 8 pgs.
Gough, Final Office Action, U.S. Appl. No. 09/493,468, Sep. 2, 2008, 24 pgs.
Gough, Final Office Action, U.S. Appl. No. 09/493,468, Jun. 25, 2012, 22 pgs.
Gough, Final Office Action, U.S. Appl. No. 09/493,468, Aug. 30, 2010, 22 pgs.
Gough, Final Office Action, U.S. Appl. No. 09/721,552, Aug. 19, 2005, 17 pgs.
Gough, Final Office Action, U.S. Appl. No. 09/997,322, Aug. 10, 2007, 10 pgs.
Gough, Final Office Action, U.S. Appl. No. 09/997,322, Dec. 22, 2008, 17 pgs.
Gough, Final Office Action, U.S. Appl. No. 12/142,606, Oct. 7, 2010, 14 pgs.
Gough, Final Office Action, U.S. Appl. No. 12/142,715, Mar. 2, 2012, 11 pgs.
Gough, Final Office Action, U.S. Appl. No. 12/142,728, Aug. 29, 2013, 18 pgs.
Gough, Final Office Action, U.S. Appl. No. 12/142,745, Feb. 3, 2012, 9 pgs.
Gough, Final Office Action, U.S. Appl. No. 12/142,750, Jun. 22, 2011, 21 pgs.
Gough, Final Office Action, U.S. Appl. No. 12/142,764, Nov. 24, 2010, 16 pgs.
Gough, Final Office Action, U.S. Appl. No. 12/143,785, Dec. 17, 2012, 9 pgs.
Gough, Final Office Action, U.S. Appl. No. 12/143,785, Oct. 22, 2010, 16 pgs.
Gough, Final Office Action, U.S. Appl. No. 12/143,786, Nov. 23, 2011, 9 pgs.
Gough, Final Office Action, U.S. Appl. No. 12/952,176, Oct. 28, 2013, 9 pgs.
Gough, Notice of Allowance, U.S. Appl. No. 09/400,708, Apr. 2, 2010, 4 pgs.
Gough, Notice of Allowance, U.S. Appl. No. 09/400,708, Dec. 2, 2009, 4 pgs.
Gough, Notice of Allowance, U.S. Appl. No. 09/400,708, Jul. 12, 2010, 4 pgs.
Gough, Notice of Allowance, U.S. Appl. No. 09/400,708, Jun. 25, 2004, 4 pgs.
Gough, Notice of Allowance, U.S. Appl. No. 09/400,708, Oct. 28, 2010, 4 pgs.
Gough, Notice of Allowance, U.S. Appl. No. 09/400,781, Aug. 12, 2003, 6 pgs.
Gough, Notice of Allowance, U.S. Appl. No. 09/401,026, Aug. 23, 2001, 3 pgs.
Gough, Notice of Allowance, U.S. Appl. No. 09/401,028, Jun. 17, 2003, 3 pgs.
Gough, Notice of Allowance, U.S. Appl. No. 09/997,322, Jul. 24, 2013, 6 pgs.
Gough, Office Action, U.S. Appl. No. 09/400,708, Jul. 9, 2008, 12 pgs.
Gough, Office Action, U.S. Appl. No. 09/400,708, Mar. 12, 2009, 12 pgs.
Gough, Office Action, U.S. Appl. No. 09/400,708, Mar. 13, 2006, 6 pgs.
Gough, Office Action, U.S. Appl. No. 09/400,708, Oct. 24, 2006, 8 pgs.
Gough, Office Action, U.S. Appl. No. 09/400,708, Sep. 24, 003, 6 pgs.
Gough, Office Action, U.S. Appl. No. 09/400,708, Mar. 27, 2002, 6 pgs.
Gough, Office Action, U.S. Appl. No. 09/400,711, Jun. 11, 2002, 7 pgs.
Gough, Office Action, U.S. Appl. No. 09/400,711, Mar. 13, 2003, 11 pgs.
Gough, Office Action, U.S. Appl. No. 09/400,711, Sep. 21, 2004, 14 pgs.
Gough, Office Action, U.S. Appl. No. 09/400,781, Dec. 16, 2002, 6 pgs.
Gough, Office Action, U.S. Appl. No. 09/400,781, Mar. 26, 2002, 5 pgs.
Gough, Office Action, U.S. Appl. No. 09/401,026, Aug. 2, 2000, 7 pgs.
Gough, Office Action, U.S. Appl. No. 09/401,028, Jun. 5, 2002, 6 pgs.
Gough, Office Action, U.S. Appl. No. 09/493,468, Dec. 5, 2007, 20 pgs.
Gough, Office Action, U.S. Appl. No. 09/493,468, Dec. 8, 2009, 23 pgs.
Gough, Office Action, U.S. Appl. No. 09/493,468, Oct. 12, 2011, 25 pgs.
Gough, Office Action, U.S. Appl. No. 09/493,468, Jan. 13, 2004, 11 pgs.
Gough, Office Action, U.S. Appl. No. 09/493,468, Nov. 21, 2002, 10 pgs.
Gough, Office Action, U.S. Appl. No. 09/493,468, Jul. 23, 2003, 11 pgs.
Gough, Office Action, U.S. Appl. No. 09/721,552, Mar. 1, 2005, 13 pgs.
Gough, Office Action, U.S. Appl. No. 09/721,552, Feb. 11, 2004, 10 pgs.
Gough, Office Action, U.S. Appl. No. 09/721,552, Jan. 22, 2010, 21 pgs.
Gough, Office Action, U.S. Appl. No. 09/997,322, Mar. 18, 2008, 14 pgs.
Gough, Office Action, U.S. Appl. No. 09/997,322, Aug. 25, 2004, 11 pgs.
Gough, Office Action, U.S. Appl. No. 09/997,322, Nov. 29, 2012, 5 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,606, Mar. 19, 2010, 12 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,606, Jan. 20, 2012, 22 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,715, Jun. 23, 2011, 14 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,728, Mar. 5, 2010, 10 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,728, Feb. 15, 2012, 14 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,728, Dec. 19, 2012, 20 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,728, Nov. 24, 2010, 10 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,728, Feb. 27, 2014, 18 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,745, Apr. 27, 2011, 8 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,750, Feb. 1, 2010, 9 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,750, Jun. 19, 2012, 18 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,750, Sep. 28, 2010, 16 pgs.
Gough, Office Action, U.S. Appl. No. 12/142,764, Mar. 15, 2010, 8 pgs.
Gough, Office Action, U.S. Appl. No. 12/143,785, Jan. 28, 2010, 12 pgs.
Gough, Office Action, U.S. Appl. No. 12/143,785, Jul. 28, 2011, 15 pgs.
Gough, Office Action, U.S. Appl. No. 12/143,786, Mar. 16, 2011, 8 pgs.
Gough, Office Action, U.S. Appl. No. 12/952,176, Jul. 31, 2012, 7 pgs.
Hansen, Enhancing documents with embedded programs: How Ness extends insets in the Andrew Toolkit, IEEE, 1990.
Pomeranz, Perl Practicum: The Emal of the Species, May 24, 1997.
Yang, Secure official document mail systems for office automation, Proceedings, Security Technology, 1997.
Yu, Digital multimedia content management for networked information access: issues and discussion, Advance Issues of E-Commerce and Web-Based Information Systems, WECWIS, 1999, Apr. 8-9, 1999, pp. 75-80.