text: referring to fig1 a , there is shown a simplified block diagram of the system of the present invention . a server site 101 is connected to the computer network 103 such as the web or a wide area network ( wan ) other than the web . at the server site , server software runs on a suitable server platform . in the case of the web , for example , the server of fig1 a might be a server available from the national center for supercomputing applications ( ncsa ), or a secure server package of a known , commercially - available type , running on a super - minicomputer such as a sunserver machine available from sun microsystems of menlo park , calif ., or on any of a wide variety of suitable unix platforms . also running , either on the same machine or a network - accessible machine , is a database management system 107 . preferably , the database management system 107 supports standard query language , or sql . one suitable database management system is minisql , which is also commercially available . sql databases , however , are not inherently “ web - friendly .” accordingly , a variety of html front - ending tools 109 are provided which run as extensions to the server software , allowing computer network users to each add entries to a database , search entries in the database , and update entries by that particular user , all using the web ( or a web - like ) graphical user interface . the server software and the html front - ending tools communicate through the common gateway interface 111 . in accordance with another embodiment , shown in fig1 b , the html front - ending tools may be fully integrated with the server software . the html front - ending tools and the database communicate through sql ( 113 ). when a network user visits the server site , the user is served a main page in a page description language such as html . the user interacts with the page , making selections or requests . these selections or requests , although they may not appears as such to the user , are in effect page requests , e . g ., urls that access a page directly or that call a cgi script to perform some sort of processing . the result of the selection or request may be a page eliciting a further selection or request , or may be contain the desired information itself . in order to convey the manner in which the automated information service and directory is used , screen displays of the graphical user interface will now be described . when a user first visits the site , he or she is presented with a main page as shown in fig2 a . along the side of the page are icons that may be clicked on to select different services . an icon 201 selects a “ webbook ” service in which database entries may be searched , viewed and updated . an icon 203 selects a “ webwho whois ” service , providing a graphical front end to the united states whois database , with additional hypertext link integration . an icon 205 selects the “ webwho traceroute ” service , providing a graphical front end to the traceroute utility , again with additional hypertext link integration . an icon 207 in the top left shows the current page &# 39 ; s icon and is not linked . when the icon 201 is selected , the user is presented with a page like that shown in fig2 b , 2c , and 2 d . at the top of the page appears a table 209 presenting examples of valid entry types for whois , i . e ., domain name , machine name , registered handle , registered name , ip address and ip network . next appears a text input field 211 to receive the information to be looked up . next appears an example of the results of a specific lookup . the user has input his or her request , and results have been received back and displayed in a results area 213 . as described more fully below , links are embedded in the results such that , by clicking on an area 215 displaying ccoley @ srmc . com , for example , an e - mail utility will be invoked showing a blank e - mail addressed to ccoley @ srmc . com . similarly , domain names , ip addresses , etc . may be clicked on , with the result that whois is queried once again with respect to the selected information . at the bottom of the page appears a navigational aid 217 used throughout the user interface where appropriate to allow the user to return directly to a particular entry point in the program flow without having to follow numerous links as is typical of the prior art . when the icon 203 is selected , the user is presented with a page for the traceroute utility like that shown in fig2 e and 2f . the various features of the page will be evident from the preceding description . one feature , however , bears particular mention . that is , just as clicking a domain name or the like in whois produces a further query , bringing up additional information , similarly , clicking on names or addresses in fig2 c also produces a further query , not of traceroute but of whois . for example , if one wanted to find additional information about the machine on line number of 1 of fig2 c , one could simply click on the ip address 205 . 138 . 192 . 1 displayed in the area 219 . this action would produce the same result as if the user had copied down the ip address , navigated to whois and entered the ip address in the lookup field . when the icon 205 is selected , the user is presented with a page like that shown in fig2 g . the navigation aid previously described , although not shown in fig2 g , may also be included if desired . the user is given the options of searching the database , adding a new entry , updating an existing entry , changing the user &# 39 ; s password , or logging in . as described below , login is typically not required to view a listing of entries satisfying a particular search request , although login may be required to view an actual entry itself and is required to update an entry . when the search option is selected , the user is presented with a page like that shown in fig2 h . within webbook , a different type of navigational aid 221 is included that allows the user to quickly move about within webbook , between search , add and update , or to go to the main page of fig2 a . the screen of fig2 h allows the user to select between different searching methods , including searching by categories ( going through a categories list ), by example ( querying each field of the entries ), and by keyword ( specifying a keyword ). when categories is selected , the user is presented with a page like that shown in fig2 . in the example shown , three root - level categories are presented , business , recreation , and webwho95 . the user selects one of these categories to show further subcategories , as seen in fig2 , which is displayed in response to the user selecting webwho95 . a single subcategory is shown — index , having 9250 entries . the entries are listed by title within the lower part of the page . the user may select how many entries are to be displayed at a time in order to quicken response time . also , presorts are used in order to quickly display the results of a category or keyword search . when example is selected , the user is presented with a page like that shown in fig2 k . the user enters the information to be searched in any field or combination of fields to be searched . to add a new entry to the database , the user is presented with a page like that shown in fig2 l . each information item in the upper portion of the form is required , unless otherwise indicated . if a required item is not provided , the program will redisplay the form and request the user to complete all required items . optional items include middle name , alternate phone number , fax number , url # 1 , and url # 2 . the remainder of the form is used to enter up to twenty keywords and a description of the user &# 39 ; s entry , to be displayed with the entry . following entry of keywords and a description of the entry , the user is requested to choose a category for the entry by presenting the user with a page like that shown in fig2 m . the user can navigate the category tree until he or she has located the desired category and then select that category . if none of the categories is adequate , then the user may define his or her own category , by entering the name of the category and a short description of the category . the new category will then be added to the category tree . a sample mini homepage is shown in fig2 n and 2o . the mini homepage may be located by searching the database and then selecting the corresponding entry , or may be retrieved directly by url . the url of the mini homepage itself should not be confused with url # 1 and url # 2 listed on the mini homepage . the latter refer to independent resources . the url of the mini homepage itself is , for example , based on a unique transaction id assigned to each entry and may be entered into a browser program to view the mini homepage directly without searching . when update is selected ( fig2 g ), the user , having entered the correct transaction id and password , is presented with a page like that shown in fig2 p . the corresponding mini homepage is displayed , and the user is requested to update the mini homepage ( the “ post ”). when the user has edited the entry to his or her satisfaction , the user presses update . the user is then presented with a further page like that shown in fig2 q and 2r , giving him or her the opportunity to review one final time the comments and keywords . to change the comments or keywords , the user presses back . the user can also change the category of the entry by pressing the change category button . to accept and complete the update , the user presses a done update button . a page like that shown in fig2 s is then presented . the user is required to enter the identification number of the post . if the identification number is entered correctly , the post is updated , and a page like that shown in fig2 t is presented to the user , confirming the update . referring now to fig3 , the operational steps involved in the present system and method are represented . the system is accessed either directly by the user or by following a link to the server site , for example the url webwho . com . the name webwho .™ is a trademark of the present assignee . the user is first presented with a page 301 ( index . shtml ) allowing the user to select from different services , including whois and traceroute . as described previously , whois is an internet service that looks up information about a user in a database . traceroute is a program that permits a user to find the path a packet will take as it crosses the internet to a specific destination . whois and traceroute are known services . previously , however , use of these services has typically required “ root - user access ” on a unix host . in accordance with one aspect of the present invention , these services are html front - ended and made available to all users , together with further hyperlink services that greatly increase the utility of the underlying whois and traceroute services . referring to fig5 , whois and traceroute are made readily available to all network users through html front - ending using cgi scripts . the actual whois code 501 and traceroute code 503 remains within the root directory 500 on a unix host . respective cgi scripts are provided , namely whois . cgi ( 505 ) and traceroute . cgi ( 507 ), that have root user privileges and that provide html front - ending between the user and their respective services . for example , when a user selects the webwho whois service from the main page of fig2 a , the whois . cgi script 505 is invoked to pass the user input to the root directory whois service 501 and cause it to service the user &# 39 ; s request . output from the root directory whois service 501 is passed back from the whois . cgi script 505 in html format . the same description applies equally to the traceroute . cgi script and the root directory traceroute service . to further augment the whois and traceroute services , hyperlink services are provided . the root directory whois and traceroute services are provided with a parsing routine 509 that parses the output of these services to identify e - mail addresses , domain names , ip names , etc .— character strings containing period separators and / or the character “@.” the parser then passes back this information to the cgi scripts in the form of links , links to the whois . cgi script 505 in the case of names and links to an e - mail . cgi script 511 in the case of e - mail addresses . the e - mail . cgi script 511 controls an e - mail utility 513 that may be located in the root directory or in a different directory . whois and traceroute , as implemented as part of the present invention , provide powerful new tools for serious internet tools . using whois , the user may type in any address with a “. com ”, “. edu ” or “. net ” extension and find the physical address , phone number and the individual ( s ) that the address represents . this ability may be used as a powerful marketing tool to find a wealth of information about people on the internet . also , whois can be used to instantly check a domain name . traceroute may be used by system administers to obtain information to make their jobs much easier . previously , system administrators have not been allowed to use traceroute on a pc running any operating system other than unix . whereas whois and traceroute are more technically oriented , “ webbook ” allows non - technical users to take advantage of the capabilities of the web with a minimum of effort . webbook allows a user to have html - front - ended access to a database of mini homepages in order to search , add entries to , or update previous entries in the database . referring again to fig3 , if webbook is chosen , a login routine 303 may request the to enter identifying information of the type that would normally be found on a business card , for example . presently , although web sites are able to track the user &# 39 ; s access point to the web ( for example , a particular slip connection through an internet service provider ), this information often gives no indication who the user really is . such information is important in order to evaluate the extent to which a target audience is being reached . the user may choose an option that allows the user to bypass the login request . the request for information as to the identity of the user therefore may or may not be complied with ; moreover , the information provided may or may not be accurate . as an incentive to provide the requested information ( and , it is hoped , the correct information ), users providing the requested information may be given more complete access to the database than users who do not provide the requested information . users providing the requested information are assigned a user id to be used during subsequent accesses and are requested to choose a password . the password may be required to access some system services . to further encourage voluntary login , users that have complied with the login request and have been assigned a user id may be afforded the ability to customize the user interface and maintain the resulting look and feel between uses . this customization is performed in a known manner by storing on the host a user preferences file and accessing the file to restore user preferences when a valid user id is provided . for a period during the initial stages of the service , while the database is still being built up , it may be desirable to allow all users complete access to the database regardless of whether or not they have identified themselves . following the login procedure , the user is provided with a page 305 presenting the different ways that the user may interact with the database . for example , a user may search the database , add a new entry to the database , or update a previous entry to the database by that user . each of these options will be described in turn . if the user chooses to search the database , the user is provided with a page 307 concerning different search options . a search may be performed on one or more of a number of different database fields , depending on the organization of the database entries . for example , in a preferred embodiment , the database entries include the following defined fields : uid country fname email lname url mname keywords title comment ident category phone 1 active phone 2 start . sub .-- date fax expire . sub .-- date addr info1 ( reserved ) city info2 ( reserved ) state info3 ( reserved ) zipcode info4 ( reserved ) in one embodiment , searches may be performed by category , by keyword , by url , or by example . to facilitate rapid retrieval of information , presorted listings may be stored for each category and keyword or for some number of the most common categories and keywords . to search by example , the user is provided with a form having the same organization as the database entries . the user fills in information in the fields of interest . the search then returns information concerning entries having matching information in those fields . entries are displayed in list fashion by title on a page 309 . the number of entries produced by a search may be very large . therefore , instead of displaying a listing for all of the entries at once , the entries may be displayed ten at a time , for example . alternatively , only the first 100 or 200 entries may be displayed . while some sites may provide information and services free of charge , for example as a result of volunteerism or advertising subsidies , other sites may have a business model in which users are charged for information or services or both . for such a site , it becomes critical to protect the information stored in the database . therefore , unlike some existing databases in which actual hypermedia links to web homepages are stored in the listed items , in order to prevent effectual pirating of the database , links are embedded only in the full entry itself , not in the entry listings . otherwise a user could simply store a voluminous listing or various different listings , with their accompanying hypermedia links , and thereby capture in large part the entire benefit of the database . instead , an item in a listing is intended only to give the user enough information to gauge the user &# 39 ; s further interest in an item . if the user is interested in an item , the user may select that item , causing the full - page entry to be provided . the full page entry includes links to any e - mail address or url that the owner of the entry may have provided , thereby providing a link to that person &# 39 ; s or organization &# 39 ; s homepage ( or to some other homepage ). if the user bypassed login , as determined in step 311 , he or she will normally be returned to the login procedure when attempting to select an entry to view it in its entirety . if the user has logged in , then the user may select an entry and the corresponding full page 313 will be served to the user . the full page entry 313 need not be limited to text alone but may be a complete hypermedia page , including possible graphics or other non - textual content . in this manner , for person &# 39 ; s or organizations not having any independent web homepage , the entry can function as a “ mini - homepage ,” i . e ., a single page hypermedia document . furthermore , the mini - homepage may have its own url , allowing it to be accessed directly without performing a search of the database . for example , a url for a mini homepage might be http :// webwho . com / view ? id = xxxx , where xxxx represents a transaction id assigned to each entry in a manner described below . a link 315 is embedded in the mini - homepage to allow for the page to be updated . prior to describing the manner in which the mini - homepage is updated , however , the manner of adding a new entry to the database will first be described . in order to add an entry to the database , a user must login , during which the user chooses a password , or must have logged in during a previous visit to the site . when the user chooses to add a new entry to the database , a unique transaction id is created for that entry , to be used throughout the life of the entry . a unique transaction id may be created in any of many different ways . for example , the transaction id might be the date ( e . g ., 951215 ) and the entry number for that date ( e . g ., 00215 ). alternatively , the transaction id might be the time of day ( e . g ., hhmmss ) and the process id of the host machine process that is servicing the user &# 39 ; s request . in one embodiment , the transaction id is a 14 - digit hexadecimal number in which eight digits represent the number of seconds since an arbitrary date ( e . g ., jan . 1 , 1970 ), four digits represent the process id running on the host machine , and two digits represent a portion of the machine ip address ( to distinguish between different host machines ). once a transaction id has been assigned , the user is then provided with an entry form 317 having fields corresponding to the various fields of a database entry as described previously . the user fills out the form and presses a screen button when the entry is complete . the form may have one or more checkboxes 319 to indicate the desire to include with the entry one or more non - textual elements , such as a graphic image , etc . also , if desired , different templates may be provided governing the appearance of the finished page , with the user selecting a desired template . non - textual content may be obtained from the user in any of a number of different ways . for example , the user may transfer to the site a file containing the non - textual content using the file transfer protocol ( fip ) with the same user id and password as when the entry was added . during the entry process , the user is prompted to enter keywords to facilitate later searching of the database and location of the entry . furthermore , the html front - end tools may assist in developing keywords for the entry . a pre - searchtsort tool , for example , might take the 2000 top keywords found in the database within the keyword field and do a total text search throughout the database for these keywords . if one or more of these keywords appears in the description (“ comment ” field ) of an entry but not in the keyword list , these keywords are then added to a keyword extension field for up to some number of keywords , e . g . five . if the server site is based on a pay - for - service model , the form will also call for the user to enter a credit card number as the last piece of information . secure , on - line credit card processing will then be performed to bill the user , either on a onetime basis , on a periodic basis , or on an occasional basis as future services may require . although various methods of processing credit card transaction on - line have been proposed , with various degrees of attendant security , such processing is preferably performed in accordance with a proprietary method developed by the assignee to provide the highest level of security possible . after an entry has been made , it may be updated at any time by one able to provide the transaction id assigned to the entry and the user password , i . e ., by the user or one acting on behalf of the user . the update option may be entered directly , or the entry to be updated may first be viewed as the result of a search and the update screen button 315 then pressed . the user is then prompted to supply the correct transaction id and password ( page 321 ), failing which the user will not be allowed to update the entry . if the transaction id and password are correctly supplied , then the equivalent of a new entry form will be provided to the user will the current information pertaining to the entry already filled in . the user may then modify the entry . if a charge is made for updating the entry , preferably the credit card information from the earlier creation of the entry will have been stored in a highly secure fashion , avoiding the need to reenter the information . both security and convenience are thereby enhanced . nothing in the process of adding , searching and updating entries requires manual intervention . rather , the entire process is automated and may be made available continuously , 24 hours a day , 365 days a year . like a publicly - accessible bulletin board , the content that is posted on the database is entirely within the control of the user , both at the time the entry is posted and all times thereafter . referring now to fig4 , various ones of the html front - ending tools of fig1 and their functional interrelationships will now be described . when a user visits the site and the webwho option is selected , a page webwho . html ( 401 ) is served to the user , offering the user various options , including , for example , options to search the database , add a new entry , update an existing entry , change the user &# 39 ; s password , or to log in if the user has not previously done so . in an exemplary embodiment , the routines illustrated in fig4 are standard c routines , called from a single cgi script . in other embodiments , the routines may be called by separate scripts , and may be written other languages such as in a unix shell language , or in one of a number of emerging internet computer languages such as java . the options routine 403 reads in the user &# 39 ; s choice and invokes one of the five following routines : search ( 405 ), add ( 407 ), update ( 409 ), changepw ( 411 ), and login ( 413 ). each of these options will be described in turn . if search is chosen , the search routine 405 initiates one of several possible search functions . in a preferred embodiment , these functions include a categories search , an example search , and a keyword search . according to the search function chosen , the search routine invokes one of the following routines : categories ( 415 ), example ( 417 ), and key . sub .-- search ( 419 ). categories are represented in computer memory in the form of a tree structure . a categories search starts from the root level , with the categories routine 415 displaying all the categories available at that level , and all the entries ( or up to some number of entries ) belonging to that level . the user can click on any category to go to the next level , and can click on any entry to bring up the mini page of the entry . if example is chosen , the example routine 417 displays a form for the user to fill in any field he or she wants to search on . the example routine 417 reads in the information and displays all the entries that match what has been specified . if keyword is chosen , the key . sub .-- ysearch routine 419 displays text boxes to read in up to a specified number of keywords ( e . g ., four ) to search on . the key . sub .-- search routine 419 displays all the entries that match the specified keywords . when a user clicks on one of the entries returned by a search function , the mini page is displayed by a list . sub .-- entries routine 421 . list . sub .-- entries displays the mini page for a particular entry and also contains an update button for the user to update that particular entry . when a user specifies that he or she wants to edit the entry currently being displayed , the update routine 409 performs a check to see if that page belongs to the user currently logged in . if so , updating is initiated by invoking an update post routine 423 . otherwise , an update . sub .-- login routine 425 is called to allow the user to perform the correct login sequence . the update . sub .-- login routine 425 reads in a user id and password and matches them against the database to determine if the user is the owner of the mini page currently being displayed . updating is not allowed until the correct user id and password are entered . the update - post routine 423 displays an entry form with values filled in from the information stored in the database . it invokes a do . sub .-- update routine 427 to process the new values being entered . the do . sub .-- update routine reads in the new information , makes sure that all the required information is filled . if not , a routine do . sub .-- missing is invoked . when all of the required information has been supplied , a update . sub .-- key routine 429 reads in the keywords and comments from the database entry , displays them , and asks the user to confirm . the user can go ahead and update the database or can change the category the entry currently belongs to . if the user chooses to change the category , a change . sub .-- cat routine 431 displays all the categories at the root level . the user can click on one of the categories to go to the next level or can specify a new category on the current level . if the user chooses to go ahead and update the database , another form is displayed to read in the identification number of the entry . a get . sub .-- ident routine 435 is then invoked . if the user chooses to change the category , an update . sub .-- cat routine 433 handles navigation through the categories tree . it will keep displaying the categories on the current level until the user has decided on a category or has specified a new category . the routine get . sub .-- ident 435 reads in the identification number and matches it against the identification number stored in the database for the current entry . if they match , the database is updated ; otherwise , the program declines the update . entries may also be updated directly without searching , using the update routine 409 . if a user is currently logged in , the update routine 409 displays all the entries belonging to that user . otherwise , the update . sub .-- login routine 425 performs a login and displays all the entries belonging to the newly logged - in user . the remaining update routines have already been described as a continuation of the search options and will therefore not be further described . when add is selected , the add routine 407 displays an empty form to allow the user to fill in all the information . the add routine 407 processes the information that has been entered , using the do . sub .-- missing routine to make sure that all the required information is entered . the do . sub .-- missing routine displays the form again until all the required information is entered . after all the required information has been entered , a get . sub .-- info routine 437 displays another form to read in the keywords and comments . a confirm . sub .-- info routine 439 processes the keywords and comment being entered and displays them again , asking the user to confirm . after the user confirms the keywords and comments , a pick . sub .-- cat routine 441 acquires the category using the same mechanism previously described in relation to update . sub .-- cat . if the user is not logged , in he or she is logged in , and a new user id is determined . a form is then displayed to read in the user &# 39 ; s password . a get . sub .-- pw routine 443 reads in the password and displays a form to read in credit card information . a get . sub .-- cc routine 445 verifies the credit card information . if the transaction is authorized , it adds the new entry into the database ; otherwise , it rejects the entry . the remaining routines are administrative in nature . the user may wish to change his or her password . if the user is not currently logged in , a login is performed by calling a changepw . sub .-- login routine 447 . changepw . sub .-- login reads in the user id and password and matches them against the values in the database . a form is then displayed to read in the new password . the changepw routine 411 actually updates the database with the new password . the login routine 413 reads in the user id and password and checks them against the database . if the user id and password are correct , operation begins at the main page with the user logged in as the new user . it will be appreciated by those of ordinary skill in the art that the invention can be embodied in other specific forms without departing from the spirit or essential character thereof . the foregoing description is therefore considered in all respects to be illustrative and not restrictive . the scope of the invention is indicated by the appended claims , and all changes which come within the meaning and range of equivalents thereof are intended to be embraced therein .