Electronic message payload for interfacing with text contained in the message6704771Abstract The present invention includes a system, method, and article of manufacture for communicating via an application program included as a payload of an electronic message. At least one application program is initialized after an electronic message is selected by a user. After initialization, the application program is executed. The execution of the application program includes displaying text included with the electronic message, and running a code segment including as a parameter at least a portion of the text included with the electronic message. Claims What is claimed is: Description FIELD OF THE INVENTION
<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 .vertline..vertline.
backBuffer.getwidth(null) != w .vertline..vertline.
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.
|
Same subclass Same class Consider this |
||||||||||