fig1 is pictorial representation of the hierarchical structure of a user forum . in fig1 , a forum may include multiple topics and each topic many include many responses . there are two types of responses possible . the first type of response is a response to the topic itself . the second type of response is a response to a previously posted response . responses to responses may be nested . an exemplary set of responses is illustrated under topic 1 . the list of responses for a given topic and their interrelationship is called a thread . for clarity , responses to topics 2 through n are not illustrated . each response includes a posting date . a posting date includes a date stamp and may include a timestamp as well . a posting date is defined as the date or date and time on which a response to a forum topic or a response to a response is placed on the forum site . the present invention will be described in a www / internet environment . a person of ordinary skill in the art will understand that the invention is applicable to private networks such as local area networks ( lan ) s as well . fig2 is pictorial representation of the databases for tracking responses to a forum topic according to the present invention . in fig1 a shell database 100 is linked to a forum database 105 and a user account database 110 . shell database 100 includes web interface elements 115 , which essentially provide the means for displaying web pages and content . shell database 100 also includes an agent 120 that assembles periodic tracking emails . forum database 105 includes the hierarchy of topics and responses as illustrated in fig1 and described supra , for one or more forums . user account database 110 includes usernames , user passwords , user email addresses . user database also includes , for each user , a list of forums and topics ( hereafter called interests ), a temporal indication of when the last new responses were found for each interest and a cross reference to the actual file ids of the tracked forums and topics . the temporal indication of the last time there were new responses may be a date that the last periodic email was sent , a date and a time that the last periodic email was sent , a date that agent 120 was last run or a date and a time that agent 120 was last run . the initial value of the temporal indication is the date or the date and time that the interest was enabled for tracking . hereafter , the temporal indication of the time there were last new responses ( i . e . the date that the last periodic email was sent , the date and a time that the last periodic email was sent , the date that agent 120 was last run or the date and a time that agent 120 was last run , will be referred to as the last new response date . agent 120 provides three functions . the first function provided by agent 120 is to read a tracking view ( illustrated in fig5 and described infra ) based on each users interests and the last new response date . generation of the tracking view is illustrated in fig3 and described infra . the second function provided by agent 120 is to query forum database 105 for new responses . a new response is a response posted after the last new response date for a given interest . the third function of agent 120 is to cause a tracking email to be sent to each user having an interest to which a new response has been posted . after a tracking email is sent , agent 120 replaces the old last new response date with a new last new response date . tracking emails are sent only to users having an interest to which a new response to that interest has been posted . the content of a tracking email is either subjects of the responses themselves and a list of universal resource locators ( url ) pointing to the qualified responses . it is possible to include the entire response , but doing so requires more server resources than including just the subject and url of each response . fig3 is a block diagram of a server system for implementing the present invention . in fig3 , shell database 100 , forum database 105 and user accounts database 110 are contained in a web application server 125 . web application server 125 generates the tracking view , which is stored in user accounts database 110 . web application server 125 links to a multiplicity of user personal computers ( pcs ) 130 a through 130 x via the www . www may be replaced by a lan . each pc 130 a through 130 x includes an email client 135 for receiving email and a browser 140 for linking to web application server 125 via the www . an example of a browser is netscape ™. tracking emails are not sent by agent 120 , but rather by an email server 145 via www under the direction of agent 120 . as discussed supra , agent 120 assembles the tracking emails . fig4 is a flowchart illustrating the method of the present invention . in step 150 , the tracking view is generated . the tracking view is a list of users having interests that those users have indicated they want tracked . the tracking view is illustrated in fig5 and described infra . user selection of interests and tracking is discussed more fully infra , in reference to fig8 . in step 155 , the first or next user in the tracking view is selected . in step 160 , a blank email to the selected user is generated . in step 165 , the first / next interest for the current user is selected . in step 170 , the forum and topic of the current interest is queried for a response having a posting date or date and time later the last new response date . in step 175 , all new responses are selected . there may be multiple new responses . in step 180 , the new responses themselves or urls to the new responses are embedded in the tracking email . in step 185 , it is determined if there is another interest for the current user . if there is another interest for the current user , the method loops to step 165 . if all the interests for the current user have been selected then the method proceeds to step 190 . in step 190 , several tracking email options exist and one or more options are executed . if there are one or more new responses , the email is sent to the current user as a tracking email . if there are no new responses , no tracking email is sent . an optional feature is to send an advisory email that a forum , a topic or one or more responses are archived and not directly available . also , in step 190 , user accounts database 110 ( see fig2 ) is updated to reflect a new date or date and time of the last new responses . in step 195 , it is determined if there is another user in the tracking view . if there is another user , the method loops to step 155 . if all the users in the tracking view have been selected then the method terminates . fig5 is pictorial representation of a tracking view according to the present invention . a tracking view may exist in any number of forms dependent upon the software and server environment . a tracking view contains the entire information agent 120 ( see fig2 ) requires . in fig5 , the tracking view is organized into rows and columns . there are 1 through l rows , one row for each user . each user appears only once . the first column of each row contains the username , the second column the user email address . next are k interest columns subdivided into three sub - columns . the first sub - column identifies a tracked forum , the second sub - column identifies the topic and the third sub - column lists the last new response date . while the number of users may be unlimited or limited only by the physical constraints of the server , the number of tracked interests may be limited to the number k . for example , k may be 20 , thus forcing users to manage the number of interests they want tracked to prevent overloading agent 120 ( see fig2 ). fig6 is a flowchart of a first method for a user to set up response tracking according to the present invention . in step 200 , a user logs onto a website . in step 205 , the user selects a forum . in step 210 , the user selects a topic . in step 215 , the user request that the forum / topic be tracked and that tracking emails be sent . in step 220 , a screen is displayed on the user &# 39 ; s computer showing the user &# 39 ; s tracking selections and allowing tracking to be selectively enabled or disabled . this screen is illustrated in fig8 and described infra . in step 225 , an initial last new responses date is set to the current date or date and time . in step 230 , upon exiting the screen by returning to a forum or topic or exiting the website , the interests ( including forum and topic ) and the initial last new response date is stored in user accounts database 110 ( see fig2 ). in step 235 , the user either returns to a forum , a topic or logs off . note that steps 205 through 230 may be repeated as many times as the user goes to new forum and steps 210 through 230 may be repeated as many times as the user goes to new topics . fig7 is a flowchart of a second method for a user to set up response tracking according to the present invention . in step 250 , a user logs onto a website . in step 255 , the user selects a forum . in step 260 , the user selects a topic . in step 265 , the user posts a response or posts a new topic . in step 270 , the user is asked if they want the to track responses to their posting . if the response is “ yes ” in step 270 then the method proceeds to step 275 . in step 275 , a screen is displayed on the user &# 39 ; s computer showing the user &# 39 ; s tracking selections and allowing tracking to be selectively enabled or disabled . this screen is illustrated in fig8 and described infra . next in step 280 , an initial last new responses date is set to the current date or current date and time . in step 285 , upon exiting the screen , the interests ( including forum and topic ) and the initial last new response date is stored in user accounts database 110 ( see fig2 ). in step 290 , the user either returns to a forum , a topic or logs off . note that steps 255 through 290 may be repeated as many times as the user goes to new forum and steps 260 through 290 may be repeated as many times as the user goes to new topics . if the answer is “ no ” in step 270 , the method goes directly to step 290 . fig8 is pictorial representation of an interest selection screen according to the present invention . in fig8 , an interest tracking selections screen 300 includes a multiplicity of text display boxes 305 . each text display box 305 includes a first portion 310 for displaying a forum name and a second portion 315 for displaying a topic name for the forum listed in first portion 310 of each text display box 305 . in one example , the forum and topic names are generated by web user interface elements 115 of shell database 100 ( see fig2 ) and a cross - reference to the actual forum file id and topic file id stored in user accounts database 110 ( see fig2 ). in a second example , the forum name , topic name or both the forum name and topic name are entered or may be overwritten by the user , though a cross - reference to the actual forum file id and topic file id are in user accounts database 110 ( see fig2 ). interest tracking selections screen 300 also includes a multiplicity of check boxes 320 and buttons 325 . when a check box 320 is checked , then tracking emails for the corresponding interest is enabled . alternatively , check boxes 320 would be replaced by buttons that open the interests and email check boxes would be displayed on individual interest screens . in the present example of fig8 , the user has selected only 17 of a maximum of 20 interests and of these 17 only 15 are enabled for actual response tracking ( interests 9 and 10 are inactive ). an option is to assign a “ soft ” maximum of 10 interests and then allow an increase to a “ hard ” maximum of 20 interests when a user requests an eleventh interest to be tracked . check boxes 320 allow for temporary stopping of tracking emails for a topic . button 325 allows selection of an interest 305 to be removed when the user no longer wishes to track an interest and permanently wants it removed or if a user has reached the maximum number of interests and wants to replace an older interest with a new interest . interest tracking selections screen 300 includes a return button 330 and an exit button 335 for navigating the website . generally , the method described herein with respect to a method for tracking responses to a forum topic is practiced with a general - purpose computer and the method may be coded as a set of instructions on removable or hard media for use by the general - purpose computer . fig9 is a schematic block diagram of a general - purpose computer for practicing the present invention . in fig9 , computer system 400 has at least one microprocessor or central processing unit ( cpu ) 405 . cpu 405 is interconnected via a system bus 410 to a random access memory ( ram ) 415 , a read - only memory ( rom ) 420 , an input / output ( i / o ) adapter 425 for a connecting a removable data and / or program storage device 430 and a mass data and / or program storage device 435 , a user interface adapter 440 for connecting a keyboard 445 and a mouse 450 , a port adapter 455 for connecting a data port 460 and a display adapter 465 for connecting a display device 470 . rom 420 contains the basic operating system for computer system 400 . the operating system may alternatively reside in ram 415 or elsewhere as is known in the art . examples of removable data and / or program storage device 430 include magnetic media such as floppy drives and tape drives and optical media such as cd rom drives . examples of mass data and / or program storage device 435 include hard disk drives and non - volatile memory such as flash memory . in addition to keyboard 445 and mouse 450 , other user input devices such as trackballs , writing tablets , pressure pads , microphones , light pens and position - sensing screen displays may be connected to user interface 440 . examples of display devices include cathode - ray tubes ( crt ) and liquid crystal displays ( lcd ). a computer program with an appropriate application interface may be created by one of skill in the art and stored on the system or a data and / or program storage device to simplify the practicing of this invention . in operation , information for or the computer program created to run the present invention is loaded on the appropriate removable data and / or program storage device 430 , fed through data port 460 or typed in using keyboard 445 . in one example , the present invention is implemented in lotus notes ™. in lotus notes ™, shell database 100 ( see fig2 ) is the file profile . nsf , user accounts database 110 ( see fig2 ) is the file names . nsf in which agent 120 ( see fig2 ) resides and where the tracking view is stored . in lotus notes , interests and tracking options are stored in the file my . notes . net and tracking emails received from myldd @ notes . net . in lotus notes ™ a topic is accessed through its doc unid and a forum through a parent unid . an example of a lotus notes ™ website is the lotus developer domain web site and an example of a forum within the website is the notes / domino 6 forum . the description of the embodiments of the present invention is given above for the understanding of the present invention . it will be understood that the invention is not limited to the particular embodiments described herein , but is capable of various modifications , rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention . therefore , it is intended that the following claims cover all such modifications and changes as fall within the true spirit and scope of the invention .