CLIENT-SERVER MULTITASKING

Abstract: A client-server multitasking system (10) and process capable of information and/or service retrieval from the same and/or different ones of servers (18) substantially simultaneously and on-the-fly, using the same and/or different ones of queries of the same and/or different ones of the servers (18), and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly, and communicating service and/or information responses to the requestors (12) and/or users (16) substantially simultaneously and on-the-fly. The client-server multitasking system (10) and process are capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks, and are capable of searching search engines and/or other sites substantially simultaneously and on-the-fly. The client-server multitasking system (10) and process are capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the requestors (12), and/or users, and/or instructions resident within the client-server multitasking system (10) and/or process. The client-server multitasking system (10) and process are capable of use in a variety of applications, and capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system (10) and process are capable of building a client-server multitasking system search engine and/or database therefrom responses returned from the servers (18), search engines, and/or sites being queried and/or searched, and/or having requests (29) made thereof, is capable of being searched and/or queried, querying sites referenced therein the client-server multitasking system search engine and/or database, and updating information and/or services stored therein.

Description: Client-Server Multitasking by HARVEY LUNENFELD TABLE OF CONTENTS Table of Contents 1 Background of the Invention 3 Field of the Invention 3 Background Art 3 Summary 3 Drawings 9 Description 15 I. System 15 A. Overview 15 E. Optional Database 17 F. Additional Details 18 II. A Particular User, User Interface, and Client on the Network 20 A. Overview 20 B. Diagrammatic Regrouping 22 III. A Particular Service and/or Information Request and Associated Service and or Information Response on the Network 23 B. The Server PS (18) 23 C. Certain Ones of the Clients 27 D. Formulating Query Information Groups 32 IV Process 39 V. Additional Details 46 A. User Input 46 B. User Interface Details 47 C. Service and/or Information Request Details 48 D. Optional Instructions 49 E. Communicating the Service and/or Information Requests 49 F. Parsing, Processing, and/or Formatting the Service and/or Information Requests 50 G. Formulating the Requests 51 H. Determining Queries and Servers to Make the Requests Thereof 54 I. Grouping the Queries and Sorting/Grouping Criteria 56 J. Communicating the Requests to the Servers 61 K. Replies from the Servers 63 L. Parsing, Processing, Formatting, Sorting, Grouping, and Organizing Responses into Service and/or Infonnation Responses 66 M. Typical Service and/or Information Entry Request Forms, Typical Completed Service and/or Information Entry Request Forms, and Typical Service and or Information Response Forms 71 N. Additional Features and/or Other Considerations 84 Claims 94 Abstract 97 Client-Server Multitasking by HARVEY LUNENFELD BACKGROUND OF THE INVENTION FIELD OF THE INVENTION The present invention relates generally to clients and servers and more particularly to client-server multitasking. BACKGROUND ART Clients, servers, and client-server systems have been known. However there is a need for client-server multitasking. A client-server multitasking system and process are needed, which are capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly. SUMMARY The present invention is directed to a client-server multitasking system and process capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries of the same and/or different ones of the servers, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly, and communicating service and/or information responses to the requestors and/or users substantially simultaneously and on-the-fly. The client-server multitasking system and process is capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks, and be capable of searching search engines and/or other sites substantially simultaneously and on-the-fly. The client-server multitasking system and process is capable of retrieving substantially multiple simultaneous services and/or information having the same and/or different criteria from the same and/or different servers, sorting, grouping, and/or organizing the responses from the servers and/or the clients into information and/or services responses, and communicating the service and/or information responses to the requestors and or the users substantially simultaneously. The requestors and/or the users may make substantially simultaneous service and/or information requests of servers and clients, using the same and/or different queries, and/or the same and/or different instructions. The same and/or different uniform resource locators, target resources, and/or paths may be used. The client-server multitasking system and process is capable of making multiple substantially simultaneous same and/or different requests of same and/or different servers, organizing responses from the servers into service and/or infonnation responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously. The client-server multitasking system and process is also capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the requestors and/or the users, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system is capable of use in a variety of applications, and is capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system and process is also be capable of building a client-server multitasking system search engine and or database therefrom responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof, be capable of being searched and/or queried, querying sites referenced therein the client-server multitasking system search engine and or database, and updating information and/or services stored therein. The client-server multitasking system and process are capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly. A requestor and or user is capable of making substantially multiple simultaneous same and/or different requests of same and/or different servers. The client server-multitasking system and process is capable of organizing responses from the servers into service and/or information responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously, and on-the-fly. The requestors and/or users are capable of making substantially simultaneous service and/or information requests of the same and/or different ones of servers and/or clients, using the same and/or different queries, and/or the same and/or different instructions. The client-server multitasking system and process is capable of retrieving substantially multiple simultaneous services and/or information having the same and/or different criteria from the same and/or different servers, sorting, grouping, and/or organizing the responses from the servers and/or the clients into information and/or services responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously. The same and/or different ones of uniform resource locators, target resources, and/or paths may be used. The requestors and/or users are capable of making multiple simultaneous searches. The searches may have at least one or a plurality of same or different queries of the same and/or different servers and/or clients. The responses from the servers and/or the clients may be of being organized into the service and/or information response in a variety of formats. The responses may be sorted within the service and/or information response, such as, for example, by category, query, group, page, order of importance, ascending and/or descending order, alphabetically and/or numerically, or other characteristics, as determined by the requestor, and/or the user, and/or the client-server multitasking system, and/or the responses may be combined within the service and/or information response, such as, for example, interleaving the responses one with the other, such as, for example, by order of relevance or other parameters. The responses may also be capable of being grouped by search criteria, server, order of importance, or by numerical factors such as value, price, or other numerical quantifier. For example, the responses may be presentable, for example, in ascending or descending order in interleaved format, such as top ones, twos, threes, and so on, or presentable separately to the requestor and/or the user. The order may be order of importance or relevance related, or, for example, numerically valued, such as price or stock market value. The client-server multitasking system and process is capable of information and/or service retrieval from the same and/or different ones of the servers substantially simultaneously and on-the-fly, using the same and/or different ones of the queries, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly. The client-server multitasking system and process is capable of substantially multiple simultaneous searching, using the same and/or different ones of queries of the same and/or different ones of the clients and/or servers, which may be search engines, and/or sites, and/or servers, and/or locations on the network, and additionally and/or alternatively building a client-server multitasking search engine and/or database. The client-server multitasking search engine and/or database is capable of storing the information and/or services retrieved therefrom the search engines, and/or sites, and/or servers, and/or locations being queried on the network therein, and building the client-server search engine and/or database. The client-server multitasking search engine should is also capable of being queried either directly and/or in combination therewith the substantially simultaneous searching, using the same and/or different queries of the same and/or different search engines, sites, servers, and/or databases. The client-server multitasking search engine and/or database should is also capable of updating information and/or services stored therein by querying sites, servers, search engines, and/or databases containing information and/or services referenced in client- server multitasking search engine and/or database. The client-server multitasking system and process is also capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks. The client-server multitasking system and process are capable of substantially simultaneous searching of the same and/or different ones of search engines and/or sites on the network substantially on-the-fly, with the same and/or different ones of the queries, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly. The client-server multitasking system and process are also capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the requestors, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system and process are also capable drilling down and/or up to different levels within the search engines, sites, and/or servers being queried. The client-server multitasking system and process are capable of providing manual and/or timed updates. Such timed updates allow for motion related presentation to the requestor and/or the user. The client-server multitasking system and process are capable of incorporating information and/or services thereinto a variety of user interfaces at different locations therein the user interfaces, grβuping, and/or organizing the - - * »■ ' information and/or services, and optionally eliminating duplicate information and/or services. The client-server multitasking system and process are capable of incorporating links, graphics, video, text, and audio, and/or combinations thereof, and selective advertising, according to selectable search, query, sorting, and/or grouping criteria, and/or combinations thereof thereinto the information and/or services to be delivered thereto the user interfaces. The requestor and/or the user may place orders, such as purchases, and/or other types of orders, payments, confirmations thereof, and/or combinations thereof, either directly and/or therethrough servers and/or sites thereon the network. The client-server multitasking system is capable of use in a variety of applications, and is capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system is capable of, for example, determining best query results, with respect to a plurality of search engine results; purchasing and/or price comparisons, viewing and/or reviewing prices/values and trends for different sites, determining lowest costs and lowest cost analyses for wholesale and retail purposes; product availability, e.g., airline tickets, pricing, and ticket availability, from different airlines to the same and/or different locations; purchasing of commodities and/or stocks form the same and/or different sites with updates every few seconds and/or minutes; obtaining prices and/or values in different stock markets substantially simultaneously; and searching for jobs on the same and/or different job sites, using the same and/or different job criteria, for example, on a daily basis, the job sites having changing job availability; and/or a combination thereof, all substantially simultaneously. The client-server multitasking system is capable of presenting information and/or services for review and/or updating from the same and/or different ones of sites, servers, and/or applications substantially simultaneously, and trend analysis thereof, using a variety of sorting, grouping and/or organizing criteria, according to the needs of the requestor, and/or the user, and/or resident within the client-server multitasking system. The client server-multitasking system and process are capable of service and/or information retrieval from at least one server, organization, communication, and presentation of such services and or information to at least one requestor and/or user, and/or optional storage, and/or retrieval of such services and/or information from the optional storage. The client-server multitasking system and process are capable of building a client-server multitasking system search engine and/or database therefrom responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof. The client-server multitasking system search engine and/or database having stored information and/or services therein are also searchable, are capable of full text searches thereof, and are searchable by the servers and/or the clients on the network, either separately and/or in combination therewith the substantially simultaneous multiple same and/or different searches and/or queries of the same and/or different servers on the network. Information therein the client-server multitasking system search engine and/or database are also searchable and/or retrievable, and are capable of being incorporated therein the service and/or information responses delivered thereto the user interfaces, according to search criteria, selectively and/or automatically, by the requestor and/or the user. The client-server multitasking system search engine and/or database are capable of spidering, and/or roboting, and/or querying sites, services and/or information to be stored therein and/or stored therein the client-server multitasking system search engine and/or database, and updating the services and/or information to be stored and/or stored therein the client-server multitasking system search engine and/or database. The client-server multitasking system and process are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information therefrom the same and/or different ones of the servers and/or clients having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information thereinto user responses for delivery to and use by the requestors and/or users. The client-server multitasking system and process, then, are capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries of the same and/or different ones of the servers, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly, and communicating service and/or information responses to the requestors and/or users substantially simultaneously and on-the-fly. The client-server multitasking system and process are capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks, and are capable of searching search engines and/or other sites substantially simultaneously and on-the-fly. The client-server multitasking system and process are capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the requestors, and/or users, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system is capable of use in a variety of applications, and capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system and process are capable of building a client- server multitasking system search engine and/or database therefrom responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof, is capable of being searched and/or queried, querying sites referenced therein the client-server multitasking system search engine and/or database, and updating information and/or services stored therein. The client-server multitasking system and process are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information therefrom the same and/or different ones of the servers and/or clients having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information thereinto user responses for delivery to and use by the requestors and/or users. The client-server multitasking system and process are also capable of performing as a multiple query search engine, which performs multiple queries of multiple sites, and of performing as a single point of sale for purchasing multiple products from multiple sources. A multitasking process having features of the present invention comprises: parsing, processing, and/or formatting a service and/or information request thereinto a current request group; opening connections therewith and making at least one request thereof at least one server; parsing, processing, formatting, grouping, and/or organizing at least one response therefrom the at least one server thereinto at least one addressable response information group; formulating information therefrom the current request group thereinto a request pointer/address group having at least one pointer/address; formulating at least one addressable query pointer/address group having at least one other pointer/address; incorporating information and/or services therefrom the at least one addressable response information group thereinto at least one addressable query information group; and incorporating the at least one addressable query information group thereinto a service and/or information response. A client-server multitasking system having features of the present invention comprises: means for parsing, processing, and/or formatting a service and/or information request thereinto a current request group; means for opening connections therewith and making at least one request thereof at least one server; means for parsing, processing, formatting, grouping, and/or organizing at least one response therefrom the at least one server thereinto at least one addressable response infonnation group; means for formulating information therefrom the current request group thereinto a request pointer/address group having at least one pointer/address; means for formulating at least one addressable query pointer/address group having at least one other pointer/address; means for incorporating information and/or services therefrom the at least one addressable response information group thereinto at least one addressable query information group; and means for incorporating the at least one addressable query infonnation group thereinto a service and/or infonnation response. DRAWINGS These and other features, aspects, and advantages of the present invention will become better understood with regard to the following description, appended claims, and accompanying drawings where: FIG. 1 is a schematic representation of a client-server multitasking system, constructed in accordance with the present invention; FIG. 2 is a more detailed schematic representation of the client-server multitasking system; FIG. 3 is a schematic representation of user input Ul n from user U n thereinto user interface l n of the client-server multitasking system; FIG. 4 is a schematic representation of a server S z of the client-server multitasking system; FIG. 5 A is a schematic representation of a server PS of the client-server multitasking system having an optional database; FIG. 5B is a schematic representation of a client C n of the client-server multitasking system having an optional database; FIG. 6 is a schematic representation of a particular one of the clients Cι...C n of the client-server multitasking system, designated as the particular client C n , communicating with ones of the servers SvS z , in accordance with the designation scheme corresponding to the corresponding ones of the server designations S n ,...S nm , corresponding to the requests Q n1 ...Q nm , therethrough the server PS; FIG. 7 is a schematic representation of the particular client C n of the client-server multitasking system communicating with ones of the servers Sι...S z , in accordance with the designation scheme corresponding to the corresponding ones of the server designations S n1 ...S nm , corresponding to the requests Qni...Q nm ; FIG. 8 is a schematic representation of the particular client C n of the client-server multitasking system communicating with ones of the servers Sι...S z , in accordance with the designation scheme corresponding to the corresponding ones of the server designations S n ι...S nm , corresponding to the requests Q n1 ...Q nm , and also therethrough the server PS; FIG. 9 is an alternate schematic representation of the client-server multitasking system of FIG.1, constructed in accordance with the present invention, regrouped diagrammatically and alternatively named for illustrative purposes only, to illustrate and visualize possible typical communication paths; FIG. 10 is a schematic representation of a particular service and/or information request lQ n ; FIG. 11 is a schematic representation of a particular service and/or information request lQ n parsed, processed, and/or formatted into a current request group QA nc , request groups QA n1 ...QA nz , and corresponding optional instructions VJ n1 ...VJ nk , and utilization of information therefrom to make the requests Q n ι...Qnm ; obtain the responses R n1 ...R nm , and incorporate information therefrom into a particular service and/or information response IR n ; FIG. 12 is a schematic representation of the particular service and/or information request lQ n parsed, processed, and/or formatted into a current request group QA nc , request groups QA n1 ...QA nz , and corresponding optional instructions VJ n , ... VJ nk , and utilization of information therefrom to make the requests Q n1 ...Q nm , obtain the responses R n ι...R πm , and incorporate information therefrom into the particular service and/or information response IR n , having other grouping/sorting that may be used additionally and/or alternatively to that of FIG. 11; FIG. 13 is a schematic representation of the particular service and/or information response IR n having a service and/or infonnation group G n , additional request links SL n1 ...SL nw , optional order form, optional additional advertisements and/or links, optional hidden information, and the optional service and/or information entry request form; FIG. 14 is a schematic representation of a particular user service and/or information request iq n ; FIG. 15 is a schematic representation of a particular user service and/or information request iq n parsed, processed, and or fonnatted into the current request group QA nc , the request groups QA n1 ...QA nz , and the corresponding optional instructions VJ n , • • -VJ n ι < , and utilization of information therefrom to make the requests Q n ι...Q nm , obtain the responses R n ι...R nm , and incorporate information therefrom into the particular user service and/or information response ir n ; FIG. 16 is a schematic representation of the particular user service and/or information request iq n parsed, processed, and/or formatted into the current request group QA nc , the request groups QA n ι...QA nz , and the corresponding optional instructions VJ n ι ...VJ nk , and utilization of information therefrom to make the requests Q n ι...Q nm , obtain the responses R n ,...R n m > and incorporate information therefrom into the particular user service and/or infonnation response ir n , having other grouping/sorting that may be used additionally and/or alternatively to that of FIG. 15; FIG. 17 is a schematic representation of the particular user service and/or information response ir n having the service and/or information group G n , the additional request links SL n1 ...SL nw , the optional order form, the optional additional advertisements and/or links, the optional hidden information, and the optional service and/or information entry request form; FIG. 18A is a schematic representation of a response information group RG nm having addressable individual information groups LG nm ι- " LG nmr showing optional addressable pointer/address indices IN nm1 ...IN nmr correspondingly associated therewith optional addressable individual information groups LG nm1 ...LG nmr , which may be addressed/pointed therewith pointer/address PPnmi; FIG. 18B is a schematic representation of the addressable response information group RG nm having the addressable individual information groups LG nm ι...LG n r showing the optional addressable pointer/address indices IN nm ι ...IN nmr correspondingly associated therewith the optional addressable individual information groups LG nm , ...LG nmr , which may be addressed/pointed therewith the pointer/address PPnm∑; FIG. 18C is a schematic representation of the addressable response information group RG nm having the addressable individual information groups LG nm ι...LG nmr showing the optional addressable pointer/address indices IN nm ι...lN nmr correspondingly associated therewith the optional addressable individual information groups LG n mi-- -LGnmr, which may be addressed/pointed therewith the pointer/address PP n mr; FIG. 19 is a schematic representation of the individual information groups LG nm i " -LGnmr having corresponding optional links LD nm1 ...LD nm r ; and/or corresponding optional descriptions DD nm1 ...DD nmr , and/or corresponding optional prices/values PD n mi---PDnmr s and/or corresponding optional images ID nm i---ID nmr ; FIG. 20 is a schematic representation of a labelled individual information group LL nmr ; FIG. 21 is a schematic representation of an addressable query information group Gl nz ; FIG. 22 is a schematic representation of steps of a client-server multitasking process of the present invention; FIG. 22-lA is a schematic representation of a multitasking process of deriving the service and/or information response IR n and/or the user service and/or information response ir n , with reference to FIGS. 11 and 15; FIG. 22-lB is a schematic representation of a multitasking process of deriving the service and/or information response IR n and/or the user service and/or information response ir n having other grouping/sorting that may be used additionally and/or alternatively to that of FIGS. 11 and 15, as shown with reference to FIGS. 12 and 16; FIG. 22-1-1 is a schematic representation of a step of the multitasking process of FIGS. 22-lA and 22-lB shown in more detail; FIG. 22-1-2A is a schematic representation of another step of the multitasking process of FIG. 22-lA shown in more detail; FIG. 22-1-2B is a schematic representation of another step of the multitasking process of FIG. 22-lB shown in more detail; FIG. 22-2 is a schematic representation of user review of user response UR n and/or selection of additional services and/or information; FIG. 23 is a schematic representation showing queries QQ n1 ...QQ nm and corresponding server addresses FIG. 24 is a schematic representation of queries QQ n1 ...QQ nm , corresponding server addresses AQ n ι...AQ nm , and optional instructions VJ nm i...VJ nk that may be parsed, processed, and/or formatted from the service and or information request lQ n and/or the user service and/or information request iq n , shows a schematic representation of a typical one of the optional service and/or information entry request fonn IE n , and is schematically representational of a typical user interface l n , FIG. 25 is a schematic representation of certain typical optional instructions VJ π mi---VJ nk and/or certain additional request links SL n1 ...SL nw ; FIG. 26 is a schematic representation of other certain typical optional instructions VJ nm i---VJ nk and/or other certain additional request links SL n1 ...SL nw ; FIG. 27 depicts certain typical additional request links SL n1 ...SL nw ; FIG. 28 is a schematic representation of a request pointer/address group QZ ns , having a particular one of query pointer/address groups QG n ι---QG nz , designated as the query pointer/address group QG nz , associated ones of the addressable response information group s RG n ι -..RG nm , the pointers/addresses PP n 11 ■ ■ - P n mn and the query information group Gl nz associated therewith the query pointer/address group QG nz ; FIG. 29 is a schematic representation of a sorting criteria addressing scheme having a particular query pointer/address group QG nz , associated ones of response information groups RG nm , and query information group Gl nz associated therewith the query pointer/address group QG nz ; FIG. 30 is a schematic representation of an alternate sorting criteria addressing scheme having a particular query pointer/address group QG nz , associated ones of response information groups RG nm , and query information group Gl nz associated therewith the query pointer/address group QG nz ; FIG. 31 is a schematic representation of typical ones of the query pointer/address groups QG n1 ...QG nz , having the sorting criteria addressing scheme of FIG. 29, having typical ones of queries QQ n1 ... QQ nz and corresponding server addresses AQ n1 ...AQ nz associated therewith; FIG. 32 is another schematic representation of the typical ones of the query pointer/address groups QG n ι-..QG nz , having the sorting criteria addressing scheme of FIG. 29, having the typical ones of the of queries QQ n1 ...QQ nz and the corresponding ones of the server addresses AQ n1 ...AQ nz of FIG. 31 associated therewith; FIG. 33 is a generic schematic representation of the query pointer/address groups QG n ...QG nz , having the sorting criteria addressing scheme of FIG. 29, having the ones of queries QQ n ---QQ nz and the corresponding ones of the server addresses AQ n1 ...AQ nz associated therewith; FIG. 34 is a schematic representation of a request Q nm of the client-server multitasking system; FIG. 35 is a schematic representation of a response R nm of the client-server multitasking system; FIG. 36 is a schematic representation of an entity body RH nm of the response R nm of FIG. 35 having optional response individual information groups LS nrn ι...LS nm r, and or optional information Ll nm ; FIG. 37 is a schematic representation of the addressable response information group RG nm having the addressable individual information groups LG nm ι...LG n mr parsed, and/or processed, and/or formatted, and/or organized, and/or grouped thereinto the addressable response information group RG nm therefrom the optional entity body RH nm of FIG. 36; FIG. 38 is a schematic representation of the optional response individual information group LS nm r parsed, and/or processed, and/or formatted, and/or organized, and/or grouped thereinto the addressable individual information group LG nmr ; FIG. 39 is a schematic representation of the optional links LD nm ι...LD nmr , and/or the optional descriptions DD πm1 ...DD nmr , and/or the optional prices/values PD nm ι...PD nmr , and/or the optional images ID nm i...lD n mr parsed individually and/or separately, and incorporated thereinto the addressable response information group RG nm therefrom the optional entity body RH nm ; FIGS. 40 is a schematic representation of a typical one of the addressable query information group Gl nz , based upon certain sorting and/or grouping criteria, having the labelled individual information groups LLnzi.-.LLnzu, the optional database labelled individual information groups RL nz ι...RL nzx , the optional query description QT nz , the optional server descriptions and/or links ST πz ι...ST nZf , and the optional advertisements and/or links LT nz ι ... LT πzt incorporated thereinto certain typical ones of the typical service and/or information response forms IS n ; and FIGS. 41 is a another schematic representation of a typical one of the addressable query information group Gl nz , based upon certain sorting and/or grouping criteria, having the labelled individual information groups LL nz1 ...LL nzu , the optional database labelled individual information groups RL nz i...RL nzx , the optional query description QT nz , the optional server descriptions and or links ST nz ...ST nZf , and the optional advertisements and/or links LT nz ι...LT nzt incorporated thereinto certain typical ones of the typical service and/or information response forms IS n ; FIG. 42 depicts a typical service and/or information entry request form lE n at the user interface l n , which the user U π may communicate typical user input Ul n thereinto; FIG. 43 depicts a typical completed service and/or information entry request form IF n at the user interface l n ; FIG. 44 depicts a typical user response UR n , as a typical service and/or information response form IS n at the user interface l n , which may be communicated thereto the user U n ; FIG. 45 depicts another typical user response UR n , as the typical service and/or information response form lS n at the user interface l n , which may be communicated thereto the user U n ; FIG. 46 depicts another typical user response UR n , as the typical service and/or infonnation response form IS n at the user interface l n , which may be communicated thereto the user U n ; FIG. 47 depicts another typical completed service and/or information entry request form IF n at the user interface l n ; FIG. 48 depicts another typical user response UR n , as the typical service and/or information response form lS n at the user interface l n , which may be communicated thereto the user U n ; FIG. 49 depicts another typical user response UR n , as the typical service and/or information response form lS n at the user interface l n , which may be communicated thereto the user U n ; FIG. 50 depicts another typical user response UR n , as the typical service and/or information response form lS n at the user interface l n , which may be communicated thereto the user U n ; FIG. 51 depicts another typical completed service and/or information entry request fonn IF n at the user interface i n ; FIG. 52 depicts another typical user response UR n , as the typical service and/or information response form lS n at the user interface l n , which may be communicated thereto the user U n ; FIG. 53 depicts another typical completed service and/or information entry request form IF n at the user interface l„; FIG. 54 depicts another typical user response UR n , as the typical service and/or information response form IS n at the user interface l n , which may be communicated thereto the user U n ; FIG. 55 depicts another typical completed service and/or information entry request form IF n at the user interface l n ; FIG. 56 depicts another typical user response UR n , as the typical service and/or information response form IS n at the user interface l n , which may be communicated thereto the user U n ; FIG. 57 depicts another typical completed service and/or information entry request form IF n at the user interface i n ; FIG. 58 depicts another typical user response UR n , as the typical service and or information response form lS n at the user interface l n , which may be communicated thereto the user U n ; . FIG. 59 depicts another typical completed service and/or information entry request form IF n at the user interface i n ; FIG. 60 depicts a typical combined user response UR n , as the typical service and/or information response form IS n at the user interface l n , which may be communicated thereto the user U n , and an order entry form OF n , which the user U n may enter an order therewith; FIG. 61 depicts a typical preview form of an order OP n , resulting from submission of the order entry form OF n , of the typical combined user response UR n , as the typical service and or information response form IS n at the user interface l n , which may be communicated thereto the user U n , and the order entry form OF n , which the user U n may enter the order therewith, of FIG. 54; FIG. 62 depicts a typical order placement form OL n , having the typical preview form of the order OP n , resulting from submission of the order entry form OF n , of the typical combined user response UR n , as the typical service and/or information response form lS n at the user interface l n , which may be communicated thereto the user U n , and the order entry form OF n , which the user U n may enter the order therewith, of FIG. 54, or which the user U n may enter therethrough the typical preview form of the order OP n of FIG. 61; FIG. 63 depicts a typical order confirmation OC n , resulting from submission of the typical completed order placement form OL n of FIG,. 62; FIG. 64 depicts another typical service and/or information entry request form IE n at the user interface l n , which the user U n may communicate other typical user input Ul n thereinto; FIG. 65 depicts another typical service and/or information entry request form IE n at the user interface l n , which the user U n may communicate other typical user input Ul n thereinto; FIG. 66 depicts another typical completed service and/or infonnation entry request form IF n at the user interface i n ; FIG. 67 depicts another typical user response UR n , as the typical service and/or information response form IS n at the user interface l n , which may be communicated thereto the user U n ; FIG. 68 depicts another typical service and/or information entry request form IE n at the user interface l n , which the user U n may communicate other typical user input Ul n thereinto; FIG. 69 depicts another typical user response UR n , as the typical service and/or information response form lS n at the user interface l n , which may be communicated thereto the user U n ; and FIG. 70 depicts another typical service and/or information entry request form lE n at the user interface l π , which the user U n may communicate other typical user input Ul n thereinto. DESCRIPTION The preferred embodiments of the present invention will be described with reference to FIGS. 1-70 of the drawings. Identical elements in the various figures are identified with the same reference alphanumerics. I. SYSTEM A. OVERVIEW FIGS. 1 and 2 show a client-server multitasking system 10 of the present invention, having requestors Uι...U n (12), hereinafter called users U ...U n (12), corresponding user interfaces I-i l π (14), corresponding clients C|...Cn (16), server PS (18), servers S^.-Sz (20), and optional servers SOι...SO p (22), constructed in accordance with the present invention, which reside on a network 24. Each of the users U<ι...U n (12) communicate with the corresponding clients C|...Cn (16) therethrough the corresponding user interfaces l ,...l n (14). Each of the users U 1 ...U n (12) enter corresponding user inputs UI,...UI n (25) having one or more same and/or different user requests qu 11 ...qu nu (26) thereinto the corresponding user interfaces lι...l n (14), as shown in FIG. 3. The user requests qUn.-. Unu (26) are communicated from the user interfaces lι...l n (14) to the corresponding clients Cι...C n (16) within corresponding user service and/or information requests iq^. qn (27), having the user requests qu 11 ...qu nu (26) and other optional information. The users U<|...U n (12) may enter the corresponding user inputs UI ...UI n (25) at the same and/or different times. Each of the user interfaces l ,...l n (14) communicate the user service and/or information requests iq 1 ...iq n (27) thereto the corresponding clients Cι...C n (16), which optionally format the corresponding user service and/or information requests iq 1 ...iq n (27) into corresponding service and/or information requests IQι...lQ n (28), as required. Each of the service and or information requests IQi ...lQ n (28) have infonnation therein that may be used to formulate one or more same and/or different requests Q1 1 ...Q nm (29) to be made of one or more of the same and/or different ones of the servers S 1 ...S Z (20), which may hereinafter be called server designations Sn...S nm (30), in accordance with a designation scheme which designates the servers Sι-..S Z (20) to be communicated with corresponding to the requests Qn.-.Qnm (29) as the corresponding server designations Sn.-.Snm (30), as shown in FIGS. 2 and 4. FIG. 4 shows the server designations Sn.-.Sn (30) for typical ones of the requests Qιι...Q nm (29) and a typical one of the servers S z (20). Each of the requests Q- H ...Q nm (29) may be the same and/or different one from the other and may be made of the same and/or different ones of the servers S.|...S Z (20) at the same time and/or different times. Each of the service and/or infonnation requests IQi ...IQ n (28) may be communicated thereto the server PS (18), which parses, processes, and/or formats the service and/or information requests IQ 1 ...IQ n (28) into the requests Qn.-.Qnm (29). The corresponding clients Cι...C n (16) may also and/or alternatively optionally parse, process, and/or format the corresponding user service and/or infonnation requests iq-i ...iq n (27) into one or more of the same and/or different requests Q 11 ...Q nm (29) to be made of one or more of the same and/or different ones of the servers S<|...S Z (20), in accordance with the designation scheme corresponding to the corresponding ones of the server designations Sι-|...Snm (30), as required. Certain ones of the clients Ci...C n (16) may communicate corresponding certain ones of the service and/or information requests IQ 1 ...IQ n (28) to the server PS (18), which parses, processes and/or formats the certain ones of the service and/or information requests IQ 1 ...IQ n (28) into certain ones of the requests Qιι...Q nm (29), as required, and communicates the certain ones of the requests Q 11 ...Q nm (29) to the servers S<|...S Z (20), in accordance with the designation scheme corresponding to the corresponding certain ones of the server designations S 11 ...S nm (30). Alternate ones of the clients C^-.Cn (16) may communicate corresponding alternate ones of the requests Qιι...Q nm (29) to corresponding alternate ones of the servers S< t ...S z (20), in accordance with the designation scheme corresponding to the corresponding alternate ones of the server designations Sιι...S nm (30). Other alternate ones of the clients C^.-C n (16) may communicate corresponding other alternate ones of the service and/or information requests IQ 1 ...IQ n (28) to the server PS (18), which parses, processes and/or fonnats the other alternate ones of the service and/or information requests lQ ...IQ n (28) into other alternate ones of the requests Qιι...Q nm (29), as required, communicates the other alternate ones of the requests Qιι...Q n (29) to corresponding other alternate ones of the servers S<|...S Z (20), in accordance with the designation scheme corresponding to the corresponding other alternate ones of the server designations S,ι...S nm (30); and additionally the other alternate ones of the clients C 1 ...C n (16) may also parse, process, and/or format the user service and/or information requests iq 1 ...iq π (27) into one or more of the same and/or different yet other alternate ones of the requests Qn...Q nm (29), and communicate the yet other alternate ones of the requests Qιι. " Qnm (29) to corresponding yet other alternate ones of the servers S-|...S Z (20), in accordance with the designation scheme corresponding to the corresponding yet other alternate ones of the server designations Sιι.„„S nrrι (30). Each of the service and/or infonnation requests IQι...IQ n (28) may, thus, be communicated therefrom the corresponding clients C^-.C,, (16) to the server PS (18). The requests Q 1 ...Q nm (29) may be communicated therefrom the server PS (18) and/or therefrom the corresponding clients C^.-Cn (16) to the servers S<|...S Z (20), and may depend upon instructions from and/or generated by the corresponding users U . - ■ U n (12), and/or the corresponding user interfaces lι...l n (14) and or the corresponding clients C|...C n (16), and/or information generated by the server PS (18) and/or the servers Si ...S z (20), and/or ancillary instructions, a combination thereof, and/or other suitable means. Each of the servers S-|...S Z (20) corresponding to the designation scheme S^.-Snm (30) replies to the server PS (18) and/or the clients Cι...C n (16), accordingly, and communicates corresponding responses RivRnm (32), associated with the requests Qn.-.Qnm (29), to the server PS (18) and/or the clients C^.-Cn (16) making the requests Q 1 ι...Q n m (29), as shown in FIG. 2 for typical ones of the requests Qι-|...Q n m (29) and the corresponding responses Rn...R nm (32). The server PS (18) and or the appropriate clients C|...C n (16) parse, process, format, sort, group, and/or organize the responses Rn...R nm (32) into corresponding service and/or information responses IR 1 ...IR n (34), having corresponding parsed, processed, formatted, sorted, grouped, and/or organized service and/or information groups G^.-G n (35) acceptable to the corresponding clients Cι...C n (16) and the corresponding respective user interfaces lι---l n (14). The server PS (18) communicates the appropriate service and/or information responses IRι...IR n (34) to the corresponding clients Cι...C n (16). The clients C.|...C n (16) format the service and/or information responses IRι...IR n (34) into corresponding user service and/or information responses irι...ir n (36), as required, and communicate the user service and/or information responses irι...ir n (36) thereto the corresponding user interfaces l ,...l n (14). The user interfaces l<,...l n (14) incorporate the user service and/or information responses i η ... i r n (36) into corresponding user responses UR^.-URn (37), which are derived at the user interfaces l ,...l n (14), and communicated by the user interfaces l<,...l n (14) thereto the corresponding users Uι...U n (12). The users U.j...U n (12) review the corresponding user responses URι...UR n (37) at the user interfaces lι...l n (14) and/or select additional services and/or information therefrom. E. OPTIONAL DATABASE The server PS (18) and/or the clients C^.-Cn (16) may also incorporate corresponding additional optional responses RAιι...RA n m (40) into the service and/or information responses IR^. Rn (34), which may be obtained by accessing optional databases 41 and/or 42, shown in FIGS. 5A and 5B, which may be optionally resident within the server PS (18) and/or the clients C(...Cn (16), respectively. The server PS (18) and/or the clients C]...C n (16) may optionally store the responses R.]i...R nrn (32) communicated therefrom the servers S<|...S Z (20), in accordance with the designation scheme corresponding to the server designations Si 1 ...S nm (30) in the optional databases 41 and/or 42, optionally resident within the server PS (18) and/or the clients Cι...C n (16), respectively, which may be optionally retrieved from the optional databases 41 and/or 42, and/or optionally incorporated into the service and/or information responses IRι...IR n (34), and accessed as the additional optional responses RAιι. " A nm (40). The server PS (18) and/or the clients C.]...C n (16) may optionally communicate with the optional servers SOι...SO p (22), and obtain information from each of the optional servers S0 ...SO p (22), which may also be stored in the optional databases 41 and/or 42, which may be optionally resident within the server PS (18) and/or the clients Cι...C n (16), respectively, and which may be optionally incorporated into the service and/or information responses IRι...IR n (34), and accessed as the additional optional responses RAn.-.RAnm (40). Each of the users U^.-Un (12) may optionally communicate corresponding additional optional requests qπ...q n (44) therethrough the corresponding user interfaces l-j I n (14) and the corresponding clients Cι...C n (16) to the optional servers SO.) ...SO p (22), based upon information in the service and/or information responses lRι ...IR n (34) and/or other information presented to and/or available and/or known to the users Ui ... U n (12) therethrough the corresponding user interfaces lι...l n (14). The optional servers SO-|...SO p (22) reply to the clients Cι...C n (16) with corresponding responses rιι...r np (46), which the clients Cι...C n (16) communicate therethrough the corresponding user interfaces I-i I n (14) to the corresponding users U^.-U n (12), as shown in FIG. 2 for typical ones of the requests qii-..q np (44) and the corresponding responses rii...r np (46). F. ADDITIONAL DETAILS Now, in more detail, the clients C 1 ...C n (16) and the servers Si ...S z (20) reside on the network 24. The users U- ...U n (12) and the corresponding clients Ci ...C n (16) communicate one with the other therethrough the corresponding user interfaces l-ι...l n (14). The user Ui (12), thus, communicates with the client Ci (16), one with the other, therethrough the user interface h (14); the user U 2 (12), thus, communicates with the client C 2 (16), one with the other, therethrough the user interface l 2 (14); the user U n (12), thus, communicates with the client C n (16), one with the other, therethrough the user interface l n (14); and so on. Any particular user, designated user U n (12), thus, communicates with corresponding client C n (16), one with the other, through corresponding user interface l n (14), as best shown later in FIGS. 6-8. The user U n (12) may be used to designate any one of the users U^.-U n (12); the user interface l n (14) may be used to designate any one of the user interfaces lι...l n (14); the client C n (16) may be used to designate any one of the users clients Cι...C π (16); and so on. The client-server multitasking system 10 may also have the server PS (18) and the optional servers SOι ...SO p (22) residing on the network 24. There may be n different or same the service and/or information requests IQ 1 ...IQ n (28) present on the network 24 at any time. Each of the service and/or information requests IQi ...lQ n (28) may have one or more of the same and or different requests Qι- t ...Q n '(29) to be made of one or more of the same and/or different ones of the servers S-|...S Z (20), which are called server designations Sn...S nm (30), in accordance with the designation scheme which designates the servers S.|...S Z (20) to be communicated with corresponding to the requests Qιι...Q nm (29) as the corresponding server designations Sιι...S nm (30). The service and/or information request IQ n (28) may be used to designate any particular one of the service and/or information requests IQ^.JQπ (28). Requests Q n ι...Q n m (29) may be used to designate the particular requests Qn ...Q πm (29) associated therewith and corresponding to the service and/or information request IQ n (28). Each of the requests Q ...Q 1m from the client Ci (16) may each be different one from the other or the same; each of the requests Q 2 ι...Q 2 m from the client C 2 (16) may each be different one from the other or the same; and each of the requests Q n ι ...Q nm (29) from the client C n (16) may each be different one from the other or the same, and so on. The requests Qn ...Q 1m (29), the requests Q 21 ...Q 2m (29), and the requests Q n ι ...Q nm (29), thus, may each be different one from the other, or the same, and so on. The requests Qn...Q nm (29) from the clients C-|...C n (14), thus, may each be different, one from the other, or the same, and may be made of the same and/or different ones of the servers S>|...S Z (20) at the same time and/or different times, in accordance with the corresponding server designations Sii...S nm (30). There may be m different or same ones of the requests Q n ι...Q n m (29) from the client C n (16) at any time, and n x m different and/or same ones of the requests Qιι...Q nm (29) of the same and/or different ones of the servers S<|...S Z (20) present on the network 24 at any time. This designation format, in which the first alphanumeric subscript after the parameter of interest, for example, as in the parameters Q n ι...Q nm representing the requests Q n ι...Q n m (29), represents the particular parameters corresponding to the user U n (12), and the second alphanumeric subscript after the parameter of interest represents the 1 st , 2 nd , 3 rd , through the mth one of the particular parameters, will be used as a designation scheme throughout. In this particular instance, for example, there are then m distinctly the same and/or different ones of the requests Q n i...Qnm (29) associated with the nth user U n , which is designated as the user U n (12). There are then the same and or different m distinctly the same and/or different server designations S n ...S nm (30) associated with the nth user U π , which is designated as the user U n (12). The same and/or different requests Q n ι...Q n m (29), then, may be made of the same and/or different ones of the servers S>|...S Z (20), in accordance with the designation scheme corresponding to the corresponding certain ones of the server designations S n ι...S nm (30), associated with and corresponding to the user U n (12). Each of the clients Cι...C n (16) may optionally also function as servers. Certain ones of the clients Cι„.C n (16) may, therefore, function only as clients, while alternate ones of the clients Cι...C n (16) may function as clients and as servers. Each of the user interfaces lι...l n (14) may be integral with the clients (16) or separate from the clients Cι...C n (16). Therefore, certain ones of the user interfaces lι...l n (14) may be integral with the clients C- t ...C n (16), while yet other ones of the user interfaces lι...l n (14) may be separate from the clients C^.-Cn (16). The client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, the server PS (18) and/or the clients C 1 ...C n (16) are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information therefrom the same and/or different ones of the servers S.]...S Z (20), and/or the optional servers SO.,...SO p (22), and/or the clients Cι...C n (16), having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information thereinto the user responses UR 1 ...UR n (37) for delivery to the user interfaces l ...l n (14) and use by the users U^.-Un (12). Now, the user interfaces lι...l n (14) may each be different, one from the other, or the same, and may change characteristics over time. Each of the user interfaces lι...l n (14) may change characteristics as a function of time, information, and/or instructions, and/or other means, which may be derived by the users Ui-..U n (12) and/or the clients C|...Cn (16) and/or the servers S<|...S Z (20), and/or the server PS (18), and/or the optional servers SOι-..SO p (22), and/or derived within the user interfaces lι...l n (14). The user interface I-i l n (14) may change state. The user interface lι...l n (14) may also change as a function of optional timers and/or timed instructions associated therewith the user interfaces ...I n (14), and or associated therewith the clients C| ...C n (16) and/or associated therewith the servers S 1 ...S Z (20), and/or associated therewith the server PS (18), and/or associated therewith the optional servers SO^-.SO p (22), and or instructions from the user U^.-Un (12). Changes in the user interface l n (14) may appear continuous to the user U n (12), spaced in time, staccato, or static depending upon the optional timers and/or the timed instructions. Other conditions may change the user interface lι...l n (14), as well. The user interfaces l-|...l n (14) may be updated continuously, intermittently, manually, randomly, semi-automatically, automatically, repetitively, non-repetitively, singly, plurally, multiplexed, and/or a combination thereof or other suitable manner. The user interfaces lι-..l n (14) may be visual, such as graphical user interfaces, aural, and/or tactile, a combination thereof, and/or other suitable means. The user interfaces lι...l n (14) may be integral with the clients Cι...C n (16) or separate. II. A PARTICULAR USER, USER INTERFACE, AND CLIENT ON THE NETWORK A. OVERVIEW FIGS. 6-8 show typical particular ones of the users U n (12), the corresponding ones of the user interfaces U n (12), the corresponding ones of the clients C n (16), the server PS (18), the servers Sι-..S Z (20) designated by the server designations S n ι ...S nrn (30) corresponding to the requests Q n ι ...Q nm (29) associated with the corresponding ones of the users U n (12), and the optional servers SO^-.SO p (22) of the client-server multitasking system 10 of the present invention, which reside on the network 24. The user U n (12) communicates with the corresponding client C n (16) therethrough the corresponding user interface l n (14). The user U n (12) enters the corresponding user input Ul n (25) having one or more same and/or different user requests qu n ...qu nu (26) thereinto the user interface l n (14). The user requests qu n ι...qu nu (26) are communicated from the user interface l n (14) to the client C n (16) within the user service and/or information request iq n (27), having the user requests qu n1 ...qu nu (26) and other optional information. The user interface l n (14) communicates the user service and/or information request iq n (27) therethrough to the client C n (16), which optionally formats the corresponding user service and/or information request iq n (27) into the corresponding service and/or information request lQ n (28), as required. The service and/or information request IQ n (28) may have one or more the same and/or different requests Q n ι...Q n m (29) to be made of the servers Sι...S z (20) designated by the server designations S n1 ...S nm (30) at the same time. The client C n (16) may communicate the corresponding service and/or information request IQ n (28) to the server PS (18). The server PS (18) parses, processes and/or formats the service and/or information request IQ n (28) received from the client C n (16) into the certain requests Q n ι...Q nm (29), and communicates the certain requests Qni...Q n (29) to the corresponding certain ones of the servers S<|.--S z (20) designated by the server designations S n ι - ..S nm (30), as shown for typical ones of the certain requests Q„ι ...Q πm (29) in FIG. 6. The client C n (16) may alternatively parse, process and/or format the user service and or information request iq n (27) into the alternate requests Q π1 ...Q nm (29), and communicate the alternate requests Q n ι ...Q nm (29) to the corresponding alternate ones of the servers S^.-Sz (20) designated by the server designations S n1 ...S nm (30), as shown for typical alternate ones of the requests Q n ι...Q n m (29) in FIG. 7. The client C n (16) may alternatively communicate the corresponding other alternate one of the service and/or information request IQ n (28) to the server PS (18), which parses, processes and/or formats the other alternate one of the service and/or information request lQ n (28) into the other alternate ones of the requests Q n1 ...Q n (29), and communicates the other alternate ones of the requests Q n ...Q n (29) to the corresponding other alternate ones of the servers Sιι...S nm (30), and additionally the client C n (16) may also parse, process and/or format the user service and or information request iq n (27) into yet other alternate ones of the requests Q n i...Q nm (29), and communicate the yet other alternate ones of the requests Q n ι ...Q nm (29) to the corresponding yet other alternate ones of the servers S n ι...S nm (30), as shown for typical other alternate ones of the requests Q n1 ...Q πm (29) and typical yet other alternate ones of the requests Q n ι...Q n m (29) in FIG. 8. Each of the servers Sι...S z (20) designated by the server designations S n ι...S nm (30) replies to the server PS (18) and/or the client C n (16), in accordance with the designation scheme corresponding to the corresponding certain ones of the server designations Sn...S nm (30), accordingly, and communicates the con-esponding responses Rni---Rnm (32), associated with the requests Q n ι...Q n m (29), to the server PS (18) and/or the client C n (16), accordingly. The server PS (18) and/or the client C n (16) parse, format, process, group, and organize the responses Rm ■ ■ ■ Rnm (32) into the corresponding service and or information response IR n (34) and/or the user service and or information response ir n (36) having the corresponding parsed, processed, formatted, grouped, and organized service and/or information group G n (35) acceptable to the client C n (16) and the user interface l n (14). The server PS (18) communicates the service and/or information response IR n (34) to the client C n (16), as required. The client C n (16) formats the service and/or information responses IRι...IR n (34) into the corresponding user service and/or information response ir n (36), as required, and communicates the user service and/or information responses ir π (36) thereto the user interfaces l n (14). The user interface l π (14) incorporates the user service and/or information response ir n (36) into the user response UR n (37), which is communicated by the user interfaces l n (14) thereto the user U n (12). The server PS (18) and/or the client C n (16) may optionally also incorporate the optional additional corresponding responses RA n1 ...RA nm (40) (shown later in FIGS. 11, 12, 15, and 16) into the service and/or information response IR n (34), which may be obtained by accessing the optional databases 41 and/or 42, which may be optionally resident within the server PS (18) and/or the client C n (16), respectively The server PS (18) and/or the client C n (16) communicate the service and/or information response IR n (34) therethrough the user interface l n (14) to the user U n (12). The server PS (18) and/or the clients C n (16) may optionally store the responses R n ι ...R nm (32) communicated from the servers Si ...S z (20) designated by the server designations S n ...S nm (30) in the optional databases 41 and/or 42, optionally resident within the server PS (18) and/or the client C n (16), respectively, which may be optionally retrieved from the optional databases 41 and/or 42, and/or optionally incorporated into the service and/or information response IR n (34), and accessed as the additional optional responses RA n ι...RA nm (40). The server PS (18) and/or the client C n (16) may optionally communicate with the optional servers SO<|...SO p (22), and obtain information from each of the optional servers SO-|...SO p (22), which may also be stored in the optional databases 41 and/or 42, which may be optionally resident within the server PS (18) and/or the client C n (16), respectively, and which may be optionally incorporated into the service and or information response lR n (34), and accessed as the additional optional responses RA n ι...RA π m (40). The user U n (12) may optionally communicate the corresponding additional optional requests q n ι..-q n p (44) therethrough the user interface l n (14) and the client C n (16) to the optional servers SO^.-SO p (22), based upon information in the service and/or information response IR n (34) and/or other information presented to and or available and/or known to the user U n (12) therethrough the user interface l n (14). The optional servers SO-|...SO p (22) reply to the client C n (16) with the corresponding responses r„ι ... r n (46), which the client C n (16) communicates therethrough the user interface l„ (14) to the user U n (12), as shown in FIGS. 6-8 for typical ones of the requests q n ι---q n p (44) and the corresponding responses r n ι...r n (46). B. DIAGRAMMATIC REGROUPING Now, in more detail, FIG. 9 shows a schematic representation of ones of the users Uι...U n (12), the corresponding user interfaces lι...l n (14), the corresponding clients C|.--C n (16), the server PS (18), the servers S-|...S Z (20), and the optional servers SO.|...SO p (22) of the client-server multitasking system 10 of the present invention, constructed in accordance with the present invention, which reside on the network 24, regrouped diagrammatically and alternatively named for illustrative purposes only, to illustrate and visualize possible typical communication paths. Other than FIG. 9, the nomenclature previously described and utilized will be used throughout. Now, as shown in FIG. 9, for illustrative purposes only, ones of the clients C.|...C n (16) communicating with the server PS (18), as in FIG. 6, may optionally be designated clients CA-|...CA W (16A), and so on. Ones of the clients C^-.Cn (16) communicating with the servers S^.-S z (20), as in FIG. 7, may optionally be designated clients CB<]...CB χ (16B), and so on. Ones of the clients C^.-Cn (16) commimicating with the server PS (18) and with the servers S-|...S Z (20), as in FIG 8, may optionally be designated clients CC^.-CC y (16C), and so on. The users U^.-Un (12) and the corresponding user interfaces lι...l n (14) corresponding to the clients C|...Cn (16) may, likewise, optionally be designated in FIG. 9 only: correspondingly to the clients CA-|...CA W (16A), as users UA-i...UA w (12A) and user interfaces IAι...lA w (14A), respectively; correspondingly to the clients CBι...CB x (16B), as users UB 1 ...UB X (12B) and user interfaces IBι...lB x (14B), respectively; and correspondingly to the clients CC,...CC y (16C), as users UC^.-UC y (12C) and IC,...IC y (14C), respectively. The clients C|...Cn (16) being accounted for, the total of the clients CA.,...CA W (16A), CB-,...CB X (16B), and CCv-CCy (16C) of FIG. 9 add up to n, where n may be any number greater or equal to one, such that the subscripts w + x + y = n. III. A PARTICULAR SERVICE AND/OR INFORMATION REQUEST AND ASSOCIATED SERVICE AND/OR INFORMATION RESPONSE ON THE NETWORK B. THE SERVER PS (18) FIG. 10 shows a typical particular one of the service and/or information requests lQ<|...IQ n (28), designated as the service and/or information request IQ n (28), having queries QQ n1 ...QQ nm (53), corresponding server addresses AQ n1 ...AQ nm (54), and optional instructions VJ n1 ...VJ nk (52). The server addresses AQ n1 ...AQ nm (54) and the optional instructions VJ n1 ...VJ nk (52) may be optional, and may depend upon the user interface l π (14), and/or other information resident within the server PS (18). FIG. 11 shows the particular service and/or information request lQ n (28) parsed, processed, and/or formatted into current request group QA nc (50), request groups QA n1 ...QA nz (51), and optional instructions VJ n1 ...VJ nk (52), and utilization of information therefrom to make the requests Q n ι...Q n m (29), obtain the responses R n ι...R m (32), and incorporate information therefrom into the particular service and or information response IR π (34). The current request group QA nc (50) may be any particular one the request groups QA n ...QA nz (51 ), which may be selected by the user U n (12). Upon receipt of the service and/or information requests IQ^.TQ n (28) at the server PS (18), communicated therefrom the corresponding clients C|...C n (16), the server PS (18) parses, processes, and/or formats each of the service and/or information requests lQι...IQ n (28) into the corresponding current request groups QA 1c ...QA nc (50) having corresponding queries QQ-n ...QQ n (53) and corresponding server addresses AQn ...AQ nm (54) to open connections with and make the requests Q 1 ι...Q nm (29) thereof the servers S.|...S Z (20), in accordance with the designation scheme which designates the certain ones of the servers S<ι...S z (20) to be communicated with corresponding to the requests Qιι...Q nm (29) as the corresponding server designations Sιι...S nm (30), shown for a particular one of the service and/or information requests IQ n (28) in FIG. 11. The server PS (18) also parses, processes, and/or formats each of the service and/or information requests IQi-..IQ n (28) into the corresponding request groups QAn...QA nz (51) having corresponding other queries QQ 1a ...QQ nz (55) and corresponding other server addresses AQ 1a ...AQ nz (56), and the corresponding optional instructions VJιιι...VJ nk (52), also shown for a particular one of the service and/or information requests IQ n (28) in FIG. 11. The server PS (18) opens connections with and makes the requests Q n ι...Q nm (29) thereof the servers S<ι...S z (20), in accordance with the designation scheme which designates the certain ones of the servers S^...S Z (20) to be communicated with corresponding to the requests Q n ι ...Qnm (29) as the corresponding server designations Sιι...S nm (30), shown for the particular one of the service and/or information requests IQ n (28) corresponding to the corresponding queries QQ n ι--.QQ n m (53) and the corresponding server addresses AQ n1 ...AQ nm (54) therein the current request group QA nc (50). The servers Sι-..S Z (20) corresponding to the server designations Sn.-.Sn (30), designated in accordance with the designation scheme which designates the certain ones of the servers S 1 a ..S z (20) to be communicated with corresponding to the requests Q n ...Q nm (29) as the corresponding server designations Sιι...S nm (30), respond to the requests Q n i...Q nm (29) with the corresponding responses R n ι...R n m (32). The server PS (18) parses, and/or processes, and/or formats, and/or groups, and/or organizes each of the responses Rni---Rnm (32) received from the servers S^.S z (20) corresponding to the server designations S n1 ...S nm (30) into corresponding addressable response information groups RG n ι...RG nm (57). The server PS (18) may also make additional optional requests QP n ι...QP nm (58) of the optional database 41, which may be optionally resident within the server PS (18), and which may reply with the corresponding additional optional responses RA n ι...RA nm (40). The server PS (18) parses, and/or processes, and/or formats, and/or groups, and/or organizes each of the additional optional responses RA n1 ...RA nm (40) into corresponding response information groups RC n1 ...RC nm (59). Information from the current request group QA nc (50) having the corresponding queries QQ n1 ...QQ nm (53) and the corresponding server addresses AQ n ι ... AQ nm (54) is formulated into a corresponding request pointer/address group QZ n (60) having pointers/addresses PG n1 ...PG nz (61) associated therewith. Each of the pointers/addresses PG n ι...PG nz (61) are directed to point address corresponding addressable query pointer/address groups QG n1 ...QG nz (62) associated therewith, which aid in obtaining information and/or services therefrom certain ones of addressable response information groups RG n ι...RG n m (57) to be incorporated thereinto addressable query information groups Gl n ...GI nz (63). Grouping and/or sorting criteria may be incorporated thereinto the optional instructions VJ„ι ...VJ nk (52), which may be entered thereinto the user interface l n (14) therethrough the user input Ul n (25) by the user U n (12). Grouping and/or sorting criteria may additionally and/or alternatively be optionally resident within the server PS (18) and/or the client C n (16). The grouping and/or sorting criteria gives the user U n (12) the ability to formulate the query information groups Gl n ι ...Gl nz (63) and the way in which information and/or services from the addressable response information groups RG n1 ...RG nm (57) is presented to the user U n (12) therethrough the user interface l n (14). Each of the addressable query pointer/address groups QG n ι ...QG nz (62) are associated therewith the corresponding ones of the addressable query information groups Gl n1 ...GI nz (63). The addressable query pointer/address group QG n1 (62) is, thus, associated therewith the addressable query information group Gl n ι (63); the addressable query pointer/address group QG n2 (62) is, thus, associated therewith the addressable query information group Gl n2 (63); the addressable query pointer/address group QG nz (62) is, thus, associated therewith the addressable query information group Gl nz (63), and so on. Each of the addressable query pointer/address groups QG n1 ...QG nz (62) is formulated based upon the grouping and/or sorting criteria, which may be incorporated thereinto the optional instructions VJ n1 ...VJ nk (52), and/or which may additionally and or alternatively optionally be resident within the server PS (18) and/or the client C n (16), and/or information within the current request group QA πc (50). Each of the addressable query pointer/address groups QG n1 ...QG nz (62) has pointers/addresses PP n11 ...PP nm r (64) directed to address/point information therein the addressable response information groups RG n ι...RG nm (57) based upon the grouping and/or sorting criteria, which may be incorporated thereinto the optional instructions VJ n1 ...VJ nk (52), and/or which may additionally and/or alternatively optionally be resident within the server PS (18) and/or the client C n (16), and/or the corresponding queries QQ n1 ...QQ nm (53), and/or the corresponding server addresses AQ n1 ...AQ nm (54) within the current request group QA nc (50). Information and/or services within each of the addressable response information groups RG n ...RG nm (57) is addressed therewith the pointers/addresses PP n n...PPnmr (64) therefrom the query pointer/address groups QG n1 ...QG nz (62), and information and/or services therefrom the addressable response information groups RG n1 .-.RG nm (57) is incorporated thereinto the addressable query information groups Gl n1 ...GI nz (63) corresponding to the pointers/addresses PP n 1 ...PP nmr (64), which are formulated by the addressable query pointer/address groups QG n ...QG nz (62), in accordance with the grouping and/or sorting criteria. The corresponding other queries QQ na ...QQ nz (55) and the corresponding other server addresses AQ na ...AQ nz (56) therein the corresponding request groups QA n1 ...QA nz (51) may be used for other ones of the requests Q n ι...Q n m (29), and may be incorporated into the service and/or information response IR π (34), as part of other information OI n (65), for future use. Each of the addressable query information groups Gl n1 ...GI nz (63) is incorporated thereinto the service and/or information group G n (35). The service and/or information group G n (35) and the other information OI n (65) are incorporated thereinto the service and/or information response IR n (34). The optional instructions VJ n ι...VJ nk (52) may be used by the server PS (18) in making the requests Q n ι...Q nm (29) and/or the additional optional requests QP n ι...QP n m (58) of the optional database 41, and/or in processing, formatting, grouping, and organizing the responses R n ι...R n m (32) from the ones of the servers S.|...S Z (20) corresponding to the server designations S n ι ...S nm (30), and/or the additional optional responses RA n ι ...RA nm (40), into the corresponding service 1 and or information responses IR ! ...IR n (34), for grouping and or sorting criteria instructions, and/or may be used for other purposes. FIG. 12 is a schematic representation of the particular service and/or information request IQ n (28) parsed, processed, and/or formatted into a current request group QA n (50), request groups QA n1 ...QA πz (51), and corresponding optional instructions VJ n ...VJ nk (52), and utilization of mformation therefrom to make the requests Qni...Q nm (29), obtain the responses R n1 ...R nm (32), and incorporate information therefrom into the particular service and or information response IR n (34), having simpler grouping/sorting that may be used additionally and/or alternatively to that of FIG. 11. The user U n (12) is typically given the option therethrough the optional instructions VJ n ...VJ nk (52) as to the grouping and/or sorting criteria to be entered thereinto the user interface l n (14) therethrough the user input Ul n (25) by the user U n (12). The user U n (12) is typically given the choice as to the grouping and/or sorting criteria to be used as in FIG. 11, and/or the grouping and/or sorting criteria of FIG. 12. Information from the current request group QA nc (50) having the corresponding queries QQ n ι...QQ n m (53) and the corresponding server addresses AQ n1 ...AQ nm (54) is formulated into a corresponding request pointer/address group QY n (68) having pointers/addresses PF n ιι...PF nm r (69) associated therewith, as shown in FIG. 12. Each of the pointers/addresses PF n11 ...PF nmr (69) are directed to point/address the corresponding addressable response information groups RG n ι...RG nm (57), and aid in obtaining information and/or services therefrom the corresponding addressable response information groups RGni...RG nm (57) to be incorporated thereinto the addressable query information groups Gl n1 ...GI nz (63), as shown in FIG. 12. The grouping and/or sorting criteria allow the user U n (12) to direct the server PS (18) and/or the client C n (16) to sort information and/or services therefrom the responses the responses R n ι...R nm (32) and/or the additional optional responses RA n ι...RA nm (40) therefrom the optional database 41, such as, for example, by category, query, group, page, order of importance, ascending and/or descending order, alphabetically and/or numerically, value, price, and/or other characteristics, and/or to combine and/or interleave the information and/or services therefrom the responses the responses R n ι...R n m (32) and/or the additional optional responses RA n ι...RA nm (40) one with the other, such as, for example, by order of relevance and/or other parameters. FIG. 13 shows the particular service and/or information response IR n (34) having a service and/or information group G n (35), additional request links SL n ι...SL nw (71), optional order form 72, optional additional advertisements and/or links 73, optional hidden information 74, and the optional service and/or information entry request form IE n (38). The service and/or information group G n (35) has the query information groups Gl n ...GI nz (63), optional database response groups 75, and optional additional advertisements and/or links 76. The additional request links SL n1 ...SL nw (71) allow the user U n (12) to make additional optional selections, based upon information and/or services previously requested by the user U n (12). The additional request links SL n1 ...SL nw (71), which are optional, may typically have Current Group/Next Group/Previous Group/Group Number Links, Server Names in Each Group, Queries in Each Group, Current Page/Next Page/Previous Page/Page Number Links, Search Display/Link and/or Description Placement/Interleave/Separate, and Link Description Options/Summary/Minimize. Other additional ones of the additional requests links SL n1 ...SL nw (71) and/or combinations thereof may also be incorporated thereinto the service and or information response IR n (34). The optional order form 72 allows direct placement and/or confirmation of orders and/or purchases therewith the servers Sι-..S Z (20) and/or the optional servers SOι-..SO p (22), which reside on the network 24. The user U n (12) may enter the order placement thereinto the user interface l n (1 ) therethrough the user input Ul n (25), and receive order confirmation therethrough the user interface l n (14). The client C n (16) may communicate the order placement therefrom the user interface l n (14) thereto the server PS (18), which may communicate the order placement thereto the servers Si ...S z (20) and/or the optional servers SOi ...SO p (22). The server PS (18) may alternatively and/or additionally communicate the order confirmation received therefrom the servers Si ...S z (20) and/or the optional servers SOι...SO p (22) thereto the client C n (16), which may communicate the order confirmation thereto the user interface l n (14) for presentation to the user U n (12). The order placement and/or the order confirmation may be stored within the server PS (18) and/or the client C n (16). The order placement and/or the order confirmation is typically secure, and may be encrypted, and is typically communicated using secure communications means. C. CERTAIN ONES OF THE CLIENTS Certain ones of the clients C|...C n (16) may alternatively and/or additionally make the requests Qιι...Q n m (29) thereof the servers Sι-..S Z (20), in accordance with the designation scheme which designates the certain ones of the servers S>|.--S z (20) to be communicated with corresponding to the requests Qιι ...Q n (29), and formulate the corresponding user service and/or information response ir 1 ...ir n (36), as previously described. FIG. 14 shows a typical particular one of the user service and/or information requests iq 1 ...iq π (27), designated as the user service and/or information request iq n (27), having the queries QQ n1 ...QQ nm (53), the corresponding server addresses AQ n1 ...AQ nm (54), and the optional instructions VJ n ι...VJ nk (52). The server addresses AQni .. -AQnm (54) and the optional instructions VJ„ι .. -VJ nk (52) may be optional, and may depend upon the user interface l n (14), and/or other information resident within the client C n (16). FIG. 15 shows the particular user service and or information request iq n (27) parsed, processed, and/or formatted into the current request group QA nc (50), the request groups QA n1 ...QA nz (51 ), and the corresponding optional instructions VJ n ι-..VJ nk (52), and utilization of information therefrom to make the requests Q n1 ...Q nm (29), obtain the responses R n ι ...R nm (32), and incorporate information therefrom into the particular user service and/or information response ir n (36); The server PS (18) makes the requests Qιι...Q nm (29) thereof the servers S^...S Z (20), in accordance with the designation scheme which designates the certain ones of the servers S.|...S Z (20) to be communicated with corresponding to the requests Qn ^ -O nm (29) as the corresponding server designations Sii...S nm (30), as shown in FIG. 11, and certain ones of the clients Cι...C n (16) may additionally and/or alternatively make the requests Qιι...Qnm (29) thereof the servers S.]...S Z (20), in accordance with the designation scheme which designates the certain ones of the servers S<|...S Z (20) to be communicated with corresponding to the requests Qιι...Q nm (29) as the corresponding server designations Sιι...S nm (30), as shown in FIG. 15. The clients C n (16) may parse, process, and/or format the user service and/or infonnation requests iq n (27) and/or organize and/or group information and/or services therefrom the addressable response information groups RG n ι...RG πm (57) thereinto the addressable query information groups Gl n1 ...GI nz (63) substantially the same as the server PS (18) parses, processes, and/or formats the service and/or information requests lQ n (28) therefrom the addressable response information groups RG n i...RG nm (57) thereinto the addressable query information groups Gl n ...GI nz (63), except that the client C n (16) may organize the addressable query information groups Gl n1 ...GI nz (63) thereinto the user service and/or infonnation response ir n (36), as in FIG. 15, and the server PS (18) organizes the addressable query information groups Gl n1 ...GI nz (63) thereinto the corresponding service and/or information response IR n (34), as in FIG. 11. Upon receipt of the user service and/or information requests iq 1 ...iq n (27) at the corresponding clients C^.-Cn (16), certain ones of the corresponding clients Cι...C n (16) may parse, process, and/or format the corresponding user service and/or information requests iq 1 ...iq n (27) into the corresponding current request groups QA 1c ...QA nc (50) having the corresponding queries QQ 11 ...QQ rιm (53) and the corresponding server addresses AQ^...AQ nm (54) to open connections with and make the requests QivQnm (29) thereof the servers S-|...S Z (20), in accordance with the designation scheme which designates the certain ones of the servers S.|.--S z (20) to be communicated with corresponding to the requests Qn.-.Qnm (29) as the corresponding server designations Sιι...S nm (30), shown for a particular one of the user service and/or information requests iq 1 ...iq n (27) in FIG. 15. The corresponding clients C 1 ...C n (16) may also parse, process, and/or format the corresponding user service and/or information response i r 1 ... i r n (36) into the corresponding request groups QA 11 ...QA nz (51) having the corresponding other queries QQ 1a ...QQ nz (55) and the corresponding other server addresses AQ a ...AQ nz (56), and the corresponding optional instructions VJ-m ...VJ nk (52), also shown for a particular one of the user service and/or information requests iq π (27) in FIG. 15. A particular one of the corresponding clients C]...C n (16), designated as the client C n (16), may open connections with and make the requests Q n ι . - .Qnm (29) thereof the servers Si ...S z (20), in accordance with the designation scheme which designates the certain ones of the servers S-|...S Z (20) to be communicated with corresponding to the requests Q n1 ...Q nm (29) as the corresponding server designations S<|.|...S nm (30), shown for the particular one of the user service and/or information requests iq n (27) corresponding to the corresponding queries QQ n1 ...QQ nm (53) and the corresponding server addresses AQ n1 ...AQ nm (54) therein the current request group QA nc (50). The servers S<|...S Z (20) corresponding to the server designations Sιι...S n m (30), designated in accordance with the designation scheme which designates the certain ones of the servers S^-.S;. (20) to be communicated with corresponding to the requests Q n1 ...Q nm (29) as the corresponding server designations Sn...S nm (30), respond to the requests Q n i...Q nm (29) with the corresponding responses R n ι...R n m (32). The client C n (16) may parse, and/or process, and/or format, and/or group, and/or organize each of the responses R n1 ...R nm (32) received from the servers S^.-S z (20) corresponding to the server designations S n ι...S nm (30) into the corresponding addressable response information groups RG n ι...RG nm (57). The client C n (16) may also make additional optional requests QP π ι...QP nm (58) of the optional database 42, which may be optionally resident within the client C n (16), and which may reply with the corresponding additional optional responses RA n ...RA n m (40). The client C n (16) may parse, and/or process, and/or format, and/or group, and or organize each of the additional optional responses RA n1 ...RA nm (40) into the corresponding response information groups RC n1 ..-RC nm (59). Now again, for the client C π (16), information from the current request group QA πc (50) having the corresponding queries QQ n1 ...QQ nm (53) and the corresponding server addresses AQ n1 ...AQ πm (54) is formulated into the corresponding request pointer/address group QZ n (60) having the pointers/addresses PG n ι...PG nz (61) associated therewith. Now again, for the client C n (16), each of the pointers/addresses PG n ι...PG nz (61) are directed to point/address the corresponding addressable query pointer/address groups QG n1 ...QG nz (62) associated therewith, which aid in obtaining information and/or services therefrom certain ones of the addressable response information groups RGni-.-RGnm (57) to be incorporated thereinto the addressable query information groups Gl n1 ...GI nz (63). Yet again, for the client C n (16), grouping and/or sorting criteria may be incorporated thereinto the optional instructions VJ π1 ...VJ nk (52), which may be entered thereinto the user interface l n (14) therethrough the user input Ul n (25) by the user U n (12). Grouping and/or sorting criteria may additionally and/or alternatively optionally resident within the server PS (18) and/or the client C n (16). Now again, the grouping and/or sorting criteria gives the user U n (12) the ability to formulate the query information groups Gl n ...Gl nz (63) and the way in which information from the addressable response information groups RG n ι...RG nm (57) is presented to the user U n (12) therethrough the user interface l n (14). Now again, for the client C n (16), each ofthe addressable query pointer/address groups QG n1 ...QG nz (62) are associated therewith the corresponding ones ofthe addressable query information groups Gl n ι...Gl nz (63). Each of the addressable query pointer/address groups QG n1 ...QG nz (62) is formulated based upon the grouping and/or sorting criteria, which may be incorporated thereinto the optional instructions VJ n1 ...VJ nk (52), and/or which may additionally and/or alternatively optionally be resident within the server PS (18) and/or the client C n (16), and/or information within the current request group QA nc (50). Now again, for the client C n (16), each ofthe addressable query pointer/address groups QG π1 ...QG nz (62) has pointers/addresses PP n11 ...PP nm r (64) directed to address/point services and/or information therein the addressable response information groups RG n ι...RG nm (57) based upon the grouping and/or sorting criteria, which may be incorporated thereinto the optional instructions VJ n1 ...VJ nk (52), and/or which may additionally and/or alternatively optionally be resident within the server PS (18) and/or the client C n (16), and/or the corresponding queries QQn -.-QQnm (53), and/or the corresponding server addresses AQ n1 ...AQ nm (54) within the current request group QA nc (50). Yet again, for the client C n (16), the information and/or services therein each ofthe addressable response information groups RG n ι...RG nm (57) is addressed therewith the pointers/addresses PP n ii...PP nm r (64) therefrom the query pointer/address groups QG n1 ...QG nz (62), and information and/or services therefrom the addressable response information groups RG n ι...RG nm (57) is incorporated thereinto the addressable query information groups Gl n1 ...GI nz (63) corresponding to the pointers/addresses PP n ιι...PP nm r (64), which are formulated by the addressable query pointer/address groups QG n ι ...QG nz (62), in accordance with the grouping and/or sorting criteria. Yet again, for the client C n (16), the corresponding other queries QQ na ...QQ nz (55) and the corresponding other server addresses AQ na ...AQ nz (56) therein the corresponding request groups QA n1 ...QA nz (51) may be used for other ones ofthe requests Q n ι...Q n m (29), and may be incorporated into the user service and/or information response ir n (36), as part of other information OI n (65), for future use. Now again, for the client C n (16), each ofthe addressable query information groups Gl n1 ...GI nz (63) is incorporated thereinto the service and/or information group G n (35). The service and/or information group G n (35) and the other information OI n (65) are incorporated thereinto the service and/or information response IR n (34). The optional instructions VJ n ...VJ nk (52) may be used by the client C n (16), in making the requests Q n ι...Q nm (29) and/or the additional optional requests QP n i...QP nm (58) ofthe optional database 42, and/or in processing, formatting, grouping, and organizing the responses R n ι...R n m (32) from the ones ofthe servers S<ι...S z (20) corresponding to the server designations S n ι ...S nm (30), and/or the additional optional responses RA n ι ...RA nm (40), into user service and/or information response ir n (36), for grouping and or sorting criteria instructions, and/or may be used for other purposes. FIG. 16 is a schematic representation ofthe particular user service and/or information request iq n (27) parsed, processed, and/or formatted into the current request group QA nc (50), the request groups QA n1 ...QA nz (51), and the corresponding optional instructions VJ n ι.-.VJ nk (52), and utilization of information therefrom to make the requests Q n ...Q nm (29), obtain the responses R n ι...R n m (32), and incorporate information therefrom into the particular user service and or infonnation response ir n (36), having simpler grouping/sorting that may be used additionally and/or alternatively to that of FIG. 15. The user U n (1 ) is typically given the option therethrough the optional instructions VJ n ι-..VJ nk (52) as to the grouping and/or sorting criteria to be entered thereinto the user interface l n (14) therethrough the user input Ul n (25) by the user U n (12). The user U n (12) is typically given the choice as to the grouping and/or sorting criteria of FIG. 15, and/or the grouping and or sorting criteria of FIG. 16. Now again, the client C n (16) may parse, process, and/or format the user service and/or information requests iq n (27) and/or organize and/or group information and/or services therefrom the addressable response information groups RG n1 ...RG nm (57) thereinto the addressable query information groups Gl n1 ...GI nz (63) substantially the same as the server PS (18) parses, processes, and or formats the service and/or information requests lQ n (28) therefrom the addressable response information groups RG n i...RG nm (57) thereinto the addressable query information groups Gl n ι . ■ .Gl nz (63), except that the client C n (16) may organize the addressable query information groups Gl n1 ...GI nz (63) thereinto the user service and/or information response ir n (36), as in FIG. 16, and the server PS (18) organizes the addressable query information groups Gl n1 ...GI nz (63) thereinto the corresponding service and/or infonnation response IR n (34), as in FIG. 12. Now again, for the client C n (16), infonnation from the current request group QA nc (50) having the corresponding queries QQ n1 ...QQ nm (53) and the corresponding server addresses AQ n1 ...AQ nm (54) is formulated into the corresponding request pointer/address group QY n (68) having the pointers/addresses PF n ιι...PF n mr (69) associated therewith, as shown in FIG. 16. Now again, for the client C n (16), each ofthe pointers/addresses PF n n...PF n mr (69) are directed to point/address the corresponding addressable response information groups RG n ι...RG nm (57), and aid in obtaining information and/or services therefrom the corresponding addressable response information groups RG n ...RG n m (57) to be incorporated thereinto the addressable query information groups GI n1 ...GI nz (63), as shown in FIG. 16. Again, the grouping and/or sorting criteria allow the user U n (12) to direct the server PS (18) and/or the client C n (16) to sort infonnation and or services therefrom the responses the responses R n ι ...R nm (32) and/or the additional optional responses RA n i...RA nm (40) therefrom the optional database 41, such as, for example, by category, query, group, page, order of importance, ascending and/or descending order, alphabetically and/or numerically, value, price, and/or other characteristics, and/or to combine and/or interleave the information and/or services therefrom the responses the responses R n ι...R n m (32) and/or the additional optional responses RA n1 ..-RA nm (40) one with the other, such as, for example, by order of relevance and/or other parameters. FIG. 17 shows the particular user service and/or information response ir n (36) having the service and/or information group G n (35), the additional request links SL n1 ...SL nw (71), the optional order form 72, the optional additional advertisements and/or links 73, the optional hidden information 74, and the optional service and/or information entry request form IE n (38). Now again, the service and/or information group G n (35) has the query information groups Gl n1 ...GI nz (63), the optional database response groups 75, and the optional additional advertisements and/or links 76. Yet again, the additional request links SL n ι...SL nw (71) allow the user U n (12) to make additional optional selections, based upon information and/or services previously requested by the user U n (12). The additional request links SL n1 ...SL nw (71), which are optional, may typically have Current Group/Next Group/Previous Group/Group Number Links, Server Names in Each Group, Queries in Each Group, Current Page/Next Page/Previous Page/Page Number Links, Search Display/Link and/or Description Placement Interleave/Separate, and Link Description Options/Summary/Minimize. Other additional ones ofthe additional request links SL n1 ...SL nw (71 ) and/or combinations thereof may also be incorporated thereinto the user service and/or information response ir n (36). Now again, for the client C n (16), the optional order form 72 allows direct placement and/or confirmation of orders and/or purchases therewith the servers S-|...S Z (20) and/or the optional servers SOι...SO p (22), which reside on the network 24. The user U n (12) may enter the order placement thereinto the user interface l n (14) therethrough the user input Ul n (25), and receive order confirmation therethrough the user interface l n (14). The client C n (16) may communicate the order placement therefrom the user interface l n (14) thereto the servers Sι...S z (20) and/or the optional servers SO^.-SO p (22), and/or receive the order confirmation therefrom, and communicate the order confirmation therefrom the servers S-i...S z (20) and/or the optional servers SOι...SO p (22) thereto the user interface l n (14) for presentation to the user U n (12). The order placement and or the order confirmation may be stored within the server PS (18) and/or the client C n (16). The order placement and/or the order confirmation is typically secure, and may be encrypted, and is typically communicated using secure communications means. D. FORMULATING QUERY INFORMATION GROUPS Each ofthe particular addressable response information groups RG n ι.-.RG nm (57), designated as the addressable response mformation group RG nm (57), has optional addressable individual information groups LGnmi--- G n r (80), which may be addressed therewith the pointers/addresses PPnmi---PPnmr (64), as shown in FIGS. 11, 15, 18A, 18B, and 18C. Each ofthe addressable response information groups RG n ι...RG nm (57) and each ofthe optional addressable individual information groups LG n ιι...LG nmr (80) therein each ofthe addressable response information groups RG n1 ...RG nm (57) may be addressed therewith the pointers/addresses PP n1 ι...PP nm r (64). Now again, the addressable response information group RG nm (57) has the optional addressable individual information groups LG n mi---LG nm r (80), which may be addressed therewith the pointers/addresses PP n mi---PPnmr (64). Each ofthe addressable individual infonnation groups LG n mi- " LG n mr (80) therein the addressable response information group RG nm (57) may be pointed/addressed by the server PS (18) and/or the client C n (16) to retrieve all and/or a portion and/or combinations thereof of specific ones ofthe addressable individual information groups LGnmi " -LGnmr (80), therefrom the addressable response information group RG nm (57), and incorporate information and or services therefrom the addressable individual information groups LG nm ι...LG nm r (80) thereinto certain ones ofthe addressable query information groups Gl n1 ...GI nz (63), in accordance with the grouping and/or sorting criteria addressing scheme. I The addressable response information group RG nm (57) having the optional addressable individual information groups LGnmi... LG nrnr (80) may have optional addressable pointer/address indices IN nm1 ...IN nmr (81 ) correspondingly associated therewith the optional addressable individual information groups LG nm -- -LGnmr (80), which may be addressed/pointed therewith the pointers/addresses PP n mi---PPnmr (64), and which may be pointed/addressed by the server PS (18) and/or the client C n (16) to retrieve all and/or a portion and/or combinations thereof of specific ones ofthe addressable individual information groups LG nm i...LG n mr (80), and incorporate infonnation and/or services therefrom the addressable individual information groups LG nm i " -LGn r (80) thereinto the certain ones ofthe addressable query information groups Gl n ---Gl nz (63), in accordance with the grouping and/or sorting criteria addressing scheme. FIGS. 18A, 18B, and 18C show the 'addressable response information group RG nm (57) having the addressable individual information groups LG n mi---LG nmr (80) showing the optional addressable pointer/address indices IN nm1 ...IN nrnr (81) correspondingly associated therewith the optional addressable individual information groups LG nrn ι-. - LGnmr (80), which may be addressed/pointed therewith the pointer/addresses PP nm ι (64), PP n 2 (64), and PPnmr (64), respectively. The optional addressable pointer/address index IN nm ι (81) is correspondingly associated therewith the optional addressable individual information group LG nm (80). The optional addressable pointer/address index IN nm2 (81) is correspondingly associated therewith the optional addressable individual information group LG nm2 (80), and so on. The optional addressable pointer/address index IN nm r (81 ) is, thus, correspondingly associated therewith the optional addressable individual information group LG πm ι (80). The pointers/addresses PG n ...PG nz (61) may be formulated as arrays and/or lists. The pointers/addresses PPnmi---PPnmr (64) and/or the pointers/addresses PF n mi---PF n mr (69) may be formulated as arrays and/or lists. The arrays may be multidimensional arrays, and the lists may be lists within lists. The optional addressable individual information group LG nm r (80) is associated therewith and corresponds to a particular one ofthe addressable individual information groups LG n mi---LG n mr (80) therein a particular one ofthe addressable response information groups RG n ι...RG nm (57), designated as the addressable response information group RG nm (57). The first subscript ofthe optional addressable individual information groups LG nm r (80) is associated therewith and corresponds to the particular service and/or information request IQ n (28) and/or the user service and/or information request iq n (27). The second subscript ofthe optional addressable individual information groups LGn r (80) is associated therewith and corresponds to a particular one of "1" through "m" i.e., 1 m, of the addressable response infonnation group RG n1 ...RG nm (57). The third subscript ofthe optional addressable individual information groups LG nm r (80) is associated therewith and corresponds to a particular one of "1" through "r" i.e., 1 r, ofthe optional addressable individual information group LG nm ι ■ ■ -LG nm r (80) within the addressable response information group RG nm (57). The subscripts ofthe optional addressable pointer/address indices IN nm1 ...IN nmr (81) are correspondingly associated therewith the subscripts ofthe corresponding addressable individual infonnation groups LG nm ι...LG n mr (80). A number and variety of pointing/addressing schemes are possible, which may be used for a variety of grouping and sorting criteria schemes and addressing/pointing schemes. For example, the pointers/addresses PG n ι ...PG nz (61 ) ofthe request pointer/address group QZ n (60) may be pointed/addressed thereto certain ones ofthe addressable query pointer/address groups QG n1 ...QG nz (62), in accordance with certain grouping and/or sorting criteria schemes and/or pointing/addressing schemes. The pointers/addresses PP n ιι...PP n mr (64) of each ofthe pointed/addressed addressable query pointer/address groups QG n1 ...QG πz (62) may be pointed thereto the pointer/address indices IN π11 ...IN πmr (81) ofthe optional addressable individual information groups LG n mi---LG nm r, i.e., 1 r, and the pointers/addresses PP n ιι...PP nm r (64), i.e., 1 m, corresponding to the addressable response information groups RG n ι...RG n m (57) formulated by the addressable query pointer/address groups QG n1 ...QG nz (62) may be pointed thereto certain ones ofthe addressable response information groups RG n ι...RG nm (57), in accordance with certain grouping and/or sorting criteria schemes and/or addressing schemes. This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LG nm ι---LG n mr from the addressable response information groups RG n1 ...RG nm (57) is incorporated thereinto the certain ones ofthe addressable query information groups Gl n1 ...GI nz (63), in accordance with the grouping and/or sorting criteria addressing scheme, as formulated by the addressable query pointer/address groups QG n1 ...QG nz (62) and the request pointer/address group QZ π (60). Alternatively and/or additionally, the pointers/addresses PG n ι...PG nz (61) ofthe request pointer/address group QZ n (60) may be incremented therethrough each ofthe addressable query pointer/address groups QG n1 ...QG nz (62). The pointers/addresses PP n ιι-..PPnmr (64) of each ofthe pointed/addressed addressable query pointer/address groups QG n1 ...QG nz (62) may be pointed to the pointer/address indices IN n11 ...IN nm r (81) ofthe optional addressable individual information groups LG nm ι ■ ■ ■ LG nmr , i.e., 1 r, and incremented once, and then the pointers/addresses PP n n...PP n mr (64), i.e., 1 m, corresponding to the addressable response information groups RGni...RG nm (57) formulated by the addressable query pointer/address groups QG n ...QG nz (62) may be incremented therethrough each ofthe addressable response information groups RG n1 ...RG nm (57). This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LGnmi ■ - - LGn r from the addressable response information groups RG n ι ... RG nm (57) is incorporated thereinto the certain ones ofthe addressable query information groups Gl n1 ...GI nz (63), in accordance with the grouping and/or sorting criteria addressing scheme, and as formulated by the addressable query pointer/address groups QG n1 ...QG nz (62). Alternatively and/or additionally, the pointers/addresses PP n ii...PP n mr (64), i.e., 1 m, may be incremented, corresponding to the addressable response information group s RG n1 ...RG nm (57) formulated by the addressable query pointer/address groups QG n1 ...QG nz (62), and then the pointers/addresses PP n ι.|...PPn mr (64), i.e., 1 r, pointing to the pointer/address indices IN n1 ...IN nmr (81) ofthe optional addressable individual information groups LGnm - ■■ LGnmr may then be incremented. This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LG nm ι - - - LG nm from the addressable response information group s RG n ι...RG n m (57) is incorporated thereinto the certain ones ofthe addressable query information groups Gl n ...GI nz (63), in accordance with the grouping and/or sorting criteria addressing scheme, and as formulated by the addressable query pointer/address groups QG n1 ...QG nz (62). Alternatively and/or additionally, the pointers/addresses PF nm ---PFnmr (69), i.e., 1 m, may be incremented, corresponding to the addressable response information group s RG n ...RG nm (57) formulated by the addressable query pointer/address groups QG n1 ...QG nz (62), and then the pointers/addresses PF n mi---PF n mr (69), i.e., 1 r, pointing to the pointer/address indices IN n 1 ...IN nmr (81) ofthe optional addressable individual information groups LG πm ι .. -LGnmr may then be incremented. This subprocess may be repeated until the information and/or services from the optional addressable individual infonnation groups LG nm ι ■ ■ ■ LG nm r from the addressable response information group s RG n1 ...RG nm (57) is incorporated thereinto the certain ones ofthe addressable query information groups Gl n1 ...GI nz (63), in accordance with the grouping and/or sorting criteria addressing scheme, and as formulated by the addressable query. pointer/address groups QG n ...QG nz (62). The typical sorting and/or grouping criteria and the addressing/pointing schemes mentioned immediately above, for example, may group certain ones ofthe queries QQ n1 ...QQ nm (53) having the same and/or substantially the same values grouped therein a particular one ofthe query information groups Gl nz ...GI nz (63), designated as the query information group Gl nz (63). The grouping and/or sorting criteria and schemes and the addressing/pointing schemes mentioned herein are but only a small portion of a much larger variety of grouping and/or sorting criteria and schemes and addressing/pointing schemes and/or combinations thereof that the client-server multitasking system 10 of the present invention may use and is capable of. The above mentioned examples are included herein to illustrate but a few examples ofthe capabilities ofthe client-server multitasking system 10 ofthe present invention. The addressable individual information groups LG n mi---LG nmr (80) are typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other, as the addressable individual information groups LG nm i---LG nmr (80) are incorporated thereinto the addressable response information group s RG n1 ...RG n m (57) therefrom the responses R n ...R nm (32). Alternatively and/or additionally the addressable individual information groups LG n mi-..LG nrn r (80) may be incorporated thereinto the addressable response information group s RG n1 ...RG nm (57) therefrom the responses R n1 ...Rnm (32) in an as-is condition and/or in raw form. The optional addressable individual information groups LG n mi---LG π mr (80) therein the addressable response information group RG nm (57), having information and or services parsed and/or processed, and or formatted, and/or grouped therefrom the response R nm (32), may be correspondingly associated therewith the locations ofthe information and/or services therein the response R nm (32). Each ofthe addressable individual information groups LG nm i...LG nm r (80) may have and/or be parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into corresponding optional links LDnmi---LD nmr (82), and/or corresponding optional descriptions DD nm1 ...DD nmr (83), and/or corresponding optional prices/values PD nm ι...PD n mr (84), and/or corresponding optional images ID nm1 ...ID nmr (85), as shown in FIG. 19. The optional links LDnmi---LD nm r (82), the corresponding optional descriptions DD nm1 ...DD nmr (83), the corresponding optional prices/values PD nrn ι...PD nm r (84), and the corresponding optional images ID nm ...ID nmr (85), corresponding to the addressable individual information groups LG nm ι-- -LGnmr (80) are typically associated correspondingly one with the other. The optional link LD nm ι (82), the corresponding optional description DD nm ι (83), the corresponding optional price/value PD nm1 (84), and the corresponding optional image ID nm (85), corresponding to the optional individual information group LG nm (80) are typically associated correspondingly one with the other. The optional link LD nm2 (82), the corresponding optional description DD nm2 (83), the corresponding optional price/value PD nm2 (84), and the corresponding optional image ID nm2 (85), corresponding to the addressable individual information group LG nm2 (80) are typically associated correspondingly one with the other, and so on. The optional link LD nmr (82), the corresponding optional description DD nm r (83), the corresponding optional price/value PD nm r (84), and the corresponding optional image ID nm r (85), corresponding to the addressable individual information group LG nmr (80) are, thus, typically associated correspondingly one with the other. The addressable individual information groups LG nm ι ■ ■ ■ LG nm r (80), which may have the corresponding optional links LD n mi- --LDnmr (82), and/or the corresponding optional descriptions DD nm1 ...DD nmr (83), and/or the corresponding optional prices/values PD nm ι...PD n mr (84), and or the corresponding optional images ID nm1 .-.ID nnι (85) are appended therewith labels/identifiers, as shown in FIG. 20, and incorporated thereinto certain ones ofthe addressable query information groups Gl n1 ...GI nz (63), depending upon the grouping and/or sorting criteria. FIG. 21 shows a particular one ofthe addressable query information groups Gl n1 ...GI nz (63), designated as the query information group Gl nz (63). Now again, the optional addressable individual information group LG nm r (80) is associated therewith and corresponds to a particular one ofthe addressable individual information groups LG n mi---LG n m r (80) therein a particular one ofthe addressable response information group s RG n ι...RG nm (57), designated as the addressable response information group RG nm (57). The first subscript ofthe optional addressable individual information groups LGnm r (80) is associated therewith and corresponds to the particular service and or information request IQ n (28) and/or the user service and/or information request iq n (27). The second subscript ofthe optional addressable individual information groups LG nmr (80) is associated therewith and corresponds to a particular one of "1" through "m" i.e., 1 m, of the addressable response information group RG n ι...RG nm (57). The third subscript of the optional addressable individual information groups LG nm r (80) is associated therewith and corresponds to a particular one of "1" through "r", i.e., 1 r, ofthe optional addressable individual information group LGnmi---LGnmr (80) within the addressable response information group RG nm (57). FIG. 20 shows a labelled individual information group LL nzu (86) associated therewith a particular one ofthe addressable query information groups Gl n1 ...GI nz (63), designated as the addressable query information group Gl πz (63), having optional group identifier GL nc (87), optional query link identifier LN ncu (88), optional resource location identifier SU nw (89), optional'server and/or query identifier Sl nm (90), and/or optional server link identifier LXnmr (91) appended thereto the addressable individual infonnation group LG n r (80). The first alphanumeric subscript ofthe labelled individual information group LL nzu (86) is associated therewith and corresponds to the service and/or information response IR n (34) and/or the user service and/or information response ir n (36). The second alphanumeric subscript ofthe labelled individual information group LL nzu (86) is associated therewith and corresponds to a particular one of "1" through "z", i.e., 1 z, ofthe addressable query information groups Gl n1 ...GI nz (63), designated as the addressable query information group Gl nz (63), which the labelled individual information group LL nzu (86) is incorporated therein. The third alphanumeric subscript ofthe labelled individual information group LL nzu (86) is associated therewith and corresponds to a particular one of "1" through "u", i.e., 1 u, of labelled individual information groups LL nz ι .. -LL nzu (86) within the addressable query information group Gl nz (63). The optional group identifier GL nc (87) labels and/or identifies the current request group QA πc (50). The optional group identifier GL nc (87) is associated therewith and corresponds to the current request group QA nc (50), which may be any particular one the request groups QA n1 ...QA nz (51) selected by the user U n (12). The first alphanumeric subscript ofthe optional group identifier GL nc (87) is associated therewith and corresponds to the service and/or information response IR n (34) and/or the user service and/or information response ir n (36). The second subscript ofthe optional group identifier GL nc (87) is associated therewith and corresponds to the particular one ofthe request groups QA n1 ...QA nz (51) selected by the user U n (12) as the current request group QA nc (50). The optional query link identifier LN ncu (88) is also associated therewith and corresponds to the current request group QA nc (50). The optional query link identifier LN ncu (88) labels and/or identifies the labelled individual information group LL nzu (86). The first alphanumeric subscript ofthe optional query link identifier LN ncu (88) is associated therewith and corresponds to the service and/or information response IR n (34) and/or the user service and/or information response ir n (36). The second subscript ofthe optional query link identifier LN ncu (88) is also associated therewith and corresponds to the particular one ofthe request groups QA n1 ...QA nz (51) selected by the user U n (12) as the current request group QA nc (50). The third alphanumeric subscript ofthe optional query link identifier LN ncu (88) is associated therewith and corresponds to a particular one of "1" through "u", i.e., 1 u, of the labelled individual information groups LL nr ι ■ ■ -LL nzu (86) therein the addressable query information group Gl nz (63). The optional resource location identifier SU nw (89) labels and/or identifies resource locations of information and/or services associated therewith and corresponding to the optional addressable individual information group LG nm r (80) therein the labelled individual information group LL nzu (86). The optional resource location identifier SU nw (89) indicates and is associated therewith and corresponds to resource locations of information and/or services associated therewith certain ones ofthe optional servers SO>|...SO p (22) and/or certain ones ofthe servers S<|...S Z (20). The optional resource location identifier SU nw (89) may be obtained from certain information therein the optional addressable individual information group LG nmr (80). The first alphanumeric subscript ofthe optional resource location identifier SU nw (89) is associated therewith and corresponds to the service and/or information response IR n (34) and/or the user service and/or information response ir n (36). The second alphanumeric subscript ofthe optional resource location identifier SU nw (89) is associated therewith and corresponds to a particular one of "1" through "w", i.e., 1 w, ofthe optional resource location identifiers SU n1 ...SU nw (89) therein the labelled individual information group LL nzu (86). The optional server and/or query identifier Sl nm (90) labels and/or identifies the query QQ nm (53) and/or the corresponding server address AQ nm (54) associated therewith and corresponding to the optional addressable individual information group LG n r (80) therein the corresponding labelled individual information group LL nzu (86) ofthe current request group QA nc (50). The first alphanumeric subscript ofthe optional server and/or query identifier Sl nm (90) is associated therewith and corresponds to the service and/or information response IR n (34) and/or the user service and/or infonnation response ir n (36). The second alphanumeric subscript ofthe optional server and/or query identifier Sl nm (90) is associated therewith and corresponds to a particular one of "1" through "m", i.e., 1 m, ofthe optional server and/or query identifiers Sl n1 ...SI nm (90), which may be correspondingly associated therewith the corresponding ones ofthe queries QQ n ...QQ nm (53) and/or the corresponding ones ofthe server addresses AQ n ι - - -AQ nm (54). The optional server link identifier LX nmr (91) labels and/or identifies the location ofthe optional addressable individual information group LG nm r (80) therein the corresponding addressable response information groups RG nm (57). The first alphanumeric subscript ofthe optional server link identifier LX nmr (91) is associated therewith and corresponds to the service and/or information response IR n (34) and/or the user service and/or information response ir n (36). The second alphanumeric subscript ofthe optional server link identifier LX nm r (91) is associated therewith and corresponds to the addressable response information group RG nm (57). The third alphanumeric subscript o the optional server link identifier LX nm r (91) is associated therewith and corresponds to a particular one of "1" through "r", i.e., 1 r, ofthe optional server link identifiers LX nm ι...LX n mr (91), which may be correspondingly associated therewith the locations of certain ones ofthe optional addressable individual information group LG nm i---LGnmr (80) therein the addressable response information groups RG n (57). The certain ones ofthe optional addressable individual information groups LG n m ---LG n mr (80) therein the addressable response information group RG nm (57), having information and/or services parsed and/or processed, and/or formatted, and/or grouped therefrom the response R nm (32), which are labelled and/or identified therewith the optional server link identifiers LX nm ι...LX nmr (91), are correspondingly associated therewith the locations ofthe information and/or services therein the response R nm (32). The optional server link identifiers LX n ι---LXnmr (91), thus, identify and/or label the location of services and/or information therein the response R nm (32). FIG. 21 shows the addressable query information group Gl nz (63) having the labelled individual information groups LL nz ...LL nzu (86), optional database labelled individual information groups RL nz ι...RL nzx (92), optional query description QT nz (93), optional server descriptions and/or links ST nz ι...ST nZf (94), and optional advertisements and/or links LT nz ι...LT nzt (95). The first and second subscripts ofthe optional database labelled individual information groups RL nz1 ...RL nzx (92), the optional query description QT nz (93), the optional server descriptions and/or links ST nz ι ...ST nzτ (94), and the optional advertisements and/or links LT nr ι ■ ■ ■ LT nzt (95) are associated therewith and correspond to the addressable query information group Gl nz (63). The third subscripts ofthe optional database labelled individual infonnation groups RL nz ...RL nzx (92), the optional server descriptions and/or links ST nz ι...ST nZf (94), and the optional advertisements and/or links LT nz ...LT nzt (95) are associated therewith and correspond to ones ofthe optional database labelled individual information groups RL nz ...RL nzx (92), the optional server descriptions and or links ST nz ι...ST nZf (94), and the optional advertisements and/or links LT nz ι...LT nzt (95), respectively. IV PROCESS FIG. 22 shows steps of a client-server multitasking process 99 ofthe present invention. The client-server multitasking process 99 is shown for the client-server multitasking system 10 for a particular one ofthe users U...U n (12), designated as the user U n (12), the corresponding particular one ofthe user interfaces l...l n (14), designated as the user interface l n (14), the corresponding particular one ofthe clients C...C n (16), designated as the client C n (16), the server PS (18), the servers S<|...S Z (20), and the optional servers SO-|...SO p (22), which reside on the network 24. The client-server multitasking process 99 starts at step 101. The user U n (12) enters the user input Ul n (25) thereinto the user interface l n (14) (step 102). The user input Ul n (25) is formulated thereinto the user service and or information request iq n (27) at the user interface l n (14) and communicated thereto the client C n (16) (step 103). The user service and or information request iq n (27) may be formulated thereinto the service and/or information request lQ n (28) at the client C n (16) and communicated thereto the server PS (18) (also step 103). The service and/or information response IR n (34) and/or the user service and/or information response ir n (36) are derived at the server PS (18) and/or the client C n (16), respectively, at step 104, which in itself is a process, and may hereinafter be referred to as the multitasking process 104. The multitasking process 104 will be discussed in more detail later with reference to FIGS. 22-lA and 22-lB. Now, continuing with FIG. 22, the user service and/or information response ir n (36) may be derived at the client C n (16) (step 104) therefrom the service and/or information response IR n (34), which may be communicated thereto the client C n (16) therefrom the server PS (18) (also step 104), and/or alternatively and/or additionally therefrom the responses R π ...R π m (32), which may be communicated thereto the client C π (16) (step 104). Now, the client C n (16) may communicate the service and/or information request IQ n (28) thereto the server PS (18) (step 103). The service and/or ' information response IR n (34) is then derived at the server PS (18) (step 104) and communicated thereto the client C n (16) (also step 104). The user service and/or information response ir n (36) may be derived therefrom the service and/or information response IR n (34) (also step 104). Now, in more detail, if the service and/or information request lQ n (28) is communicated thereto the server PS (18) (step 103), then the server PS (18) makes the requests Q n ι - - -Qnm (29) and/or certain ones ofthe requests Q n ι...Qnm (29) thereof the servers S< t ...S z (20), in accordance with the designation scheme which designates the certain ones ofthe servers S<|...S Z (20) to be communicated with corresponding to the requests Q n ι...Q n m (29) as the corresponding server designations Sn ...S nm (30), utilizing information therefrom the service and/or information request IQ n (28). The service and/or information response IR n (34) is then derived at the server PS (18) (step 104) therefrom the responses R n ι ...R n (32) received from the servers Si ...S z (20) corresponding to the server designations S n ι...S n m (30), and communicated thereto the client C n (16). Now, again, the user service and/or information response ir n (36) may be derived therefrom the service and/or information response IR n (34) (also step 104). Now, also in more detail, alternatively and/or additionally, the client C n (16) may make the requests Q n ι...Q n m (29) and/or certain other ones ofthe requests Q n ι...Q n m (29) thereof the servers S<ι...S z (20), in accordance with the designation scheme which designates the certain ones ofthe servers S<|...S Z (20) to be communicated with corresponding to the requests Q π ι...Q n m (29) as the corresponding server designations S n ι...S nm (30), utilizing information therefrom the user service and or information request iq n (27). Now, again, the user service and/or information response ir n (36) may also be derived at the client C n (16) (step 104) therefrom the responses Rni...R n m (32) communicated thereto the client C n (16) (step 104) and/or alternatively and/or additionally therefrom the service and/or information response IR n (34) communicated thereto the client C n (16) therefrom the server PS (18) (also step 104). The user service and/or information response ir n (36), thus, may be derived therefrom the service and/or information response IR n (34) communicated therefrom the server PS (18) thereto the client C n (16) and/or alternatively and or additionally therefrom the responses R n ι...R nm (32) communicated thereto the client C n (16) (step 104). The user service and/or information response ir n (36) is communicated thereto the user interface l n (14) (step 105) and incorporated thereinto the user response UR n (37). The user U π (12) reviews the user response UR n (37) and/or selects additional services and or information (step 106). Step 106 will be discussed in more detail later with reference to FIG. 22-2. The process 99 ends at step 107. The process 99 will be described in more detail with reference to FIGS. 1-70 ofthe drawings. The service and/or information response IR n (34) and/or the user service and or information response ir n (36) are derived at the server PS (18) and/or the client C n (16), respectively, at step 104 in FIG. 22, and shown in more detail in FIGS. 22-lA and 22-lB. FIG. 22-lA shows the multitasking process 104 of deriving the service and or information response IR n (34) and or the user service and/or infonnation response ir n (36), with reference to FIGS. 11 and 15. FIG. 22-lB shows the multitasking process 104 of deriving the service and/or information response IR n (34) and or the user service and/or infonnation response ir n (36) having other grouping/sorting that may be used additionally and/or alternatively to that of FIGS. 11 and 15, as shown with reference to FIGS. 12 and 16. The multitasking process 104 will also be described in more detail with reference to FIGS. 1-70 ofthe drawings. The server PS (18) and/or the client C π (16) parse, process, and/or format the service and/or information request IQn (28) and/or the user service and/or infonnation request iq n (27) into the current request group QA nc (50), the request groups QA n1 ...QA nz (51), and the optional instructions VJ n1 ...VJ nk (52) (step 104-1), as shown in FIGS. 22-lA and 22-lB. Information therefrom the current request group QA nc (50) and the optional instructions VJ n ι...VJ nk (52) may be used to make the requests Q n ...Q n m (29), obtain the responses R n ι...R n m (32), and incorporate information therefrom into the service and/or information response IR n (34) and/or the user service and/or information response ir n (36), as shown in FIGS. 22-lA and 22-lB with reference to FIGS. 11, 12, 15, and 16. The current request group QAn c (50) may be any particular one the request groups QA n1 ...QA nz (51), which may be selected by the user U n (12). The current request group QA nc (50) has the corresponding queries QQ n1 ...QQ nm (53) and the corresponding server addresses AQ n1 ...AQ nm (54) to open connections with and make the requests Q n ι...Q nm (29) thereof the servers S-|...S Z (20), in accordance with the designation scheme which designates the certain ones ofthe servers S^.-Sz (20) to be communicated with corresponding to the requests Q n1 ...Q nm (29) as the corresponding server designations S n ι..-S nm (30), shown for the particular service and/or information request IQ n (28) and/or the particular user service and or information request iq n (27). The server PS (18) and/or the client C n (16) open connections with and make the requests Q n ι...Q nm (29) having the corresponding queries QQ n ι - - ■ QQnm (53) and the corresponding server addresses AQ n ι ... AQ nm (54) therein the current request group QA nc (50) thereof the servers S.]...S Z (20) (step 104-2) as shown in FIGS. 22-lA and 22-lB, in accordance with the designation scheme which designates the certain ones ofthe servers Sι...S z (20) to be communicated with corresponding to the requests Q n ι...Q nm (29) as the corresponding server designations S n1 ...S nm (30). The servers S<]...S Z (20) corresponding to the server designations S n ι...S nm (30), designated in accordance with the designation scheme which designates the certain ones ofthe servers S^.-S;, (20) to be communicated with corresponding to the requests Q n ι...Q n m (29) as the corresponding server designations Sιι...S nm (30), respond to the requests Q n ι...Q nm (29) with the corresponding responses R n i...R nm (32). The server PS (18) and/or the client C n (16) parse, and/or process, and/or format, and/or group, and or organize each ofthe responses R n ι...R n m (32) received from the servers S-|...S Z (20) (step 104-3), as shown in FIGS. 22-lA and 22-lB with reference to FIGS. 36-38, corresponding to the server designations S n ι...S nm (30) thereinto the corresponding addressable response infonnation groups RG n ι...RG n m (57). The server PS (18) and/or the client C n (16) may also make additional optional requests QP n1 ...QPnm (58) ofthe optional databases 41 and/or 42 (also step 104-2 of FIGS. 22-lA and 22-lB), which may be optionally resident within the server PS (18) and or the client C n (16), and which may reply with the corresponding additional optional responses RA n i...RA nm (40). The server PS (18) and/or the client C n (16) parse, and/or process, and/or format, and/or group, and/or organize each ofthe additional optional responses RA n1 ...RA nm (40) into the corresponding response information groups RC π1 ...RC nm (59) (also step 104-3 of FIGS. 22-lA and 22-lB). Now, step 104-3 of FIGS. 22-lA and 22-lB is shown in more detail in FIG. 22-1-1. As discussed later, and shown in FIGS. 36-38, entity body RH nm (353) ofthe response R nm (32) has optional response individual information groups LS nm1 ...LS nm r (360). Each ofthe optional response individual infonnation groups LS n ι ...LS nm r (360) and/or portions thereof therefrom the entity bodies RH n ι...RH n m (353) ofthe responses R n ...R n m (32) may be optionally compared one with the other, and duplicate ones ofthe optional response individual information groups LS n ιι...LS nm r (360) may be optionally discarded (step 104-3-1), as shown in FIG. 22-1-1. The remaining optional response individual information groups LS n i ...LS nmr (360) are parsed, and/or processed, and/or formatted, and/or organized, and/or grouped thereinto corresponding ones ofthe addressable individual information groups LG n ιι...LG n mr (80) as the addressable individual information groups LG n ιι...LG n mr (80) are incorporated thereinto the addressable response information group s RG n ...RG nm (57) therefrom the responses Rni— nm (32) (step 104-3-2), as shown in FIG. 22-1-1. The addressable individual information groups LG n 1 ... LG nm r (80) are typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other, as the addressable individual information groups LG n ιι...LG n mr (80) are incorporated thereinto the addressable response information group s RGni-.-RGnm (57) therefrom the responses R n ι...R nm (32). The server PS (18) and or the client C n (16) may formulate information from the current request group QA nc (50) having the corresponding queries QQ n ι ■ - -QQnm (53) and the corresponding server addresses AQ n ι .. -AQ nm (54) into the corresponding request pointer/address group QZ n (60) having the pointers/addresses PG n ..-PG nz (61) associated therewith (step 104-4 ofFIG. 22-lA with reference to FIGS. 11, 15, and 28). Alternatively and/or additionally, the server PS (18) and or the client C n (16) may formulate information from the current request group QA nc (50) having the corresponding queries QQ π ι - - -QQnm (53) and the corresponding server addresses AQ n i--.AQnm (54) into a corresponding request pointer/address group QY n (68) having the pointers/addresses PF n ii...PFnmr (69) associated therewith (step 104-4 of FIG. 22-lB with reference to FIGS. 12 and 16). The server PS (18) and/or the client C n (16) may formulate the addressable query pointer/address groups QGni...QG nz (62) (step 104-5 of FIG. 22-lA with reference to FIGS. 11, 15, 28, 33, and typical ones ofthe addressable query pointer/address groups QG n ...QG nz (62) in FIGS. 29 and 30), depending upon the grouping and/or sorting criteria used. Each ofthe pointers/addresses PG n1 ...PG nz (61 ) may be directed to point/address the corresponding addressable query pointer/address groups QG n1 ...QG nz (62) associated therewith, which aid in obtaining information and/or services therefrom certain ones of addressable response information groups RG n1 ...RG nm (57) to be incorporated thereinto addressable query information groups Gl n ...GI nz (63). Each ofthe addressable query pointer/address groups QG n ...QG nz (62) has the pointers/addresses PP n n...PP n mr (64) directed to address/point information therein the addressable response information groups RG n ι...RG n m (57) based upon the grouping and/or sorting criteria. The grouping and/or sorting criteria may be incorporated thereinto the optional instructions VJ n1 ...VJ nk (52), which may be entered thereinto the user interface l n (14) therethrough the user input Ul n (25) by the user U n (12). Grouping and/or sorting criteria may additionally and/or alternatively optionally resident within the server PS (18) and/or the client C n (16). The grouping and/or sorting criteria gives the user U n (12) the ability to formulate the query information groups Gl n ---Gl nz (63) and the way in which information and/or services from the addressable response information groups RGni-.-RGnm (57) is presented to the user U n (12) therethrough the user interface l n (14). Information and/or services within each ofthe addressable response information groups RG n ι...RG nm (57) is addressed therewith the pointers/addresses PP n n . ■ .PP nm r (64) therefrom the query pointer/address groups QG n1 ...QG nz (62), and infonnation and/or services therefrom the addressable response information groups RG n ι...RG nm (57) is incorporated thereinto the addressable query infonnation groups Gl n ...GI nz (63) 5 corresponding to the pointers/addresses PP n ι --. PPnmr (64) (step 104-6 of FIG. 22-lA), which are formulated by the addressable query pointer/address groups QG n1 ...QG nz (62), in accordance with the grouping and/or sorting criteria, as shown in FIG. 22-lA with reference to FIGS. 11, 15, 18A, 18B, 18C, 19 - 21, 28, 33, typical ones ofthe addressable query pointer/address groups QG n1 ...QG nz (62) in FIGS. 29 and 30, and a typical one ofthe addressable query information groups Gl n1 ...GI nz (63), designated as the addressable query information group Gl nz 10 (63), in FIG. 40. Alternatively and/or additionally, each of the pointers/addresses PF n ιι...PF πm r (69) may directed to point/address the corresponding addressable response information groups RG n ι...RG nm (57), and aid in obtaining information and/or services therefrom the corresponding addressable response information groups RG n i...RG nm (57) to be 15 incorporated thereinto the addressable query information groups Gl n ...GI nz (63) (step 104-6) as shown FIG. 22-lB with reference to FIGS. 12, 16, 18A, 18B, 18C, 19 - 21, and another typical one ofthe addressable query information groups Gl n ...GI nz (63), designated as the addressable query information group Gl nz (63), in FIG. 41. Now, step 104-6 of FIG. 22-lA is shown in more detail in FIG. 22-1-2A with reference to FIGS. 11, 15, 18A, 18B, 20 18C, 19 - 21, 28, 33, typical ones ofthe addressable query pointer/address groups QG n ι...QG nz (62) in FIGS. 29 and 30, and a typical one ofthe addressable query infonnation groups Gl n1 ...GI nz (63), designated as the addressable query information group Gl nz (63), in FIG. 40. Step 104-6 of FIG. 22-lB is shown in more detail in FIG. 22-1-2B with reference to FIGS. 12, 16, 18A, 18B, 18C, 19 - 21, and another typical one ofthe addressable query information groups Gl n1 ...GI nz (63), designated as the addressable query infonnation group Gl nz (63), in FIG. 25 41. The optional addressable individual information groups LGniι...LG nm r (80) therein each ofthe addressable response information groups RG n i...RG nm (57) may be addressed therewith the pointers/addresses PP n n...PP n mr (64) (step 104-6-1) as shown FIG. 22-1-2A with reference to FIGS. 11 and 15 and FIG. 22-lA. 30 The optional addressable individual information groups LG n ι ...LG n mr (80) therein each ofthe addressable response information groups RG n ι...RG n (57) may alternatively and/or additionally be addressed therewith the pointers/addresses PF n ιι...PF n mr (69) (step 104-6-1) as shown FIG. 22-1-2B with reference to FIGS. 12 and 16 and FIG. 22-lB. 35 The addressed optional addressable individual information groups LG n ιι...LG n mr (80) an/or portions thereof may be optionally labelled with labels and/or identifiers and incorporated thereinto the labelled individual information groups LL nz ι... LLp z u (86) (step 104-6-2), as shown in FIGS. 22-1-2A and 22-1-2B. The labelled individual information groups LL nz1 ...LL nzu (86) may be incorporated thereinto certain ones ofthe addressable query information groups Gl n ...GI nz (63), depending upon the grouping and/or sorting criteria (step 104-6-3), as shown in FIGS. 22-1-2A and 22-1-2B. The addressed optional addressable individual information groups LGniι...LG nm r (80) an/or portions thereof are typically appended with the labels and/or identifiers, thus creating the labelled individual information groups LL nz ...LL nzu (86), as each ofthe labelled individual information groups LL nz1 ...LL nzu (86) are incorporated thereinto the certain ones ofthe addressable query information groups Gl n1 ...GI nz (63). The steps 104-6-2 and 104-6-3 are thus typically consolidated into a single step. The addressable query information groups Gl n1 ...GI nz (63) may then be incorporated thereinto the service and/or information response IR n (34) (step 104-7), as shown in FIGS. 22-lA and 22-lB with reference to FIG. 13, and/or the user service and or infonnation response ir n (36) (also step 104-7), as also shown in FIGS. 22-lA and 22-lB but with reference to FIG. 17. The user U n (12) reviews the user response UR n (37) the user interface l n (14) and/or selects additional services and/or information at step 106 in FIG. 22, and shown in more detail in FIG. 22-2. The step 106 will also be described in more detail with reference to FIGS. 1-70 ofthe drawings. The user U n (12) selects additional services and/or information therethrough the user interface l n (14) (step 106-1) or exits to the end ofthe process 99 at step 107. If the user U n (12) selects additional services and/or information therethrough the user interface l n (14) (step 106-1), the user U n (12) may optionally enter one or more orders thereinto an order form and/or order forms thereat and therethrough the user interface l n (14) (step 106-2). The order and/or orders may be, for example, for purchases, and/or instructions, and/or payment, and/or other information and/or services to be directed to and/or requested thereof third parties, and/or combinations thereof, of the optional servers SOι...SO p (22), and/or the servers S<|...S Z (20), and/or other ones ofthe clients C|...Cn (16) therethrough the server PS (18) and/or the client C n (16). The order and/or orders may, thus, be placed therethrough and thereby the server PS (18) and or the client C n (16), eliminating the need for the user U n (12) to place separate ones ofthe orders with the third parties, the optional servers SO^-.SO p (22), and/or the servers S 1 ...S z (20) separately and/or individually. The server PS (18) and/or the client C n (16) process the orders and/or communicate the orders to the third parties, the optional servers SOι...SO p (22), and/or the servers Sι...S z (20), and/or other ones ofthe clients Cι...C n (16) (step 106-3). The server PS (18) and/or the client C n (16) confirm the order (step 106-4). The user U n (12) may select additional services and/or information therethrough the user interface l n (14) (step 106-1) or exit to the end of the process 99 at step 107. If the user U n (12) selects additional services and or information therethrough the user interface l n (14) (step 106- 1), the user U n (12) may alternatively and/or additionally optionally enter information and/or service requests ofthe optional servers SO^.-SO p (22), and/or the servers S.]...S Z (20) therethrough the user interface l n (14) (step 106- 5) and/or exit to the end ofthe process 99 at step 107. If the user U n (12) selects additional services and/or information therethrough the user interface l n (14) (step 106- 1), the user U n (12) may alternatively and/or additionally optionally enter additional requests as the user input Ul n (25) thereat and therethrough the user interface l n (14) (step 106-6) and enter the process 99 at step 102. V. ADDITIONAL DETAILS A. USER INPUT The user input Ul n (25), which the user U n (12) makes therethrough the user interface l n (14), may have one or a plurality ofthe same and/or different ones ofthe queries QQ n1 ...QQ nm (53) to be made by the server PS (18) and/or the client C n (16) ofthe same and/or different ones ofthe servers S.]...S Z (20), in accordance with the designation scheme which designates the servers S-|...S Z (20) to be communicated with corresponding to the requests Q n ι...Q nm (29) as the corresponding server designations S n ι...S nm (30) at the corresponding server addresses AQ n ι ... AQ nm (54). The server PS (18) and/or the client C n (16) parse, process, format, sort, group, and/or organize each ofthe responses R n ι..-R n m (32) to the corresponding requests Q n ι...Q nm (29), received therefrom the servers S<]...S Z (20) designated by the server designations S n ι..-S nm (30), and/or each ofthe additional optional responses RA n ι...RA nm (40) therefrom the server PS (18) and/or the client C n (16). The parsed, processed, formatted, sorted, grouped, and/or organized results therefrom the server PS (18) and/or the client C n (16) are communicated thereto the user U n (12) therethrough the user interface l n (14) as the user response UR n (37), which the user U n (12) may review, interact therewith, and/or select additional services and or information therefrom. The user U n (12) enters the user input Ul n (25) having one or more ofthe same and/or different user requests qu n ---qu nu (26) thereinto user interface l n (14), as shown in FIG. 3. The user requests qu n1 ...qu nu (26) are communicated from the user interface l n (14) to the client C n (16) within the user service and/or information request iq n (27), having the user requests qu n1 ...qu nu (26) and other optional information. The user U n (12) may enter the user input Ul n (25) having one or more ofthe same and/or different user requests qu n1 ...qu nu (26) thereinto the service and/or information entry request form IE n (38) at the user interface l n (14), or thereinto the user interface l n (14) therethrough other suitable means. The user interfaces l-|...l n (14) have suitable input means and/or suitable presentation and or display means, which allow the corresponding users (12) to communicate therewith the corresponding clients Cι...C n (16). The user U n (12) may enter the user input Ul n (25) thereinto the service and/or information entry request form IE n (38) at the user interface l n (14). The user input Ul n (25) may be entered as user input values thereinto fields or alternate request links ofthe service and/or information entry request form IE n (38). B. USER INTERFACE DETAILS The client-server multitasking system 10 ofthe present invention may have any suitable user interface l n (14) acceptable to and/or preferred by the user U n (12), and acceptable to the client C n (16). The user interface l n (14) may be, for example, a graphical user interface, visual, aural, and/or tactile user interface, and/or combination thereof, or other suitable interface. The user interface l n (14) may be integral with the client C n (16) or separate therefrom. The user interface l n (14) may be hardware based, and/or computer based, and/or process based, and/or a combination thereof, and may be a graphical user interface, such as, for example, a browser and/or combinations thereof, varieties of which are commonly used on the internet. The service and/or information entry request form IE n (38) may be optionally available to the user U n (12) at the user interface l n (14), or the user U n (12) may optionally request the service and/or information entry request form IE n (38) therethrough the user interface l n (14). Now again, the user interfaces lι-..l n (14) may each be different, one from the other, or the same, and may change characteristics over time. Each ofthe user interfaces l-ι...l n (14) may change characteristics as a function of time, information, and/or instructions, and/or other means, which may be derived by the users U<|...U n (12) and/or the clients Ci ...C n (16) and/or the servers Si ...S z (20), and/or the server PS (18), and/or the optional servers SOι...SO p (22), and/or derived within the user interfaces li-..l n (14). The user interface I-i l n (14) may change state. The user interface l-|...l n (14) may also change as a function of optional timers and/or timed instructions associated therewith the user interfaces lι...l n (14), and/or associated therewith the clients Cι...C n (16) and/or associated therewith the servers Sι-..S Z (20), and/or associated therewith the server PS (18), and/or associated therewith the optional servers SOι...SO p (22), and/or instructions from the user U^.-Un (12). Changes in the user interface l n (14) may appear continuous to the user'U n (12), spaced in time, staccato, or static depending upon the optional timers and/or the timed instructions. Other conditions may change the user interface l-|...l n (14), as well. The user interfaces lι ...l n (14) may be updated continuously, intermittently, manually, randomly, semi-automatically, automatically, repetitively, non-repetitively, singly, plurally, multiplexed, and/or a combination thereof or other suitable manner. The user interfaces ...l n (14) may be visual, such as graphical user interfaces, aural, and/or tactile, a combination thereof, and/or other suitable means. The user interfaces ...l n (14) may be integral with the clients C^-.C n (16) or separate therefrom. The user interfaces l ...l n (14) may change in response to the user inputs UI-|...UI n (25), the service and/or information entry request forms lE^.TEn (38) at the user interfaces lι...l n (14), completed service and/or information request forms IF n , the user service and/or information requests iq 1 ...iq n (27), optional execute request elements, accessing the alternate request links QLn-.-QL^, accessing server request links UL^-.-UL^, accessing the additional request links SLπ...SL-| W (71), the service and or information responses IR-|...lRn (34), the service and or information response forms lS<ι...IS n (39). Other conditions may change the user interface lι...l n (14), as well. Portions ofthe user responses URι...UR n (37) may be mapped into and/or onto different portions ofthe user interfaces lι...l n (14) to facilitate interaction with and the needs of each ofthe users U<|...U n (12). Such mappings may be optionally customized by the users U^-.Un (12). C. SERVICE AND/OR INFORMATION REQUEST DETAILS Each ofthe users Uι...U n (12) communicate the corresponding user service and/or information requests iqι...iq n (27) therethrough the corresponding user interfaces lι...l n (14) to the corresponding clients Cι..;C n (16), which optionally format the corresponding user service and/or information requests iqi ...iq n (27) into the corresponding service and/or information requests IQι...lQ n (28), as required. Now, again, the user U n (12) may instruct the user interface l n (14) to communicate the user service and/or information requests iq n (27). The user service and/or information request iq n (27) is communicated from the user interface l n (14) to the client C n (16), which acts upon the user service and/or information request iq n (27) to derive the service and/or information request lQ n (28) therefrom. The service and/or information request lQ n (28) has information and/or elements, which may be used by the server PS (18) to make the requests Q n ι...Q n m (29) ofthe servers S>|...S Z (20), in accordance with the designation scheme which designates the ones ofthe servers Sι...S z (20) to be communicated with corresponding to the requests Qii...Q n m (29) as the corresponding server designations Sιι...S nm (30). The client C n (16) may additionally and/or alternatively make the requests Q n ι...Q n m (29) ofthe servers S.|...S Z (20), using information and/or elements within the user service and/or information request iq n (27). Now, again, each ofthe users (12) communicate the corresponding user service and/or information requests iq^.-iqn (27) therethrough the corresponding user interfaces lι...l n (14) to the corresponding clients C|...C n (16), which optionally format the corresponding user service and/or information requests iq^.-.iqn (27) into the corresponding service and/or information requests lQι...IQ n (28), as required. The user service and/or information requests iqι...iq n (27) may be communicated as the elements, values, field names, optional instructions, and or alternate requests entered thereinto the completed service and/or information entry request form lF n or other suitable means therefrom the corresponding user interfaces lι..-l n (14) to the corresponding clients Cι...C n (16). The users Uι...U n (12) may, thus, communicate the corresponding user service and/or information requests iq n ...iq n (27) to the clients Ci ...C n (16) therethrough the user interfaces ...I n (14), upon entering the corresponding user inputs UI<|...UI n (25) thereinto the corresponding service and or infonnation entry request forms IE<ι...IE n (38) at the corresponding the user interfaces lι...l n (14). The completed service and/or information entry request forms IF-|...IF n are derived therefrom the user inputs UI.|...UI n (25) having the corresponding user service and/or information requests iq 1 ...iq n (27), which may be entered as values or alternate requests thereinto the corresponding service and or information entry request forms IEι ...IE n (38). The user U<ι...U n (12) may alternatively communicate the user service and/or infonnation requests iq^. qn (27) by entering the alternate request links QLn...QL na (203) or the server request links UL|i...UL ns (204) or the additional request links SLn...SL nw (71 ) thereinto the service and/or information entry request form IE<]...lE n (38) or thereinto the completed service and/or information request form IF.) ...IF n (230). The server PS (18) and or the C n (16) may alternatively and/or additionally use infonnation resident within the server PS (18) and/or the client C n (16), such as default information, and/or information communicated therefrom the user U n (12) therethrough the user interface l n (14) to the client C n (16) to make the requests Q n ...Q n m (29) of the servers S^.-S z (20), in accordance with the designation scheme which designates the ones ofthe servers S.|...S Z (20) to be communicated with corresponding to the requests Qn...Q nm (29) as the corresponding server designations Sιι...S nm (30). FIG. 23 is a schematic representation showing queries QQ n ι...QQ nm (53) and corresponding server addresses AQ n1 ...AQ nm (54). D. OPTIONAL INSTRUCTIONS Now, in yet more detail, the user inputs UI 1 ...UI n (25) may have one or more ofthe same and/or different optional instruction values W 11 ... W nv . The optional instruction values Wι 1 ... W πv may typically have instructions, which may be used by the server PS (18) and/or the clients Ci ...C n (16), such as, for example, as instructions on how to request, organize, present and/or display, and/or retrieve services and/or mformation from the servers Sι...S z (20) and/or other suitable instructions. E. COMMUNICATING THE SERVICE AND/OR INFORMATION REQUESTS Now, each ofthe users U^-.U,, (12) communicate the corresponding user service and/or information requests iq 1 ...iq n (27) therethrough the corresponding user interfaces lι...l n (14) to the corresponding clients C^.-Cn (16), which optionally format the corresponding user service and/or information requests iq<|...iq n (27) into the corresponding service and/or information requests lQ-|...IQ n (28). The clients Cι...C n (16) communicate the corresponding service and/or information requests IQ^.-lOn (28) thereto the server PS (18) and/or use the corresponding user service and/or information requests iq^.jqn (27) internally to formulate the requests Qn-.-Onm (29). F. PARSING, PROCESSING, AND/OR FORMATTING THE SERVICE AND/OR INFORMATION REQUESTS The server PS (18) and/or the clients C 1 ...C n (16) parse, process, and/or format the service and/or information requests lQι...IQ n (28) into the requests Qιι...Q nm (29), the optional instructions VJιι...VJ nk (52), and information to open connections OCιι...OC nm (323). Upon receipt ofthe service and/or information requests IQ 1 ...IQ n (28) at the server PS (18), communicated therefrom the clients C^.-Cn (16), the server PS (18) parses, processes, and/or formats each ofthe corresponding service and/or information requests lQι...IQ n (28) into the corresponding queries QQn...QQ nm (53), the corresponding server addresses AQn^.AQnm (54) to open connections OC 11 ...OC πm (323) with and make the requests Qn...Q n m (29) thereof the servers Sι-..S Z (20), in accordance with the designation scheme which designates the certain ones ofthe servers Si ...S z (20) to be communicated with corresponding to the requests Qn.-.Qnm (29), and/or the optional instructions VJn... VJnk (52) to be used by the server PS (18) in making the requests Qn.-.Qnm (29) and/or in processing, formatting, grouping, and organizing the responses R- t ι...R nm (32) from the ones ofthe servers S< t ...S z (20) corresponding to the server designations Sn.--S nm (30), and/or the additional optional responses RAιι...RA nm (40), into the corresponding service and/or information responses IRi .. JR n (34), as shown in FIG. 86. Alternatively and/or additionally, upon receipt ofthe user service and or information requests iq^.jqn (27) at the corresponding clients Cι...C n (16), the corresponding clients C|...Cn (16) may parse, process, and/or format each o the user service and/or information requests iq^-.iqn (27) into corresponding queries QQn.-.QQnm (53), corresponding server addresses AQn...AQ nm (54) to open connections OCιι...OC nm (323) with and make the requests Qn...Q nm (29) thereof the servers Sι...S z (20), in accordance with the designation scheme which designates the certain ones ofthe servers Si ...S z (20) to be communicated with corresponding to the requests Qιι...Q nm (29), and/or the optional instructions VJn...VJn k (52) to be used by the corresponding clients C|...Cn (16) in making the requests Qn...Q nm (29) and/or in processing, formatting, grouping, and organizing the responses Rιι...R nm (32) from the ones ofthe servers Sv-S z (20) corresponding to the server designations Sιι...S πm (30), and/or the additional optional responses RA^-.-RAnm (40), into the corresponding user service and/or information responses irι...ir n (36). The server PS (18) parses, processes, and/or formats each ofthe service and/or information requests IQι...lQ n (28) into queries, server addresses to make the queries of, query groups and/or server groups, and instructions to be used by the server PS (18), typically when the server PS (18) makes the requests Qιι...Q nm (29) ofthe servers S<|...S Z (20) corresponding to the server designations Sιι...S nm (30) and/or the server PS (18) processes, formats, groups, and organizes the responses Rιι...R nm (32) from the ones ofthe servers S<|...S Z (20) corresponding to the server designations Sn...S nm (30) at the server PS (18). Otherwise, the clients C|...Cn (16) may parse, process, and/or format each ofthe user service and/or information requests iq 1 ...iq n (27) into queries, server addresses to make the queries of, query groups and or server groups, and instructions, typically when the clients C^-.Cn (16) make the requests Q<π...Q nm (29) ofthe servers S<|...S Z (20) corresponding to the server designations Sιι...S nm (30) and/or the clients C t ...C n (16) process, format, group, and organize the responses Rιι...R nm (32) from the ones ofthe servers Sι-..S Z (20) corresponding to the server designations Sιι...S nm (30) at the corresponding clients C^-.Cn (16). Choice as to whether the server PS (18) and or the clients C^.-C n (16) makes the requests Qn...Q nm (29) of the servers Si ...S z (20) corresponding to the server designations S-π . - .S nm (30) and/or process, format, group, and organize the responses R.ιι...R nm (32) are dependent on processing capabilities ofthe server PS (18) and/or the clients Ci ...C n (16) and other factors. Ones ofthe requests Qn.-.Q nm (29) may require further formatting and/or processing by the server PS (18) and/or the corresponding clients C|...C n (16), and or other ones ofthe requests Qn.-.Qnm (29) may already be formatted in accordance with requirements with respect to communications protocols, the service and/or information requests IQ 1 ...lQ n (28), the servers S.,...S Z (20), and/or the optional servers SO.,...SO p (22), and/or the server PS (18), and or other requirements ofthe network 24 ofthe client-server multitasking system 10. The server PS (18) and/or the clients (16) parse, process, and/or format the requests Qn...Q nm (29), as required. G. FORMULATING THE REQUESTS Each ofthe optional instructions VJ 11 ...VJ πk (52) is typically parsed, and/or processed, and/or formatted, and/or grouped, and/or organized into particular ones ofthe optional instructions VJ n ι...VJ nk (52) for use by the server PS (18) and or particular ones ofthe clients Cι...C n (16), a particular one ofthe clients C|...Cn (16) being designated as the client C n (16). The additional request links SL n1 ...SL πw (71 ) allow the user U n (12) to make additional optional selections, based upon infonnation and/or services previously requested by the user U n (12). FIG. 24 is a schematic representation of queries QQ n ...QQ nm , corresponding server addresses AQ n1 ...AQ nm , and optional instructions VJ nm i...VJ nk that may be parsed, processed, and/or formatted from the service and/or information request IQ n and/or the user service and/or information request iq n , shows a schematic representation of a typical one ofthe optional service and/or information entry request form IE n , and is schematically representational of a typical user interface l n , Typical ones ofthe optional instructions VJ n ...VJ nk (52) and the additional request links SL n1 ...SL nw (71) that may be parsed, processed, and/or formatted from the service and/or information request lQ n (28) and/or the user service and/or information request iq n (27) are shown in FIG. 24. The requests Qιι...Q nm (29) may be made by the server PS (18) and or the corresponding clients C|...C n (16) of the associated corresponding ones ofthe servers Si ...S z (20), according to the designation scheme corresponding to the corresponding ones ofthe server designations Sιι...S nm (30), in accordance with the optional instructions VJ 1 ι...VJn k (52) and/or default values for the optional instructions VJn...VJ nk (52) resident within the server PS (18) and or the corresponding clients C-i ...C n (16). The service and/or information responses IR 1 ...IR„ (34) and/or the corresponding user service and/or information responses irι...ir n (36) may be formulated by the server PS (18) and or the corresponding clients C|...Cn (16), in accordance with the optional instructions VJ 1 ι...VJ nk (52) and/or default values for the optional instructions Jιι... Jn (52) resident within the server PS (18) and/or the corresponding clients C^.-Cn (16). The optional instructions VJ n i... J nk (52) and the additional request links SLn...SL nw (71) for a particular one of the service and or information requests IQ n (28) may typically have Searches per Group 326, and/or Group 327, and/or Page 328A and/or Page 328B, and/or Timeout per Search Engine 329, and/or URL's per Search Engine 330, and or Search Engine Results 331 A and/or Search Display 331 B, and/or URL Details 332A and/or Description and/or List 332B, as shown in FIG. 24. Default values may additionally and/or alternatively be established or be resident for any and/or all ofthe optional instructions VJιι„.VJ nk (52) within the server PS (18) and/or the clients C^.-Cn (16). The Searches per Group 326 are typically considered to be the number ofthe queries QQ n1 ...QQ nm (53) to make of the servers Sι...S z (20) thereof at the corresponding server addresses AQ n1 ...AQ nm (54), in accordance with the designation scheme which designates the certain ones ofthe servers Sι...S z (20) to make the requests Q n ι...Q n m (29) thereof as the corresponding ones ofthe server designations S n1 ...S n (30). The Group 327 is considered to be the group ofthe queries QQ π ι - - -QQnm (53) to make ofthe servers Si ...S z (20) thereof at the corresponding server addresses AQ n1 ...AQ nm (54), in accordance with the designation scheme which designates the certain ones ofthe servers S<|...S Z (20) to make the requests Q n1 ...Q nm (29) thereof as the corresponding ones ofthe server designations S n ι...S nm (30). The Page 328A and the Page 328B have certain service and/or information location information, which may be incorporated into the requests Q n ι...Q n m (29) to be made ofthe associated corresponding ones ofthe servers S^.-Sz (20) thereof, at the corresponding server addresses AQ n1 ...AQ nm (54), in accordance with the designation scheme corresponding to the corresponding ones ofthe server designations S n ι...S nm (30). The Timeout per Search Engine 329 is considered to be substantially the maximum time for the server PS (18) and/or the particular client C n (16) making the requests Q n ι...Q n m (29) to wait for each ofthe responses R n ι...R nm (32) therefrom certain ones ofthe servers S<ι...S z (20), in accordance with the designation scheme which designates the certain ones ofthe servers Sι...S z (20) to be communicated with corresponding to the requests Q n ι...Q n m (29) as the corresponding server designations S n i...S nm (30). The URL's per Search Engine 330, is considered to be the number of links, and/or descriptions, and/or prices/values, and/or images to be returned to the user interface l n (14) from each ofthe responses R n ι...R n m (32). ' The Search Engine Results 331 A and the Search Display 331 B each designate presentation and/or display schemes to be presented at the user interface l n (14). The URL Details 332A and the Description and/or List 332B each also designate presentation and/or display schemes to be presented at the user interface l n (14). FIG. 25 is a schematic representation of certain typical optional instructions VJ n ι---VJn k (52) and or certain additional request links SL n1 ...SL nw (71), referred to as the Search Engine Results 331A, which are shown to be Interleave 331A-1, Separate 331A-2, Combine $[a-z] 331A-3, Combine $[z-a] 331 A-4, Separate $[a-z] 331A-5, Separate $[z-a] 331 A-6, which are instructions for parsing, processing, sorting, and/or formatting the service and/or information response IR n (34). FIG. 26 is a schematic representation of other certain typical optional instructions VJ nm ι---VJ nk (52) and/or other certain additional request links SL n1 ...SL nw (71), referred to as the URL Details 332A, which are other instructions for parsing, processing, sorting, and/or formatting the service and or information response IR n (34) in Summary 332A-1 or List 332A-2 formats. FIG. 27 depicts certain typical additional request links SL n ι - . -SL nw (71 ), and also shows the Search Display 331 B, which are shown to be Interleave 331 B-1 , Separate 331 B-2, Combine $[a-z] 331 B-3, Combine $[z-a] 331 B-4, Separate $[a-z] 331 B-5, Separate $[z-a] 331 B-6, which are instructions for parsing, processing, sorting, and or formatting the service and/or information response IR n (34) and the Description and/or List 332 B ,which are other instructions for parsing, processing, isorting, and or formatting the service and/or information response IR n (34) in Summary or List formats. The optional instructions VJ n ι...VJ nk (52) may also typically have Next Group 333 and Previous Group 334, which are considered to be the next group and the previous group, respectively, to make the queries QQ n ι--.QQ m (53) thereof at the next and previous ones ofthe corresponding groups ofthe queries QQ n ι...QQ nm (53) to make of the servers S>|...S Z (20) thereof at the corresponding server addresses AQ n1 ...AQ nm (54), in accordance with the designation scheme which designates the certain ones ofthe servers Sι...S z (20) to make the requests Q n i...Q n (29) thereof as the corresponding ones ofthe server designations S n ι...S nm (30). Information about Current Group 337 having the queries QQ n1 ...QQ nm (53) and the server addresses AQ n1 ...AQ nm (54) is also shown. Current Page Number 338 is also indicated. The optional instructions VJ n ι...VJ nk (52) for a particular one ofthe service and or information requests IQ n (28) may also typically have Next Page 335 and Previous Page 336, each of which has certain different service and/or information location information, which may be incorporated into the requests Q n ι...Q n m (29) to be made ofthe associated corresponding ones ofthe servers S^.-Sz (20), in accordance with the designation scheme corresponding to the corresponding ones ofthe server designations S n ι...S n m (30). H. DETERMINING QUERIES AND SERVERS TO MAKE THE REQUESTS THEREOF The server PS (18) and/or the clients C- ! ...C n (16) evaluate the optional instructions VJn.-. Jn (52), determine the queries QQn...QQ n (53) and the servers S-|...S Z (20) to make the requests Qιι...Q nm (29) thereof at the corresponding server addresses AQ 1 ...AQ nm (54), in accordance with the designation scheme which designates the certain ones ofthe servers S^.-S z (20) to be communicated with as the server designations Sιι...S nm (30), corresponding to the requests Qn...Q nm (29), and group the queries QQii...QQ nm (53) and the corresponding server addresses AQn ...AQ nm (54) associated therewith. FIG. 24 shows typical ones ofthe queries QQ n1 ...QQ nm (53), the corresponding server addresses AQ n1 ...AQ nm (54), and the optional instructions VJ n ι - - - VJ nk (52) that may be parsed, processed, grouped, sorted, and/or formatted from the service and/or information request lQ n (28) and/or the user service and/or information request iq„ (27). The queries QQn...QQ nm (53) and the servers S^-.Sz (20) to make the requests Q^...Q nm (29) thereof are typically based upon the values designated therein and parsed from the queries QQ 1 ...QQ nm (53) and the values designated therein and parsed from the corresponding server addresses AQ.) 1 ... AQ nm (54), in accordance with the designation scheme which designates the certain ones ofthe servers Sι...S z (20) to be communicated with as the server designations Sιι...S nm (30), corresponding to the requests Qιι...Q nm (29), and the Searches per Group 326, the Group 327, the Page 328A and/or the Page 328B within the optional instructions VJn-.VJn k (52). The server PS (18) and/or the clients Cι...C n (16) evaluate the values therein the Group 327, the Searches per Group 326, the queries QQn.-.QQnm (53), the corresponding server addresses AQ 11 ...AQ nm (54), and determine the servers S-ι...S z (20) corresponding to the corresponding server addresses AQn.-.AQnm (54) within the Group 327, in accordance with the designation scheme which designates the certain ones ofthe servers S<]...S Z (20) to be communicated with as the server designations S^.-.Snm (30) to make the requests Qιι...Q nm (29) thereof, and the Page 328A and/or the Page 328B. The Group 327 and the Searches per Group 326 are used to determine which ofthe servers S>|.--S z (20) to make the requests Qιι...Q nm (29) thereof. The server PS (18) and/or the clients C^-C n (16) determine the size ofthe Group 327 from the Searches per Group 326 and the Group 327, and the servers S-i ...S z (20) associated with the corresponding server addresses AQn...AQnm (54) within the Group 327, in accordance with the designation scheme which designates the certain ones ofthe servers S< t ...S z (20) to be communicated with as the server designations Sn...S n (30). The Searches per Group 326 and the Group 327 are used to formulate the current request groups QA 1c ...QA n c (50) having the corresponding queries QQn.-.QQnm (53) and the corresponding server addresses AQi-|...AQ nm (54) to open connections with and make the requests Qιι...Q n m (29) thereof the servers Sι...S z (20), in accordance with the designation scheme which designates the certain ones ofthe servers S.|...S Z (20) to be communicated with corresponding to the requests Qιι...Q nm (29) thereof as the server designations Sιι...S n (30), corresponding to the requests Qιι...Q nm (29), for corresponding ones ofthe service and/or information requests IQ<|...lQ n (28) and/or the user service and/or information requests iq-|...iq n (27). The queries QQιι...QQ nm (53), the server addresses AQn.-.AQnm (54), and the Page 328A and/or the Page 328B provide tlie location of information and or services to the server PS (18) and/or the clients C^.-Cn (16) within the Group 327, in accordance with the Searches per Group 326, to make the requests Qιι...Q nm (29) thereof, in accordance with the designation scheme which designates the ones ofthe servers S<i...S z (20) to make the requests Qii...Q nm (29) thereof as the server designations Sιι...S nm (30), corresponding to the requests Qιι...Q nm (29). The URL's per Search Engine 330 determine whether the server PS (18) and or the clients C| ...C n (16) communicate additional ones ofthe requests Qιι...Q nm (29) ofthe servers S^.-Sz (20), depending upon the number ofthe links, and/or descriptions, and/or prices/values, and/or images requested by ones ofthe user U^-.-Un (12) to be returned to the user interfaces l-|...l n (14), and the number of links, and/or descriptions, and/or prices/values, and/or images available within each ofthe corresponding ones ofthe responses Rιι...R nm (32). If insufficient ones ofthe links, and/or descriptions, and/or prices/values, and/or images are not available within the responses Rιι...R nm (32) to satisfy delivery ofthe number ofthe URL's per Search Engine 330 requested by certain ones the users U<ι...U n (12), the server PS (18) and/or the clients C|...Cn (16) may yet make additional ones ofthe requests Qιι...Q nm (29) ofthe servers S^-.S z (20), in order deliver the number ofthe links, and/or descriptions, and/or prices/values, and/or images requested in the number ofthe URL's per Search Engine 330 to the user interfaces l -..l n (14) requested by certain ones ofthe user U^.-Un (12). If the optional instructions do not indicate which ones ofthe servers S<ι...S z (20) to make the requests Qii...Q nm (29) thereof, in accordance with the designation scheme which designates the certain ones ofthe servers Sι...S z (20) to be communicated with as the server designations Sιι...S nm (30), corresponding to the requests Qιι...Q nm (29), default values may be used. The default values may be resident within the server PS (18) and/or the clients &,...(:„ (16). If all and or a portion of the optional instructions VJ 11 ... VJ nk (52) are absent and/or are not communicated thereto the server PS (18) and/or the clients Cι...C n (16), default values may be used. The default values may be resident within the server PS (18) and/or the clients C, ...C n (16). I. GROUPING THE QUERIES AND SORTING/GROUPING CRITERIA Upon receipt ofthe service and or information requests IQi ...IQ n (28) at the server PS (18), communicated therefrom the corresponding clients C 1 ...C n (16), the server PS (18) parses, processes, and/or formats each ofthe service and/or information requests lQι...lQ n (28) into the corresponding current request groups QA 1c ...QA nc (50) having the corresponding queries QQ<| < t ... QQ nm (53) and the corresponding server addresses AQi 1 ... AQ nm (54) to open connections with and make the requests Qιι...Q nm (29) thereof the servers S<|...S Z (20), in accordance with the designation scheme which designates the certain ones ofthe servers S-|...S Z (20) to be communicated with corresponding to the requests Qιι...Q nm (29) as the corresponding server designations S-n.-.Snm (30), shown for a particular one ofthe service and/or information requests lQ n (28) in FIG. 11. The process 104 of deriving the service and or information response lR n (34) for the grouping and/or sorting criteria of FIG. 11 is shown in FIG. 22- lA. The server PS (18) also parses, processes, and/or formats each ofthe service and/or information requests lQi-..IQ n (28) into the corresponding request groups QAιι.--QA nz (51) having the corresponding other queries QQ 1a .--QQ n z (55) and the corresponding other server addresses AQ 1a ...AQ πz (56), and the corresponding optional instructions VJ 11 ...VJ nk (52), also shown for a particular one ofthe service and/or information requests IQ n (28) in FIG. 11. Certain ones ofthe clients C.)...C n (16) may alternatively and/or additionally make the requests Q^.-.Qnm (29) thereof the servers Sι...S z (20), in accordance with the designation scheme which designates the certain ones ofthe servers S-|...S Z (20) to be communicated with corresponding to the requests Q^...Q n (29) as the corresponding server designations Sιι...S nm (30), and formulate the correspondmg user service and/or information response irι...ir n (36), as previously described, as shown in FIG. 15. The process 104 of deriving the user service and/or information response ir n (36) for the grouping and or sorting criteria of FIG. 11 is shown in FIG. 22-lA. Upon receipt of the user service and/or information requests iq 1 ...iq n (27) at the corresponding clients Cι...C n (16), certain ones ofthe corresponding clients C-|...C π (16) may parse, process, and/or format the corresponding user service and/or information requests iq^-.iqn (27) into the corresponding current request groups QAι c -.-QA nc (50) having the corresponding queries QQ^.-QOnm (53) and the corresponding server addresses AQιι...AQ nm (54) to open connections with and make the requests Qιι...Q nm (29) thereof the servers S.|...S Z (20), in accordance with the designation scheme which designates the certain ones ofthe servers S.|...S Z (20) to be communicated with corresponding to the requests Qιι...Q nm (29), shown for a particular one ofthe user service and/or information requests iq n (27) in FIG. 15. The corresponding clients C t ...C n (16) may also parse, process, and/or format the corresponding user service and/or information response ir^.-irn (36) into the corresponding request groups QAn...QA nz (51) having the corresponding other queries QQ 1a ...QQ nz (55) and the corresponding other server addresses AQ 1a ...AQ nz (56), and the corresponding optional instructions VJn...VJ n (52), also shown for a particular one ofthe user service and/or information requests iq n (27) in FIG. 15. The server PS (18) makes the requests Qn.-.Qnm (29) thereof the servers Sι...S z (20), in accordance with the designation scheme which designates the certain ones ofthe servers S-|...S Z (20) to be communicated with corn responding to the requests Qn...Q n m (29) as the corresponding server designations S^.-.Snm (30), as shown in FIG. 11, and certain ones ofthe clients Cι...C n (16) may additionally and/or alternatively make the requests Qιι...Q nm (29) thereof the servers Sι...S z (20), in accordance with the designation scheme which designates the certain ones ofthe servers Sι...S z (20) to be communicated with corresponding to the requests Qii...Q n (29) as the corresponding server designations Sιι...S nm (30), as shown in FIG. 15. The Searches per Group 326 and the Group 327 are used to formulate the current request group QA nc (50) having the corresponding queries QQ n1 ...QQ nm (53) and the corresponding server addresses AQ n1 ...AQ nm (54) to open connections with and make the requests Q n ι...Q nm (29) thereof the servers S<|...S Z (20), in accordance with the designation scheme which designates the certain ones ofthe servers Sι...S z (20) to be communicated with corresponding to the requests Q n ι...Q n m (29) thereof as the server designations Sιι...S nm (30), corresponding to the requests Qn...Q nm (29), for the service and or information request lQ n (28) and/or the user service and/or information request iq n (27). Information from the current request group QA nc (50) having the correspondmg queries QQ n1 ...QQ nm (53) and the corresponding server addresses AQ n1 ...AQ nm (54) is formulated into the corresponding request pointer/address group QZ n (60) having the pointers/addresses PG n -..PG nz (61) associated therewith, as shown in FIGS. 11 and 15. Each ofthe pointers/addresses PG n ι...PG nz (61) are directed to point/address the corresponding addressable query pointer/address groups QG n ι .. -QG nz (62) associated therewith, which aid in obtaining services and/or information therefrom the certain ones ofthe addressable response information group s RG n1 ...RG nm (57) to be incorporated thereinto the query information groups Gl n1 ...GI nz (63). Ones ofthe addressable query information groups Gl n1 ...GI nz (63) may be associated therewith corresponding ones ofthe addressable query pointer/address groups QG n ι - - -QG nz (62). Each ofthe addressable query pointer/address groups QG n1 ...QG nz (62) associated with the service and/or information request lQ n has the pointers/addresses PP n ι ...PP πmr (64) directed to address/point services and/or information therein the addressable response information groups RG n ι - - - RG nm (57), based upon the grouping and/or sorting criteria. Information and/or services therein the addressable response infonnation groups RG n ι...RG nm (57) is addressed therewith the pointers/addresses PP n ιι---PP n mr (64) therefrom the query pointer/address groups QG n ...QG nz (62), and information and or services therefrom the addressable response information groups RG n ι...RG n m (57) is incorporated thereinto the addressable query information groups Gl π1 ...Gl nz (63) corresponding to the pointers/addresses PP n ιι...PP n mr (64), which are formulated by the addressable query pointer/address groups QG n ι---QG nz (62), in accordance with the grouping and/or sorting criteria. FIGS. 11 and 15 show the request pointer/address group QZ n (60), the addressable query pointer/address groups QG n1 ...QG nz (62), the pointers/addresses PP n n...PP n mr (64), associated ones ofthe addressable response information groups RG n1 ... RG nm (57), and the query information group Gl nz (63) associated therewith the query pointer/address group QG nz (62). FIGS. 11 and 15 show the rth pointers/addresses PP n r - --PPnmr (64), which point to the rth optional addressable pointer/address indices IN nmr ...IN nmr (81) ofthe corresponding rth individual infonnation groups LG n1r ...LG nrn r (80) ofthe addressable response information group s RG n1 ... RG nm (57) associated therewith the query pointer/address group QG nz (62) and the associated query information group Gl nz (63). FIG. 28 shows the request pointer/address group QZ n (60), a particular one ofthe addressable query pointer/address groups QG n1 ...QG nz (62), designated as the query pointer/address group QG nz (62), the pointers/addresses PPnn... PPnmr (64), associated ones ofthe addressable response information group s RG π ι-.. RG πm (57), and the query information group Gl nz (63) associated therewith the query pointer/address group QG nz (62). The addressable query pointer/address groups QG n ι ...QG nz (62) each have corresponding ones of query information groups Gl n ι---Gl nz (63) associated therewith. Each ofthe query information groups Gl n1 ...GI nz (63) have information and/or services therein, which are derived therefrom information and/or services obtained from the certain ones ofthe addressable response information groups RG n1 ...RG nm (57), which are addressed to provide such information therewith the aid ofthe corresponding pointers/addresses PP n ιι...PP n mr (64). Each ofthe pointers/addresses PP n ιι-.. PPnmr (64) are directed to point/address information and/or services therein the corresponding response infonnation groups RGni...RG nm (57) associated therewith, which the information and/or services incorporated into the ones ofthe query information groups Gl n1 ...GI nz (63) associated therewith the corresponding addressable query pointer/address groups QG n1 ...QG nz (62) is obtained therefrom. The addressable query pointer/address groups QG n ι .. -QG nz (62) may be used to aid in formulating the query information groups Gl n1 ...GI nz (63), having infonnation obtained the addressable response information group s RG nm (57), resulting from certain ones ofthe queries QQ n1 ...QQ nm (53) grouped one with the other and/or the associated ones ofthe corresponding server addresses AQ n1 ...AQ nm (54). The query information groups Gl n1 ...GI nz (63) may be presented thereto the user U n (12) therethrough the user interface l n (14). The addressable query pointer/address groups QG n - - -QG nz (62) may be derived therefrom query criteria in the optional instructions VJ 11 ...VJn k (52) and/or using default criteria resident within the server PS (18) and/or the client C n (16). Query grouping criteria giving the user U n (12) the ability to formulate the addressable query pointer/address groups QG n ι-..QG nz (62) may be incorporated thereinto the optional instructions VJ^.-.VJn k (52), which may be entered thereinto the user interface l n (14) therethrough the user input Ul n (25) by the user U n (12). Typically, however, the queries QQ n ι...QQ nm (53) having the same and/or substantially the same values are grouped one with the other therein individual ones ofthe addressable query pointer/address groups QG n1 ...QG πz (62). Default criteria may be resident within the server PS (18) and/or the client C n (16). The size ofthe request pointer/address group QZ n (60) and which particular ones ofthe queries QQ n ι---QQ n m (53) and the corresponding ones ofthe server addresses AQ n1 ...AQ nm (54) to use therein the requests Q n ι-..Qnm (29), and thus construction and/or formulation ofthe addressable query pointer/address groups QG n1 ...QG nz (62) to incorporate thereinto the particular request pointer/address group QZ n (60), and, thus, delivery of information therein the query information groups Gl n1 ...Gl nz (63) is determined by the current request groups QA 1c ...QA nc (50), which may be determined from the Group 327 and the Searches per Group 326, the queries QQ n1 ...QQ nm (53) and the corresponding ones ofthe server addresses AQ n1 ...AQ nm (54) therein. Certain ones ofthe queries QQ n ι...QQ nm (53) may be grouped one with the other in the addressable query pointer/address groups QG n1 ...QG nz (62), which have the certain ones ofthe queries QQ n ...QQ nm (53) and the corresponding ones ofthe server addresses AQ n .--AQ nm (54) associated therewith, and the corresponding pointers/addresses PP n n... PPnmr (64) associated therewith the certain ones ofthe queries QQ n ...QQ nm (53), the corresponding ones ofthe server addresses AQ n1 ...AQ nm (54), and certain ones of response information groups Typical sorting and/or grouping criteria, for example, may group certain ones ofthe queries QQ n1 ...QQ nm (53) having the same and/or substantially the same values grouped therein a particular one ofthe query information groups Gl nz ...GI nz (63), designated as the query infonnation group Gl nz (63). Alternatively and/or additionally, other typical sorting and/or grouping criteria, for example, may group certain ones ofthe server addresses AQ n1 ...AQ nm (54), having the same and/or substantially the same values grouped therein a particular one ofthe query information groups Gl nz ...GI nz (63), designated as the query information group Gl nz (63), as shown in FIG. 30. FIGS. 28-30 show the rth pointers/addresses PP ner (64), PP nrr (64), and PP nw r (64), which point to the rth optional addressable pointer/address indices IN ner (81 ), IN nr r (81 ), and IN nW r (81 ) ofthe corresponding rth individual information groups LG ner (80), LG nrr (80), and LG nwr (80) ofthe addressable response information group s RG ne (57), RG πr (57), and RG nw (57) associated therewith the query pointer/address group QG nz (62) and the associated query information group Gl nz (63). . Alternatively and/or additionally, the user U n (12) may select query grouping criteria, which simply provides information to the user interface l n (14), separately with respect to the individual server addresses AQ n1 ...AQ nm (54), as shown in FIGS. 12 and 16. For example, the query information groups Gl n1 ...GI nz (63), may alternatively and or additionally be correspondingly associated with the server address AQ n1 ...AQ nm (54), and, thus, may be correspondingly associated with the addressable response information group s RG n ι ...RG nm (57). The query information group Gl n ι (63) may, thus, be associated therewith the server address AQ n ι (54), the addressable response information group RG n (57), and the query information group Gl n ι (63); the query information group Gl n2 (63) may, thus, be associated therewith the server address AQ n2 (54), the addressable response information group RG n2 (57), and the query information group Gl n2 (63), and so on; and the query information group Gl nz (63) may, thus, be associated therewith the server address AQ nz (54), the addressable response information group RG n2 (57), and the query information group Gl nz (63), as shown in FIGS. 12 and 16. The process 104 of deriving the service and/or information response IR n (34) and or the user service and/or information response ir n (36) for the grouping and/or sorting criteria of FIGS. 12 and 16 is shown in FIG. 22-lB. The pointing/addressing scheme of FIGS. 12 and 16 is, of course, a much simpler pointing/addressing scheme than the pointing/addressing scheme of FIGS. 11 and 15, and does not require incorporating the addressable query pointer/address groups QG n ...QG nz (62) thereinto the request pointer/address group QZ n (60). Each ofthe pointers/addresses PF n ιι...PF nmr (69), of FIGS. 12 and 16, may then be directed to point/address the corresponding response information groups RG n ι . - -RG nm (57) directly therefrom the request pointer/address group QY ns (68), to obtain information therefrom the corresponding response information groups RG n1 ...RG nm (57) and incorporation thereinto corresponding ones ofthe corresponding query information groups Gl n1 ...GI nz (63), as shown in FIGS. 12 and 16. In this case, the addressable queiy pointer/address groups QG n1 ...QG nz (62) may be bypassed and/or eliminated completely, thus simplifying the process. Of course, then, in this case, the resulting sorting and grouping is not as sophisticated, and allows for such simplification. The above sorting criteria addressing schemes are meant only as typical examples of sorting criteria addressing schemes that may be used. Yet other sorting criteria addressing schemes and/or combinations thereof may be used. FIG. 31 shows typical ones ofthe addressable query pointer/address groups QG n ...QG nz (62) having the typical ones ofthe queries QQ n1 ...QQ nm (53), the typical ones ofthe server addresses AQ n1 ...AQ nm (54), and the corresponding ones of typical ones ofthe pointers/addresses PP n n...PP n mr (64) having the same ones ofthe queries QQ n1 ...QQ nm (53) grouped one with the other therein individual ones ofthe addressable query pointer/address groups QG n1 ...QG nz (62). More particularly, FIG. 31 shows the query pointer/address group QG n ι (62), the query pointer/address group QG n2 (62), and the query pointer/address group QG n3 (62). The query pointer/address group QG n ι (62) of FIG. 31 has the same ones ofthe queries QQ n (53), QQ n2 (53), QQ n3 (53), and QQ n g (53), the ones ofthe server addresses AQni (54), AQ n2 (54), AQ n3 (54), and AQ n9 (54), and the ones ofthe pointers/addresses PP n1r (64), PP n2r (64), PP n3 r (64), and PP n9 r (64) associated therewith. The query pointer/address group QG n2 (62) of FIG. 31 has the same ones ofthe queries QQ n (53) and QQ n (53), the ones ofthe server addresses AQ π4 (54) and AQ n (54) the ones ofthe pointer/addresses PP n r (64) and PP n7r (64) associated therewith. The query pointer/address group QG n3 (62) of FIG. 31 has the same ones ofthe query values QQ n5 (53), QQ n6 (53), and QQ n8 (53), the ones ofthe server addresses AQ n s (54), AQ n6 (54), and AQ n8 (54) and the ones ofthe pointers/addresses PP n s r (64), PP n 6r (64), and PP n _r (64) associated therewith. The addressable query pointer/address groups QG n1 ...QG nz (62), however, may alternatively and/or additionally be grouped, for example, by the server addresses AQ n ...AQ nm (54) and have the corresponding query values QQ n i---QQnm (53) associated therewith. Ones ofthe same and/or substantially the same ones ofthe server addresses AQ n1 ...AQ nm (54), for example, having the correspondmg queries QQ n ι...QQ nm (53) associated therewith may be used as the grouping criteria. FIG. 32 shows another schematic representation ofthe typical ones ofthe addressable query pointer/address groups 5 QGni ...QG nz (62) having the typical ones ofthe queries QQ n ι - - -QQ nm (53), the typical ones ofthe server addresses AQ n1 ...AQ nm (54), and the typical the ones ofthe pointer/addresses PP n 1 ...PP nm r (64) of FIG. 31 associated therewith. FIG. 33 is a generic schematic representation ofthe addressable query pointer/address groups QG n1 ...QG nz (62) 10 having the queries QQ n1 ...QQ πm (53), the server addresses AQ n1 ...AQ nm (54), and the pointers/addresses PP n -.. PPnmr (64) associated therewith. Certain information therein the addressable response information groups RG n ...RG nm (57) may be associated with the corresponding queries QQ n1 ...QQ nm (53) and/or the corresponding server addresses AQ n1 ...AQ nm (54) within 15 the current request group QA nc (50), and may optionally be used by the server PS (18) and/or the client C n (16). Certain information therein the addressable response infonnation groups RGni...RG nm (57) may also be incorporated thereinto the optional instructions VJ n . - -VJ nk (52). Such information may be incorporated thereinto the optional instructions VJ n ι...VJ nk (52) may also be additionally and/or alternatively optionally resident within 20 the server PS (18) and/or the client C n (16). J. COMMUNICATING THE REQUESTS TO THE SERVERS The server PS (18) and/or the clients Cι...C n (16) contact and open the connections OC<ιι...OC nm (323) with ones ofthe servers Sι...S z (20), according to the server designations Sn.-.Snm (30) at the corresponding server 25 addresses An...A nu (265) at corresponding ports Wιι...W nm (343). The server PS (18) and/or the clients Cι..-C n (16) communicate the requests Qιι...Q n (29) of one or more ofthe same and/or different ones ofthe servers S.|...S Z (20), designated within the Group 327 and the Searches per Group 326 to make the requests Qn...Q nc (29) thereof, in accordance with the designation scheme corresponding to the corresponding ones ofthe server designations Sιι...S πm (30), corresponding to the requests Qιι...Q nm (29). If the Group 327 is not specified and/or 30 the Searches per Group 326 are not specified by the users U>|...U n (12), default values may additionally and/or alternatively values be used. A particular one ofthe requests Qιι...Q nm (29), hereinafter designated as the request Q nm (29), corresponding to one request within the requests Q n ...Q n m (29) corresponding to the user U n (12), is shown schematically in FIG. 35 34. Information 344 may be used for formulating a typical particular one ofthe requests Q nm (29) from the service and/or information request IQ n (28), and parsing, processing, and/or formatting the optional instructions VJ n ι..-VJn k (52), and opening the connection OC nm (323). Now, in more detail, the request Q nm (29) may have a corresponding request line L nm (345), corresponding optional request header fields JH n ι...JH ns (346), and a corresponding optional entity body EH nm (347). The request line L nm (345) may have a corresponding method M nm (348), a corresponding target resource P nm (349), which may have information associated with the corresponding query QQ nm (53), and corresponding protocol B πm (350). The user U n (12), the server PS (18) and/or the client C n (16) may optionally specify the port W nm (343) to communicate the request Q nm (29) therethrough, and/or the method M nm (348), and/or the protocol B nm (350). The port W nm (343), and/or the method M nm (348), and/or the protocol B nm (350) may optionally be resident within the server PS (18) and/or the client C n (16). Default values may also be used for the port W nm (343) and/or the protocol B nm (350). Typically, information within or from any and/or all or a portion ofthe queries QQ nm (53) may be incorporated into the corresponding ones ofthe target resources Pιι...P nm (349) and/or the corresponding ones ofthe optional entity bodies EHιι...EH nm (347), and may in certain instances depend upon the method 11 ...M nm (348). However, information that may be used for opening the connections OC 11 ...OC nm (323) and formulating the requests Qιι...Q nm (29) from the service and/or information requests iQv-IQn (28) may be derived from any and/or all or a portion ofthe user client requests QCn.-.QCn u (280) accessible to the users U<|...U n (12) and/or the hidden client requests HC n ι .. -HC nh (281 ) hidden from the users U ...U n (12), and or a combination thereof, and/or may also have infonnation and or instructions to be utilized by the server PS (18) and or ones ofthe clients Cι.--C n (16). Alternatively information from the alternate request links QLπ...QL na (203), and/or the server request links ULi-i...UL ns (204), and/or the additional request links SLπ...SL nw (71), and/or a combination thereof, may be used by the server PS (18) and/or ones ofthe clients C^-.Cn (16) to fonnulate the requests Qιι...Q nm (29). There may be m different or same ones ofthe requests Q n ι...Q n m (29) from the client C n (16) at any time, and n x m different and or same ones ofthe requests Qn.-.Q n m (29) ofthe same and/or different ones ofthe servers S<ι...S z (20) present on the network 24 at any time. The queries QQ n ι - - -QQnm (53) may each be different, one from the other, or the same. The queries QS n ι .. -QS nu (288) accessible to the user U n (12) may each be different, one from the other, or the same. The hidden queries QH n1 ...QH nh (290) may each be different, one from the other, or the same. The number ofthe queries QQ n ■ ■ -QQnm (53) " " may be substantially the sum ofthe queries QS n ι - - -QS nu (288) accessible to the user U n (12) and the hidden queries QH n1 ...QH nh (290), i.e., m = u + h. There may be m different or same ones ofthe queries QQ π1 ...QQ nm (53) corresponding to the requests Q n i...Q nm (29) from the client C n (16) at any time, and n x m different and or same ones ofthe queries QQ^.- ' QQnm (53) corresponding to the requests Qn...Q nm (29) ofthe same and or different ones ofthe servers S-|...S Z (20) present on the network 24 at any time. The server addresses AQ n1 ...AQ nm (54) may each be different, one from the other, or the same. The server addresses A n ι - - - A nu (265) accessible to the user U n (12) may each be different, one from the other, or the same. The hidden server addresses AH n ι - - ■ AH nn (291 ) may each be different, one from the other, or the same. The number ofthe server addresses AQ n1 ...AQ nm (54) "m" may be substantially the sum ofthe server addresses A n i...A nu (265) accessible to the user U n (12) and the hidden server addresses AH n ι...AH nh (291), i.e., m = u + h. There may be m different or same ones ofthe server addresses AQ n1 ...AQ nm (54) corresponding to the requests Q n i...Qnm (29) from the client C n (16) at any time, and n x m different and/or same ones ofthe server addresses AQ<n.--AQnm (54) corresponding to the requests Q-n.-.Qnm (29) ofthe same and/or different ones ofthe servers Si ...S z (20) present on the network 24 at any time. The optional instructions VJ n ι...VJ nk (52) may each be different, one from the other, or the same. The optional instructions V n ι...V nv (289) accessible to the user U n (12) may each be different, one from the other, or the same. The optional hidden instructions H n ι.-.H n i (292) may each be different, one from the other, or the same. The number ofthe optional instructions VJ n i-..VJ nk (52) "k" may be substantially the sum ofthe optional instructions V n ι---V nv (289) accessible to the user U n (12) and The optional hidden instructions H n ι...H n ι (292), i.e., k = v + i. There may be m x k different or same ones ofthe optional instructions VJ n ι-..VJ nk (52) corresponding to the requests Q n ι...Q n m (29) from the client C n (16) at any time, and n x m x k different and/or same ones ofthe optional instructions VJιι...VJ n (52) corresponding to the requests Qιι...Q nm (29) ofthe same and/or different ones ofthe servers Sι...S z (20) present on the network 24 at any time. [ The requests Qn...Q nm (29) ofthe servers Sι...S z (20) may be made at the same and/or different times. One or more ofthe requests Qn...Q n m (29) may be made of each ofthe servers S<]...S Z (20) by the same/and or different ones ofthe clients C^.-Cn (16) and/or the server PS (18) at the same and/or different times. The server PS (18) and/or the client C n (16) may make one or more ofthe requests Q n ι . - .Q nm (29) ofthe same and/or different ones ofthe servers Si ...S z (20), in accordance with the designation scheme corresponding to the corresponding ones ofthe server designations S n ι...S nm (30), in order to fulfill the services and/or information requirements ofthe user U n (12). K. REPLIES FROM THE SERVERS Each ofthe servers Si ...S z (20) communicated therewith replies to the server PS (18) and/or the clients C| ...C n (16), in accordance with the designation scheme which designates the servers S>|...S Z (20) being communicated with corresponding to the requests Qιι...Q nm (29) as the corresponding server designations Sιι...S nm (30), and communicates the corresponding responses R^-.-Rnm (32), associated therewith the requests Qιι...Q nm (29), to the server PS (18) and/or the clients Cv-Cn (16) making the requests Qιι...Q nm (29). Now, ones ofthe servers Sι...S z (20) having been contacted by the server PS (18) and/or the clients Cι...C n (16) and the connections opened OCu-.-OCnm (323) therewith, corresponding to the requests Qιι...Q nm (29), according to the server designations Sn...S nm (30) at the corresponding server addresses An...A nu (265) at the corresponding ports Wιι...W nm (343) reply to the server PS (18) and or the contacting clients Cι...C n (16) with the corresponding responses Rιι...R n (32). A particular one ofthe responses R n ι...R n m (32), hereinafter designated as the response R nm (32), corresponding to one response within the responses R n ι...R n m (32), the response R nm (32) corresponding to the request Q nm (29), and the responses R n ι...R n m (32) corresponding to the requests Q n ι...Q nm (29), is shown schematically in FIG. 35. Now, the response R nm (32) may have a corresponding response header line LR nm (351), corresponding optional response header fields JR n ι-..JR nt (352), and a corresponding optional entity body RH nm (353). The optional entity body RH n (353) typically has links, and/or descriptions, and or other information. The request header line LRnm (351) may have a corresponding protocol BR nm (354), a correspondmg status SR nm (355), and a corresponding status explanation SE nm (356). Ones ofthe connections may be closed after ones ofthe responses R^ ...R nm (32) are communicated to the PS (18) and/or to the requesting corresponding ones ofthe clients Cι...C n (16). Again, the Timeout per Search Engine 329 is considered to be substantially the maximum time for the server PS (18) and/or the particular client C n (16) making the requests Q n ι...Q n m (29) to wait for each ofthe responses R n ι...Rnm (32) therefrom certain ones ofthe servers S>|...S Z (20), in accordance with the designation scheme which designates the certain ones ofthe servers S .. ,S Z (20) to be communicated with corresponding to the requests Qιι...Q πrπ (29) as the corresponding server designations Sn...S n (30). If certain ones ofthe servers S.|...S Z (20) do not open connections OC 11 ...OC nm (323) therewith and/or communicate the responses Rιι...R nm (32) thereto the server PS (18) and/or the clients C-|...C n (16), and/or if certain other ones ofthe servers Sι...S z (20) do not communicate the responses Rn.-.Rn (32) thereto the server PS (18) and/or the clients C^-.Cn (16) once connections therewith may have been opened OC^.-OCnm (323), corresponding to the requests Qιι...Q nm (29), according to the server designations Sιι...S nm (30), within the timeout set by the Timeout per Search Engine 329, the certain ones of requests Qm ...Q nm (29) of such nonresponding ones ofthe servers S 1 ...S z (20) may then be cancelled by the server PS (18) and/or the clients Cv-Cn (16). Information about such ones ofthe nonresponding ones ofthe servers S-|...S Z (20) may then be communicated therefrom the server PS (18) and/or the clients Ci ...C n (16) therethrough the corresponding ones of the user interfaces lι...l n (14) thereto the corresponding ones ofthe users Ui...U n (12), according to the server designations Sιι...S nm (30) corresponding to the certain ones of requests Q n ...Q n m (29) of such nonresponding ones ofthe servers S.|...S Z (20). In certain instances, the server PS (18) and/or certain ones ofthe clients Cι...C n (16) may contact certain ones of the servers S-i...S z (20) and open the connections OCιι...OC nm (323) therewith, corresponding to the requests Qii...Q nm (29), according to the server designations Sιι...S nm (30), one or more additional times, in order to satisfy the needs ofthe users U<]...U n (12), and/or certain requirements within the optional instructions VJ n ι-..VJ nk (52), such as, for example, the URL's per Search Engine 330, and/or as a result of certain information communicated to the PS (18) and/or certain ones ofthe clients Ci...C n (16) within the responses Rιι...R nm (32). If, for example, less links, and/or descriptions, and/or prices/values, and/or images are returned within certain ones ofthe responses Rιι...R n (32), which may be considered to be first ones ofthe responses Rιι...R n m (32), than are requested by certain ones ofthe users U<|...U n (12) within certain ones of the URL's per Search Engine 330, the server PS (18) and/or certain ones ofthe clients Cι...C n (16) may contact certain ones ofthe servers S>|...S Z (20), open the connections OC 1 ι ...OC nm (323) therewith, and make additional ones of the requests Qιι...Q nm (29), according to the server designations Sιι...S nm (30), one or more additional times, in order to satisfy the needs ofthe users Uι...U n (12). The links, and/or the descriptions, and/or the images returned within and/or parsed therefrom additional ones ofthe responses Rιι...R nm (32) thereto the additional ones ofthe requests Qιι...Q n (29) may then be appended thereto the corresponding ones ofthe links, and/or the corresponding ones ofthe descriptions, and/or the corresponding ones ofthe images returned within and parsed therefrom the first ones ofthe responses Rιι...R nm (32) The servers S<]...S Z (20) communicate the responses Rιι...R nm (32) to the requests Qιι...Q nm (29) thereto the server PS (18) and/or specific ones ofthe clients Cι...C n (16), in accordance with the designation scheme corresponding to the corresponding ones ofthe server designations Sιι...S nm (30). Alternatively, and/or additionally, in certain instances, certain ones ofthe servers S<|...S Z (20), corresponding to certain ones ofthe server designations Sιι...S πm (30), may request additional information ofthe server PS (18) and/or specific ones ofthe clients C^-.Cn (16), prior to communicating the responses Rιι...R nm (32) to the requests Qn...Q nm (29). Upon receiving such additional information from the server PS (18) and/or the specific ones ofthe clients Cι...C n (16), the certain ones ofthe servers S 1 ...S Z (20), corresponding to the certain ones ofthe server designations Sιι.--S nm (30), may then communicate the responses Rn...R nm (32) to the requests Qn...Q nm (29) thereto the server PS (18) and/or the specific ones ofthe clients Cι...C n (16). In such certain instances, in more detail, the server PS (18) and/or certain ones ofthe clients (16) may contact certain ones ofthe servers S.]...S Z (20) and open the connections OCιι...OC nm (323) therewith, corresponding to the requests Q^...Q nm (29), according to the server designations Sn...S nm (30), one or more additional times, as a result of certain information communicated to the PS (18) and/or certain ones ofthe clients C^.-Cn (16) within the responses Rn...R nm (32), such as, for example, information obtained from and/or parsed from the responses Rn...R nm (32). This information is typically within certain ones ofthe response header fields JRιι„-JR nt (352), but may also be within the corresponding optional entity bodies RHιι...RH nm (353) and/or the corresponding response header lines LR^ ^ .LRnm (351). Now, in such certain instances, the certain ones ofthe servers S^...S Z (20) request the information from the server PS (18) and or certain ones ofthe clients C^-.C n (16), prior to communicating the responses Rn...R nm (32) thereto the server PS (18) and or the certain ones ofthe clients C-i ...C n (16). The server PS (18) and/or the certain ones ofthe clients C-i ...C n (16) being requested such information may then respond to the requests for such information, by communicating the requested information to the ones ofthe requesting servers S-|...S Z (20). Upon receipt ofthe requested information at the ones ofthe requesting servers S-|...S Z (20), the requesting ones ofthe servers Sι...S z (20) reply thereto the server PS (18) and/or the certain ones ofthe clients Cι...C n (16) with the responses Rιι...R nm (32). Such requests for information from the servers S>|...S Z (20) may occur not at all, and/or one or more times. L. PARSING, PROCESSING, FORMATTING, SORTING, GROUPING, AND ORGANIZING RESPONSES INTO SERVICE AND/OR INFORMATION RESPONSES A particular one ofthe optional entity bodies RH 1 ι...RH nm (353), designated as the entity body RH n m (353), of a particular one ofthe responses Rn.-.R n m (32), designated as the response R nm (32), may have optional response individual information groups LS n mi---LS n mr (360) and optional information Ll nm (361 ), as shown in FIG. 36. Each ofthe optional response individual information groups LS nm ι---LSnmr (360) may have and/or be parsed into corresponding optional response links LK nm1 ...LK nmr (362), and/or corresponding optional response descriptions DK nm1 ..-DK nmr (363), and or corresponding optional response prices/values PK n mi---PK n mr (364), and/or corresponding optional response images IK nm1 ...IK nmr (365), as shown in FIG. 36. The optional response links LK n mi---LK nm r (362), the corresponding optional response descriptions DK nm ι---DKnmr (363), the corresponding optional response prices/values PK n mi---PK n mr (364), and the corresponding optional response images IK n m ...lK n mr (365), corresponding to the optional response individual information groups LSnmi-.-LSnmr (360) are typically associated correspondingly one with the other. The optional response link LK nm ι (362), the corresponding optional response description DK nm ι (363), the corresponding optional response price/value PK nm ι (364), and the corresponding optional response image IK nm1 (365), corresponding to the optional response individual infonnation group LS nm ι (360) are typically associated correspondingly one with the other. The optional response link LK nm2 (362), the corresponding optional response description DK nm2 (363), the corresponding optional response price/value PK πm2 (364), and the corresponding optional response image IK nm2 (365), corresponding to the optional response individual information group LS nm2 (360) are typically associated correspondingly one with the other, and so on. The optional response link LK nm r (362), the corresponding optional response description DK nmr (363), the corresponding optional response price/value PK nm r (364), and the corresponding optional response image IK nm r (365), corresponding to the optional response individual information group LS nmr (360) are, thus, typically associated correspondingly one with the other. The optional information Ll nm (361) may have additional links, and/or additional descriptions, and/or additional images, and or prices/values, and or other information, and/or services, and/or media, all and/or a portion of which may be used and or discarded by the server PS (18) and/or the clients Cj ...C n (16). The optional information Ll n (361) is typically filtered from the optional entity body RH nm (353) and discarded, and/or other unwanted information and/or media is also typically filtered from the response R nm (32), and/or the optional entity body RH nm (353), and discarded. The optional response individual information groups LS n mi---LS n mr (360) are typically parsed and/or processed and/or formatted therefrom the entity body RH n m (353) ofthe response R nm (32), and/or parsed, and/or processed, and/or formatted, and/or organized, and/or grouped thereinto the addressable individual information groups LG n mi---LG nmr (80) ofthe addressable response information group RG nm (57), correspondingly associated therewith the response R πm (32), as shown in FIGS. 37 and 38. FIG. 37 shows the addressable response information group RG nm (57) having the addressable individual information groups LG nm ι..-LGnmr (80) parsed, and/or processed, and or formatted, and/or organized, and/or grouped thereinto the addressable response information group RG nm (57) therefrom the optional entity body RH nm (353) of FIG. 36. FIG. 38 shows a particular one ofthe optional response individual information groups LS n mi...LS n mr (360), designated as the optional response individual information group LS nm r (360), parsed, and/or processed, and/or formatted, and or organized, and/or grouped thereinto a particular one ofthe addressable individual information groups LGnmi ■■ -LGnmr (80), designated as the addressable individual information group LG nrnr (80). The addressable individual information groups LG nm ι---LG nmr (80) are typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other, as the addressable individual information groups LG nm i...LG n mr (80) are incorporated thereinto the addressable response information group s RGni-.-RGnm (57) therefrom the responses R n1 ...R nm (32). Alternatively and/or additionally the addressable individual information groups LG nm ...LG nmr (80) may be incorporated thereinto the addressable response information group s RG n ι...RG nm (57) therefrom the responses R n ι...Rnm (32) in an as-is condition and/or in raw form. The optional response links LK nm ...LK nmr (362) are typically parsed, and/or processed, and/or formatted thereinto the corresponding optional links LD nm ι...LD nmr (82). The optional response descriptions DK nm ι...DK nm r (363) are typically parsed, and/or processed, and or formatted thereinto the optional descriptions DD nm1 ...DD nmr (83). The optional response prices/values PK n mi-..PK n mr (364) are typically parsed, and/or processed, and/or formatted thereinto the corresponding optional prices/values PD nm ι---PDnm r (84). The optional response images IK nm ι...lKnmr (365) are typically parsed, and/or processed, and/or formatted thereinto the corresponding optional • images ID n mi--.ID nmr (85). Each ofthe optional links LD m1 ...LD mr (82) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other. Alternatively and/or additionally the optional links LD nm ι-- -LD nmr (82) may be retained in an as-is condition and/or in raw form. Each ofthe optional descriptions DD nm1 ...DD nmr (83) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other. Alternatively and/or additionally the optional links optional descriptions DD nm ...DD nmr (83) may be retained in an as-is condition and/or in raw form. Each ofthe optional prices/values PD nm ι ■ ■ -PD nm r (84) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other. Alternatively and/or additionally the optional prices/values PD nm ι...PD nm r (84) may be retained in an as-is condition and/or in raw form. Each ofthe optional images ID nm1 ...ID nmr (85) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other. Alternatively and/or additionally the optional images ID nm1 ...ID n m r (85) may be retained in an as-is condition and/or in raw form. The optional links LD n m ---LD n mr (82), and/or the optional descriptions DD nm1 ...DD nmr (83), and/or the optional prices/values PD nm ι---PDnmr (84), and/or the optional images ID nm ι---IDnmr (85), correspondingly associated therewith the response R nm (32), may additionally and/or alternatively be parsed individually and/or separately, and incorporated thereinto the addressable response information group RG nm (57) therefrom the optional entity body RHnm (353), as shown in FIG. 39. The response header line LR nm (351) and/or the optional response header fields JR n ...JR nt (352) may also have information, which the server PS (18) and/or the clients C|...Cn (16) may use. The optional information Ll nm (361 ) and or certain information and or media within the response R nm (32), particularly within the optional entity body RH nm (353), may be optionally used by the server PS (18) and/or the clients C ...C n (16), and/or optionally incorporated thereinto the addressable response information group RG nm (57). Each ofthe optional response individual information groups LS nm ι ■ ■ -LSnmr (360) therefrom each ofthe responses R n ..-Rnm (32) may be compared one with the other, and duplicate ones ofthe ofthe optional response individual information groups LS n mi---LS n mr (360) may be discarded. Alternatively and/or additionally, each ofthe optional addressable individual information groups LG n n...LG nmr (80) therefrom each ofthe addressable response information group s RG n ι...RG n m (57) may be compared one with the other, and duplicate ones ofthe optional addressable individual information groups LG n ι...LG nm r (80) may be discarded. Each ofthe optional response individual information groups LSnι...LS n mr (360) and/or portions thereof therefrom the entity bodies RHn...RH nm (353) ofthe responses Rιι...R n m (32) may also be optionally compared one with the other, and duplicate ones ofthe ofthe optional response individual information groups LSm.-.LSnmr (360) may be optionally discarded. Alternatively and or additionally, each ofthe optional links LK n11 ...LK nmr (362), and/or the optional descriptions DK n11 ...DK nmr (363), and/or the optional prices/values PD n mi---PD n mr (365), and/or the optional images IK n11 ...IK nmr (365), therefrom each ofthe responses R n ι...R n m (32) may be compared one with the other of like kind, and duplicate ones ofthe optional links LK n11 ...LK nmr (362), and/or the optional descriptions DK n ιι...DK n mr (363), and/or the optional prices/values PK nm ι...PK n mr (364), and or the optional images IK n ...IK nmr (364), and/or a combination thereof may be discarded. Alternatively and/or additionally, each ofthe optional links LD n1 ...LD nmr (82), and/or the optional descriptions DD n ιι---DD n mr (83), and/or the optional prices/values PD n mi---PD n mr (84), and/or the optional images ID n 1 ...ID nmr (85) therefrom each ofthe addressable response information group s RG n1 ...RG nm (57) may be compared one with the other of like kind, and duplicate ones ofthe optional links LD n11 ...LD nmr (82), and/or the optional descriptions DD n11 ...DD nmr (83), and/or the optional prices/values PD nm ---PDnmr (85), and/or the optional images ID n1 ...ID nmr (85), and/or a combination thereof may be discarded. The optional links LK n11 ...LK nmr (362) are typically compared one with the other, and duplicate ones ofthe corresponding optional links LK n 1 ...LK nmr (362), and or the correspondmg optional descriptions DK n ιι...DK n mr (363), and/or the corresponding optional images IK n ...IK nmr (364), and/or the corresponding optional prices/values PKnmi...P nmr (365) are discarded, leaving only one of any ones ofthe duplicate optional links LK n ---LKnmr (362) and/or the corresponding optional descriptions DK n11 ...DK nmr (363), and/or the corresponding optional images IK n11 ...IK nmr (364), and/or the optional prices/values PK nm ι---PKnmr (365) remaining. The optional prices/values PD nm ι...PD n mr (84) and or the corresponding optional links LD n ιι...LD n mr (82) and/or the corresponding optional descriptions DD n ...DD nmr (83), and/or the corresponding optional images ID π11 ...ID nmr (85) may be sorted with respect to the optional prices/values PD nm i---PDnmr (84), in accordance with sorting criteria in the optional instructions VJ n ι - ■ -VJ nk (52) and/or in accordance with default criteria resident within the server PS (18) and/or the client C n (16). The optional links LD n11 ...LD nm r (82), and/or the corresponding optional descriptions DD n 1 ...DD nmr (83), and/or the corresponding optional prices/values PD nm ι---PDnmr (84), and/or the corresponding optional images ID n11 ... IDn r (85) may be sorted, for example, in ascending order with respect to the optional prices/values PD nm -..PDnmr (84) having the lowest price therein being presented to the user U n (12) at the user interface l n (14) first and the highest price therein last. Alternatively and/or additionally, the optional links LD n11 ...LD nmr (82), and/or the corresponding optional descriptions DD n11 ...DD nmr (83), and/or the corresponding optional prices/values PD n mi---PD n mr (84), and/or the corresponding optional images ID n 1 ...ID nmr (85) may be sorted, for example, in ascending or descending alphabetical order with respect to the optional links LD n11 ...LD nmr (82) and/or the corresponding optional descriptions DD n 1 ...DD nmr (83) being presented to the user U n (12) at the user interface l n (14). Other sorting criteria may be used for the optional links LD n ...LD nmr (82), and/or the optional descriptions DD n11 ...DD nmr (83), and/or the optional prices/values PD nm ι---PDnmr (84), and/or the optional images ID n11 ... IDn r (85), and may depend upon needs ofthe user U n (12). The sorting criteria may be determined by the user U n (12). Sorting criteria gives the user U n (12) the ability to formulate how information is presented to the user U n (12) at the user U n (12), and may be incorporated thereinto the optional instructions VJ n ι . - -VJ„ k (52), which may be entered thereinto the user interface l n (14) therethrough the user input Ul n (25) by the user U n (12). The sorting criteria may additionally and/or alternatively be resident within the server PS (18) and/or the client C n (16). Now again, the labelled individual infonnation group LL nzu (86) associated therewith the addressable query information group Gl nz (63) has the optional group identifier GL πc (87), the optional query link identifier LN ncu (88), the optional resource location identifier SU nw (89), the optional server and/or query identifier Sl nm (90), and/or the optional server link identifier LX nmr (91 ) appended thereto the addressable mdividual information group LGnmr (80), as shown in FIG. 20. FIGS. 40 and 41 show typical ones ofthe addressable query information group Gl nz (63), based upon certain sorting and/or grouping criteria, having the labelled individual information groups LL nz ...LL nzu (86), the optional database labelled individual information groups RL nz ι.--RL nZ χ (92), the optional query description QT nz (93), the optional server descriptions and/or links ST πz ι ...ST nzf (94), and the optional advertisements and/or links LT nz ι...LT nz t (95) incorporated thereinto certain typical ones ofthe typical service and/or information response forms lS n (39). The client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, the server PS (18) and/or the clients Cι.--C n (16), then, are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information therefrom the same and/or different ones ofthe servers S^.-Sz (20), and/or the optional servers SO-|...SO p (22), and/or the clients C^-.Cn (16), having the same and/or different structures, formats, organizations, groupings, and or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information thereinto the user responses URι...UR n (37) for delivery to the user interfaces lι-..l n (14) and use by the users U^-.U n (12). The client-server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and the multitasking process 104, the server PS (18) and/or the clients Cι...C n (16), then, are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information therefrom the same and/or different ones of each ofthe optional response individual information groups LS-m... LSnmr (360), and/or the optional response links LKιι 1 ...LK nm r (362), and/or the optional response descriptions DKιιι...DK nm r (363), and/or the optional response prices/values PKιι 1 ...PK nm r (364), and/or the optional response images IK nm1 ...IK nmr (365) therefrom the entity bodies RHιι...RH nm (353) ofthe responses Rιι...R nm (32), having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information thereinto the user responses UR^-.URn (37) for delivery to the user interfaces lι...l n (14) and use by the users U- t ...U n (12). M. TYPICAL SERVICE AND/OR INFORMATION ENTRY REQUEST FORMS, TYPICAL COMPLETED SERVICE AND/OR INFORMATION ENTRY REQUEST FORMS, AND TYPICAL SERVICE AND/OR INFORMATION RESPONSE FORMS FIG. 42 shows a typical one of service and/or information entry request forms IE>ι...IE n (38) at the user interfaces lι...l n (14), which the users (25) thereinto, as requests for information and or services. The typical ones ofthe service and/or information entry request forms (38) at the user interfaces ...l π (14) shown in FIGS. 42 is a typical example one ofthe service and/or information entry request forms iE^.TEn (38) at the user interfaces lι...l n (14), a much larger variety of which is possible. Names and/or links and/or other information are incorporated therein the typical one ofthe service and/or information entry request forms IEι...IE n (38) shown in FIG. 42 are for illustrative purposes, and are not intended to limit the large variety ofthe service and/or information entry request forms lEi ...IE n (38) and the names and/or links and/or information that are possible, and that may be incorporated thereinto the service and/or information entry request forms lEι...IE n (38) at the user interfaces lι...l n (14). A particular one ofthe service and/or information entry request forms lEi ...IE n (38) may hereinafter be designated as the service and/or information entry request form IE n (38), at the particular user interface l n (14). FIG. 43 shows a typical particular one ofthe completed service and/or information entry request forms IFι...lF n (230), which may hereinafter be designated the completed service and/or information entry request form IF n (230), at a particular one ofthe user interfaces ...l n (14), which may hereinafter be designated the user interface l n (14), having same and different ones ofthe typical queries QQ n ι-..QQ n m (53), different ones ofthe typical server addresses AQ n1 ...AQ nm (54), and the typical optional instructions VJ n ι...VJ nk (52). Typical same ones ofthe typical queries QQ n1 ...QQ nm (53), are "Cat", "Dog", and "Mouse", which are different one from the other. FIGS. 44-46 show typical ones ofthe user responses URv--UR n (37), as typical service and/or information response forms ISι...lS n (39) at the user interfaces l-ι...l n (14), which may be communicated thereto the corresponding ones ofthe users U^-.Un (12). A typical particular one ofthe user responses UR^-.URn (37), as a particular typical one ofthe service and/or information response forms IS<|...IS n (39) at the particular one ofthe user interfaces lι...l n (14) may hereinafter be designated as the user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14). FIGS. 44-46 also show information therein each ofthe typical ones ofthe user responses UR n (37), as the typical service and/or information response forms lS n (39) at the user interface l n (14), pertaining to the "Current Group", the "Previous Group", if appropriate, the "Next Group", if appropriate, and each "Group" by alphanumerics. FIGS. 44-46 also show information therein each ofthe typical ones ofthe user responses UR n (37), as the typical service and/or information response forms lS n (39) at the user interfaces l n (14), pertaining to links to additional selections, and/or links to previous selections, if appropriate, and/or links to future selections, if appropriate, that may be made by pointing to and clicking on the selections to be made. FIGS. 44-46 show typical ones ofthe user responses UR n (37), as the typical service and/or information response forms IS n (39) at the user interface l n (14), with reference to FIG. 43, having information and/or services therefrom the responses R n ι...R n m (32) incorporated therein, and incorporated thereinto Group I, Group II, and Group III, respectively. The user U n (12) may optionally select Group II, and/or Group III therefrom the typical one ofthe user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14) of FIG. 44, and/or Group I and/or Group III at the user interface l n (14) of FIG. 45, and/or Group I, and/or Group II at the user interface l n (14) of FIG. 46. The user U n (12) may also select Group I, and/or Group II, and/or Group III by entering such into the typical one ofthe service and/or information entry request form IE n (38) at the user mterfaces I t ... In (14), and completing the typical completed service and/or information entry request form IF n (230), at the user interface l n (14) therewith the appropriate selections to be made. The user U n (12) may also make other selections by entering such into the typical one ofthe service and/or information entry request form IE n (38) at the user interfaces l ...l n (14), and completing the typical completed service and/or information entry request form IF n (230), at the user interface l n (14) therewith the appropriate selections to be made, and/or by making such selections therethrough the typical ones ofthe user responses UR n (37), as the typical service and/or information response forms lS n (39) at the user interface l π (14). The user U n (12) may typically make selections by pointing and clicking on the appropriate selections and/or by entering the desired information. Such information may be entered by any suitable means, including but not limited to mouse, keyboard entry, audible entry, and/or other suitable means. FIGS. 44-46 show typical ones ofthe user responses UR n (37), as the typical service and/or information response forms IS n (39) at the user interface l n (14), having the service and/or information group G n (35) having the addressable query information groups Gl n1 ...GI nz (63) therein, the labelled individual information groups LL n11 ...LL nzu (86) therein the addressable query information groups Gl n ...GI nz (63), the additional request links SL n1 ...SL nw (71), the optional service and/or information entry request form IE n (38), and other information and/or services therein, resulting from the same and different ones ofthe typical queries QQ n ι...QQ nm (53), different ones ofthe typical server addresses AQ n1 ...AQ nm (54), and the typical optional instructions VJ n i...VJ„ k (52). FIGS. 44-46 show typical ones ofthe user responses UR n (37), as the typical service and/or information response forms lS n (39) at the user interface l n (14), resulting from the typical ones ofthe queries QQ n1 ...QQ nm (53), "Cat", "Mouse", and "Dog", the same ones ofthe typical queries QQ n ι...QQ n3 (53) and QQ n e (53) being "Cat", other same ones ofthe typical queries QQ n (53) and QQ n (53) being "Mouse", but different from "Cat", and other same ones ofthe typical queries QQ n s, QQnβ (53), and QQ n s (53) being "Dog", but different from "Cat" and/or "Mouse", the typical ones ofthe queries QQ n1 ...QQ nm (53), "Cat", "Dog", and "Mouse", being different one from the other. The typical same ones ofthe typical queries QQ n ι .. -QQ n3 (53) as "Cat" are incorporated thereinto the addressable query information groups Gl n -ι (63) of Group I. The typical one ofthe queries QQ n (53) as "Mouse" is incorporated thereinto the addressable query information groups Gl n ι (63) of Group II. The other same ones ofthe typical queries QQ n s and QQ n6 (53) as "Dog are incorporated thereinto the addressable query information groups Gl n2 (63) of Group II. The typical one ofthe queries QQ n7 (53) as "Mouse" is incorporated thereinto the addressable query information groups Gl n ι (63) of Group III. The typical one ofthe queries QQ n s (53) as "Dog" is incorporated thereinto the addressable query information groups Gl n2 (63) of Group III. The typical one ofthe queries QQ n g (53) as "Cat" is incorporated thereinto the addressable query information groups Gl n3 (63) of Group III. FIGS. 44-46 show typical ones ofthe user responses UR n (37), as the typical service and/or information response forms IS n (39) at the user interface l n (14), with reference to FIG. 43 having: "Search Engine Results" as "Interleave"; "URL's per Search Engine" as "10"; "URL Details" as "Summary"; "Timeout (seconds) per Search Engine" as "3"; "Page" as "1"; "Searches per Group as "3"; and "Group" as I, II, and III, respectively, for FIGS. 44- 46. The typical optional instructions VJ n ι...VJ nk (52) "URL's per Search Engine" as "10" instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form IS n (39) at the user interface l n (14) having substantially "10" ones ofthe typical labelled individual information groups LL n11 ...LL nzu (86) per each one ofthe typical server addresses AQ n1 ...AQ nm (54) in the typical "Current Group", retrieved therefrom the responses R n i-..R n m (32). In this case, the typical labelled individual information groups LL n11 ...LL nzu (86) may be "Uniform Resource Locators", or "URL's" and/or other services and/or information associated therewith. The typical optional instructions VJ n ι...VJ nk (52) "Searches per Group" as "3" instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14) having "3 Searches per Group" for the group selected, which is designated in the typical optional instructions VJ n1 ... VJ„ k (52) having "Group" as "1". "Group I", which is the "Current Group: I", has the first three searches ("Searches per Group" designated as "3"), i.e., Search 1, Search 2, and Search 3, having the typical queries QQ n1 ...QQ n3 (53) of "Cat", "Cat", and "Cat" and the typical server addresses AQ n ι...AQ n3 (54) of "WebCrawler", "Altavista", and "Lycos". The "Next Group: II" and/or the "Group: III" may be selected therefrom the typical user response UR n (37), as the typical service and/or information response form IS n (39) at the user interface l n (14). If the "Next Group: II" is selected, then Search 4, Search 5, and Search 6, having the typical queries QQ n4 .--QQ n6 (53) of "Mouse", "Dog", and "Dog" and the typical server addresses AQ n4 ...AQ n6 (54) of "Infoseek", "Excite", and "Yahoo" are selected and returned as the typical service and/or information response form lS n (39) at the user interface l n (14). If the "Group: III" is selected, then Search 7, Search 8, and Search 9, having the typical queries QQ n7 ...QQ n9 (53) of "Mouse", "Dog", and "Cat" and the typical server addresses AQ n7 ...AQ n9 (54) of "LookSmart", "HotBot", and "Dejanews" are selected and returned as the typical service and/or infonnation response form lS n (39) at the user interface l n (14). The typical optional instructions VJ n ι...VJ nk (52) having "URL's per Search Engine" as "10" and "Searches per Group" as "3", then returns substantially "10 URL's per Search Engine" multiplied by "3 Searches per Group", which is substantially "30 URL's per Group", and/or other services and/or information associated therewith, returned therein the "Current Group". The actual number ofthe typical "URL's per Group" may vary from the number ofthe "URL's per Search Engine" multiplied by the number ofthe "Searches per Group", as duplicate ones ofthe "URL's" and or other services and/or information associated therewith may typically be optionally discarded. The typical optional instructions VJ n1 ...VJ nk (52) "Page" as "1" instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form IS n (39) at the user interface l n (14) having the first "10 URL's per Search Engine" which is substantially the first "30 URL's per Group", and or other services and/or information associated therewith, therein the "Current Group". The "Next Page" and/or other pages may be selected, which in this typical case may be Pages 1-25, therefrom the typical user response UR n (37), as the typical service and/or information response form IS n (39) at the user interface l n (14). If the "Next Page" is selected, then the nex 'lO URL's per Search Engine" which is substantially the next "30 URL's per Group", and or other services and/or information associated therewith, therein the "Current Group" are selected and returned as the typical service and/or information response form lS n (39) at the user interface l n (14). If, for example, the third "Page' is selected, then the third "10 URL's per Search Engine" which is substantially the third "30 URL's per Group", and/or other services and/or information associated therewith, therein the "Current Group" are selected and returned as the typical service and/or information response form lS n (39) at the user interface l n (14). The typical optional instructions VJ n i...VJ nk (52) of "Search Engine Results" as "Interleave" instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14) having ones ofthe typical labelled individual information groups LL n1 ι...LL nzu (86) and/or other services and/or information associated therewith the typical queries QQ n1 ...QQ nm (53) and the typical server addresses AQ n ι...AQ nm (54) in the typical "Current Group", portions of which have been retrieved therefrom the responses R n i...R nm (32), interleaved one with the other (or alternating one with the other) therein the appropriate addressable query infonnation groups Gl n1 ...GI nz (63). The "Interleaved" information and/or services may typically be incorporated therein the appropriate addressable query information groups Gl n1 ...GI nz (63) therein the "Current Group" in substantially the same sequence as the information and/or services are therein the responses R n ...R nm (32) communicated therefrom the servers S-|...S Z (20). However, other sorting/grouping criteria may optionally be used, as will be discussed later. In this case, the typical labelled individual infonnation groups LL n ιι...LL nZ u (86) may be "Uniform Resource Locators", or "URL's" and/or other services and/or information associated therewith. "Separate" may be selected therefrom the typical user response UR n (37), as the typical service and/or mformation response form IS n (39) at the user interface l n (14), which instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form IS n (39) at the user interface l n (14) in "Separate" groups, i.e., grouped by the typical server addresses AQ n1 ...AQ nm (54) incorporated therein the appropriate addressable query information groups Gl n1 ...GI nz (63) therein the "Current Group". The typical optional instructions VJ n ι.-.VJ nk (52) "URL Details" as "Summary" instruct the client C n (16) and/or the server PS (18) to return the typical user response UR π (37) showing the typical labelled individual information groups LL n11 ...LL nzu (86) showing descriptions and/or other information and/or services, in addition to links, and/or URL's therein the typical ones ofthe user responses UR n (37), as the typical service and/or information response forms IS n (39) at the user interface l n (14). "List" may be selected therefrom the typical user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14), which instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14) typically showing only links to URL's and/or other links therein the typical ones ofthe user responses UR π (37), as the typical service and/or information response forms IS n (39) at the user interface l n (14). The "Timeout (seconds) per Search Engine" instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form IS n (39) at the user interface l n (14) within a period of less than the "Timeout (seconds) per Search Engine" specified in the typical optional instructions VJ n ι ...VJ nk (52). It should be noted that response times of less than one second per search engine are typical, and response times of substantially less than one second are quite common. However, the "Timeout (seconds) per Search Engine" has been incorporated herein for the user Ui (12) to specify in the event of slow ones ofthe responses R n ι...R nm (32) from certain ones ofthe servers S.]...S Z (20). If the time it takes to retrieve information from certain ones ofthe servers Si ...S z (20) having the typical ones ofthe queries QQn ...QQ nm (53) at the typical ones ofthe server addresses AQ n1 ...AQ nm (54) is greater than the "Timeout" selected, then the client C n (16) and/or the server PS (18) typically incorporate a message and/or messages, such as "No Results Found for 'Query 'x" at 'Server Address 'y" within "z" seconds!" for each ofthe non-responding certain ones ofthe servers Sι...S z (20), as shown later in FIG. 44. Information and/or services only from those ones ofthe servers S<|...S Z (20) responding within the "Timeout" period are then incorporated thereinto the typical ones ofthe user responses UR n (37), as the typical service and/or information response forms IS n (39) at the user interface l n (14). FIG. 47 shows the typical completed service and/or information entry request form IF n (230), at the user interface l n (14), having same and different ones ofthe typical queries QQ n1 ...QQ n (53), different ones ofthe typical server addresses AQ n1 ...AQ nm (54), and the typical optional instructions VJ n ι...VJ nk (52). Typical same ones ofthe typical queries QQ n1 ...QQ nm (53) are "Cat", "Dog", and "Mouse", which are different one from the other. Typical same ones ofthe typical server addresses AQ n1 ...AQ nm (54) are "HotBot", "WebCrawler", and "Dejanews", which are different one from the other, and which are also different from "Yahoo" and "LookSmart". The typical optional instructions VJ n i-..VJ nk (52) have 5 "URL's per Search Engine", which instructs the client C π (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14) having 5 "URL's per Search Engine", rather than 10 "URL's per Search Engine", as instructed in FIG. 43. FIGS. 48-50 show typical ones ofthe user responses UR n (37), as the typical service and/or information response forms lS n (39) at the user interface l n (14), with reference to FIG. 47, having information and/or services therefrom the responses R n ι...R nm (32) incorporated therein, and incorporated thereinto Group I, Group II, and Group III, respectively. FIGS. 48-50 show typical ones ofthe user responses UR n (37), as the typical service and/or information response forms lS n (39) at the user interface l n (14), having the service and/or information group G n (35) having the addressable query information groups Gl n1 ...GI nz (63) therein, the labelled individual information groups LL n ιι---LL nzu (86) therein the addressable query information groups Gl n1 ...GI nz (63), the additional request links SLni---SLn (71), the optional service and/or information entry request form IE n (38), and other information and/or services therein, resulting from the same and different ones ofthe typical queries QQ n ι...QQ n m (53), and the same and different ones ofthe typical server addresses AQ n1 ...AQ nm (54), and the typical optional instructions VJni...VJ„ k (52), rather than results just from different ones ofthe typical server addresses AQ n1 ...AQ nm (54) as in FIGS. 44-46. FIGS. 48-50 show the typical ones ofthe user responses UR π (37), as the typical service and/or information response forms lS n (39) at the user interface l n (14), resulting from the typical ones ofthe queries QQ n1 ...QQ nm (53), "Cat", "Dog", and "Mouse", the same ones ofthe typical queries QQm, QQ P3 (53), and QQ n9 (53) being "Cat", other same ones ofthe typical queries QQ n2 (53), QQ n5 (53), QQ nβ (53),and QQ n8 (53) being "Dog", but different from "Cat", and other same ones ofthe typical queries QQ n4 and QQ n7 (53) being "Mouse", but different from "Cat" and/or "Dog", the typical ones ofthe queries QQ n ι...QQ nm (53), "Cat", "Dog", and "Mouse", being different one from the other. FIGS. 48-50 also show the typical ones ofthe user responses UR n (37), as the typical service and/or information response forms lS n (39) at the user interface l n (14), resulting from the typical ones ofthe server addresses AQ„i .. -AQnm (54), "HotBot", "WebCrawler", "Yahoo", "LookSmart" , and "Dejanews", the same ones ofthe typical server addresses AQ n ι and AQ n2 (54) being "HotBot", other same ones ofthe typical server addresses AQ n3 ...AQ n5 (54), being "WebCrawler", but different from "HotBot", another one ofthe server addresses AQ n6 (54), being "Yahoo", but different from "HotBot" and/or "WebCrawler", another one ofthe server addresses AQ n7 (54), being "LookSmart", but different from "HotBot" and or "WebCrawler" and/or "Yahoo", and other same ones ofthe typical server addresses AQ n8 (54) and QQ n9 (54) being "Dejanews", but different from "HotBot" and/or "WebCrawler" and/or "Yahoo" and/or "LookSmart", the typical ones ofthe server addresses AQ n1 ...AQ nm (54), "HotBot", "WebCrawler", "Yahoo", "LookSmart", and "Dejanews", being different one from the other. The typical same ones ofthe typical queries QQ n ι and QQ n3 (53) as "Cat" are incorporated thereinto the addressable query information groups Gl n ι (63) of Group I. The typical one ofthe queries QQ n2 (53) as "Cat" is incorporated thereinto the addressable query information groups Gl π2 (63) of Group II. The typical one ofthe queries QQ n4 (53) as "Mouse" is incorporated thereinto the addressable query information groups Gl n ι (63) of Group II. The other same ones ofthe typical queries QQ n s and QQ n β (53) as "Dog are incorporated thereinto the addressable query infonnation groups Gl n2 (63) of Group II. The typical one ofthe queries QQ n (53) as "Mouse" is incorporated thereinto the addressable query information groups Gl n ι (63) of Group III. The typical one ofthe queries QQ n s (53) as "Dog" is incorporated thereinto the addressable query information groups Gl n2 (63) of Group III. The typical one ofthe queries QQ n9 (53) as "Cat" is incorporated thereinto the addressable query information groups Gl n3 (63) of Group III. FIGS. 48-50 show typical ones ofthe user responses UR n (37), as the typical service and/or information response forms IS n (39) at the user interface l n (14), with reference to FIG. 47 having: "Search Engine Results" as "Interleave"; "URL's per Search Engine" as "5"; "URL Details" as "Summary"; "Timeout (seconds) per Search Engine" as "3"; "Page" as "1"; "Searches per Group as "5"; and "Group" as I, II, and III, respectively, for FIGS. 48- 50. Now again, FIGS. 48-50 show the typical ones ofthe user responses UR n (37), as the typical service and/or information response forms lS n (39) at the user interface l n (14), resulting from the same and different ones ofthe typical queries QQ n1 ...QQ nm (53), the same and different ones ofthe typical server addresses AQ n1 ...AQ nm (54), and the typical optional instructions VJ n ι - .. VJ nk (52), but which also result from the typical optional instructions VJ n1 ...VJ nk (52) having 5 "URL's per Search Engine", which instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form IS n (39) at the user interface l n (14) having 5 "URL's per Search Engine", rather than 10 "URL's per Search Engine", as in FIGS. 44-46. FIG. 51 shows another one ofthe typical completed service and/or infonnation entry request form lF n (230), at the user interface l n (14), having the same ones ofthe typical queries QQ n1 ...QQ nm (53), different ones ofthe typical server addresses AQ n ι ... AQ nm (54), and the typical optional instructions VJ n ι ... VJ nk (52). The typical optional instructions VJ π1 .-.VJ nk (52) have 18 "URL's per Search Engine", which instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14) having 18 "URL's per Search Engine". The typical optional instructions VJ n i-..VJn k (52) also instruct the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and or information response form lS n (39) at the user interface l n (14) at "Group" 2, having 4 "Searches per Group", at "Page" 2 ofthe "Current Group", with a 2 second "Timeout (seconds) per Search Engine", and to return the results "Separately". FIG. 52 show a typical one ofthe user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14), with reference to FIG. 51, having information and/or services therefrom the responses R n ι...R n m (32) incorporated therein, and incorporated thereinto Group II. FIG. 52 shows the typical one ofthe user response UR n (37), as the typical service and/or information response forms lS n (39) at the user interface l n (14), with reference to FIG. 51 having: "Search Engine Results" as "Separate"; "URL's per Search Engine" as "18"; "URL Details" as "Summary"; "Timeout (seconds) per Search Engine" as "1"; "Page" as "2"; "Searches per Group as "4"; and "Group" as "2". Groups I and/or III may be selected therefrom the typical one ofthe user response UR n (37), as the typical service and/or information response forms IS n (39) at the user interface l n (14) of FIG. 52. FIG. 53 shows another typical completed service and/or information entry request form IF n (230), at the user interface l n (14), having same and different ones ofthe typical queries QQ n1 ...QQ nm (53), different ones ofthe typical server addresses AQ n ι...AQ nm (54), and the typical optional instructions VJ n ι...VJ nk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as "Combined $[a-z]". The typical optional instructions VJ n ι...VJ nk (52) "Combined $[a-z]" of FIG. 53 instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14) having information and or services therein the responses R n ι...R n m (32) to be sorted in ascending order first numerically, and then alphabetically, therein the appropriate addressable query information groups Gl n ι - - -Gl nz (63): Items having prices will be sorted numerically by price, with lowest price first. The labelled individual information groups LL n11 ...LL nzu (86) therein the addressable query information groups Gl n1 ...GI nz (63) are grouped and sorted in ascending order one with the other and labelled and/or identified and associated correspondingly therewith the responses R„ι ... R nm (32) therefrom the servers Si ...S z (20). The "Combined $[a-z]" infonnation and/or services may typically be incorporated therein the appropriate addressable query information groups Gl n ι - - -Gl nz (63) in accordance with the "Combined $[a-z]" optional instructions VJ n -|...VJn k (52), and communicated therein the other typical user response UR n , as the typical service and/or information response form IS n at the user interface l n , which may be communicated thereto the user U n , as shown in FIG. 54. However, other sorting/grouping criteria may optionally be used, as will be discussed. FIG. 54 also depicts typical order boxes 402 of a typical order entry fonn OF n , which is communicated therewith the typical user response UR n , to enter quantities that the user U n may elect to order therethrough, as the typical service and/or information response form lS n at the user interface l n , which may be communicated thereto the user U n , which the user U n may enter an order therewith. FIG. 55 shows another typical completed service and or information entry request form IF n (230), at the user interface l n (14), having same and different ones ofthe typical queries QQ n ...QQ nm (53), different ones ofthe typical server addresses AQ n1 ...AQ nm (54), and the typical optional instructions VJ n i...VJ„ k (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as "Combined $[z-a]". The typical optional instructions VJ n ι...VJ nk (52) "Combined $[z-a]" of FIG. 55 instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form lSn (39) at the user interface l n (14) having infonnation and/or services therein the responses R n ι...R n m (32) to be sorted in descending order first alphabetically, and then numerically, therein the appropriate addressable query information groups Gl n1 ...GI nz (63). Items having prices will be sorted numerically by price, with highest price first. The labelled individual information groups LL n ιι...LL nzu (86) therein the addressable query information groups Gl n1 ...GI nz (63) are grouped and sorted in descending order one with the other and labelled and/or identified and associated correspondingly therewith the responses R n ι...R n m (32) therefrom the servers S.]...S Z (20). The "Combined $[z-a]" information and/or services may typically be incorporated therein the appropriate addressable query information groups Gl π1 ...GI nz (63) in accordance with the "Combined $[z-a]" optional instructions VJ n i-..VJn k (52), and communicated therein the other typical user response UR n , as the typical service and or information response form lS n at the user interface l n , which may be communicated thereto the user U n , as shown in FIG. 56. FIG. 57 shows another typical completed service and/or information entry request form lF n (230), at the user interface ! n (14), having same and different ones ofthe typical queries QQ n ...QQ nm (53), different ones ofthe typical server addresses AQni...AQ nm (54), and the typical optional instructions VJ n ...VJ nk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as "Separate $[a-z]". The typical optional instructions VJ n ι-..VJ nk (52) of FIG. 57 have "Separate $[a-z]", which instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14) in separate groups, sorted in ascending order first numerically, and then alphabetically, therein the appropriate addressable query information groups Gl n1 ...GI nz (63), i.e., grouped by the typical server addresses AQ n1 ...AQ nm (54), and communicated therein the other typical user response UR n , as the typical service and/or information response form IS n at the user interface l n , which may be communicated thereto the user U n , as shown in FIG. 58. Items having prices will be sorted numerically by price, with lowest price first within each ofthe typical server addresses AQ n1 ...AQ nm (54) groups. FIG. 59 shows another typical completed service and/or information entry request form IF n (230), at the user interface l n (14), having same and different ones ofthe typical queries QQ n1 .--QQnm (53), different ones ofthe typical server addresses AQ n1 ...AQ nm (54), and the typical optional instructions VJ n ι...VJ nk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as "Separate $[z-a]". The typical optional instructions VJ n ι-..VJ nk (52) of FIG. 59 have "Separate $[z-a]", which instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or information response form lS n (39) at the user interface l n (14) in separate groups, sorted in descending order alphabetically, and then numerically, therein the appropriate addressable query information groups Gl n1 ...GI nz (63), i.e., grouped by the typical server addresses AQ n1 ...AQ nm (54), and communicated therein the other typical user response UR n , as the typical service and/or information response form IS n at the user interface l n , which may be communicated thereto the user U n , as shown in FIG. 60. Items having prices will be sorted numerically by price, with highest price first within each ofthe typical server addresses AQ n ι - - ■ AQ nm (54) groups. FIG. 61 depicts a typical preview form of an order OP n , resulting from submission ofthe quantities to be ordered therein order boxes 402 ofthe order entry form OF n of FIG. 54, ofthe typical user response UR n , as the typical service and/or information response form IS n at the user interface l n , which may be communicated thereto the user U n , and the order entry form OF n , which the user U n may enter the order therewith. FIG. 62 depicts a typical order placement fonn OL n , having a typical preview form ofthe order OP n , resulting from submission ofthe quantities to be ordered therein order boxes 402 ofthe order entry form OF n of FIG. 54, ofthe typical user response UR n , as the typical service and/or infonnation response form IS n at the user interface l n , with the typical order information entered therein, or which the user U n may enter therethrough the typical preview form ofthe order OP n of FIG. 61. FIG. 63 depicts a typical order confinnation OC n , resulting from submission ofthe typical completed order placement form OL n of FIG. 62. The orders are also confirmed automatically by e-mail, with e-mailed confirmations being sent to the user U n (12), i.e., the buyer, seller, order fulfillment organization, with the total order being totaled, portions ofthe order being segregated and separated one from the other, and subtotaled, each segregated and subtotaled portion being directed to individual suppliers. FIG. 64 depicts another typical service and/or information entry request form lE n at the user interface l n , which the user U n may communicate other typical user input Ul n thereinto, which is substantially the same as the typical service and/or information entry request form IE n at the user interface l n of FIG. 53, except the typical service and/or information entry request form lE n at the user interface l n of FIG. 64 is adapted to allow 10 different ones ofthe typical queries QQ n ...QQ nm (53) and 10 different ones ofthe typical server addresses AQ n1 ...AQ nm (54) to be entered, whereas the typical service and/or infonnation entry request form IE n at the user interface l n of FIG. 53 is adapted to allow 9 different ones ofthe typical queries QQ n1 ...QQ nm (53) and 9 different ones ofthe typical server addresses AQ n ...AQ nm (54) to be entered. FIG. 65 depicts another typical service and/or information entry request form lE n at the user interface l n , which the user U n may communicate other typical user input Ul n thereinto, which is substantially the same as the typical service and/or information entry request form lE n at the user interface l n of FIG. 64, except the typical service and/or information entry request form IE n at the user interface l n of FIG. 65 is adapted to allow the 10 different ones ofthe typical queries QQ n1 ...QQ nm (53) and the 10 different ones ofthe typical server addresses AQ n1 ...AQ nm (54) to be entered, aligned vertically one with the other in pairs, in two rows predominantly horizontally adjacent one with the other, whereas the typical service and/or information entry request form lE n at the user interface l n of FIG. 64 is adapted to allow the 10 different ones ofthe typical queries QQ n1 ...QQ nm (53) and the 10 different ones ofthe typical server addresses AQ n1 ...AQ nm (54) to be entered, aligned horizontally one with the other in pairs adjacent one with the other in vertical rows. FIG. 66 shows another typical completed service and/or information entry request fonn IF n (230), at the user interface l n (14), having same and different ones ofthe typical queries QQ n ...QQ nm (53), different ones ofthe typical server addresses AQ n1 ...AQ nm (54), and the typical optional instructions VJ n1 ...VJ nk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as "Combined $[a-z]". The typical optional instructions VJ n -..VJ nk (52) "Combined $[a-z]" of FIG. 66 instructs the client C n (16) and/or the server PS (18) to return the typical user response UR n (37), as the typical service and/or infonnation response form IS n (39) at the user interface l n (14) having information and/or services therein the responses R n ι - . ■ R π m (32) to be sorted in ascending order first numerically, and then alphabetically, therein the appropriate addressable query information groups Gl n1 ...GI nz (63). Items having prices will be sorted numerically by price, with lowest price first. The labelled individual information groups LL n1 ι...LL nzu (86) therem the addressable query information groups Gl n ι---Gl nz (63) are grouped and sorted in ascending order one with the other and labelled and/or identified and associated correspondingly therewith the responses R n ι...R n m (32) therefrom the servers S.|...S Z (20). The "Combined $[a-z]" information and/or services may typically be incorporated therein the appropriate addressable query information groups Gl n ...GI nz (63) in accordance with the "Combined $[a-z]" optional instructions VJ n ι .. -VJn k (52), and communicated therein the other typical user response UR n , as the typical service and/or information response fonn lS n at the user interface l n , which may be communicated thereto the user U n , as shown in FIG. 67. FIG. 68 shows yet another typical completed service and or information entry request form IF n (230), at the user interface l n (14), having same and different ones ofthe typical queries QQ n1 ...QQ nm (53), different ones ofthe typical server addresses AQ n ι...AQ nm (54), and the typical optional instructions VJ n ι...VJ nk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as "Combined $[a-z]". FIG. 68 depicts another typical service and/or information entry request form lE n at the user interface l n , which the user U n may communicate other typical user input Ul n thereinto, which is substantially the same as the typical service and or information entry request form IE n at the user interface l n of FIG. 65, except the typical service and/or information entry request fonn IE n at the user interface l n of FIG. 68 is adapted to allow 12 different ones ofthe typical queries QQ n ...QQ nm (53) and 12 different ones ofthe typical server addresses AQ n1 ...AQ nm (54) to be entered, whereas the typical service and/or information entry request form lE n at the user interface l n of FIG. 68 is adapted to allow 10 different ones ofthe typical queries QQ n1 ...QQ nm (53) and 10 different ones ofthe typical server addresses AQ n1 ...AQ πm (54) to be entered. FIGS. 69 and 70 depicts yet other typical service and/or information entry request forms lE n at the user interface l n , which the user U n may communicate other typical user input Ul n thereinto. Each ofthe typical service and/or information entry request forms IE n at the user interface l n , which the user U n may communicate other typical user input Ul n thereinto, of FIGS. 53-70 may also have news stories, which may be updated intermittently on a substantially routine basis. The typical ones ofthe completed service and/or information entry request forms IFι...IF n (230) at the user interfaces lι...l n (14) shown in certain ones ofthe FIGS. 53-70 are typical examples ofthe completed service and/or information entry request forms IFi... lF n (230) at the user interfaces lι...l n (14), a much larger variety of which is possible. Typical queries QQ n1 ...QQ nm (53), typical server addresses AQ n1 ...AQ nm (54), and typical optional instructions VJ„i...VJ nk (52) therein the typical ones ofthe completed service and/or information entry request forms IFι...lF n (230) at the user interfaces lι-..l n (14) shown in certain ones ofthe FIGS. 53-70 are typical examples for illustrative purposes, and are not intended to limit the substantially infinite variety ofthe queries QQni - ■ -QQnm (53), the server addresses AQ n ι .. -AQ nm (54), and the optional instructions VJ n ι ...VJ„ k (52) that may be entered thereinto the service and/or information entry request forms lEi ...IE n (38), to derive the completed service and/or information entry request forms IFι...lF n (230) at the user interfaces lι...l n (14). Likewise, names and/or links and/or other information are incorporated therein the typical ones ofthe completed service and/or information entry request forms IFι...lF n (230) shown in certain ones ofthe FIGS. 53-70 are for illustrative purposes, and are not intended to limit the large variety ofthe completed service and/or information entry request forms IFi ...IF n (230) and the names and/or links and/or information that are possible, and that may be incorporated thereinto the completed service and/or information entry request forms lF-ι...IF n (230) at the user interfaces lι...l n (14). Any ones ofthe typical queries QQ n ι ...QQ nm (53), any values within the ranges allowable for the typical server addresses AQ n1 ...AQ nm (54), and any values allowable for the typical optional instructions VJ n ι...VJ nk (52) may be incorporated thereinto the typical ones of service and/or information entry request forms IE f ...IE n (38) at the user interfaces lι...l n (14) shown in certain ones ofthe FIGS. 53-70, which the users U ...U n (12) enter to complete the typical ones of the completed service and or information entry request forms IF ...IF n (230) at the user interfaces lι...l n (14) of shown in certain ones ofthe FIGS. 53-70. Any values within the ranges allowable for "Search Engine Results"; "URL's per Search Engine"; "URL Details"; "Timeout (seconds) per Search Engine"; "Page"; "Searches per Group"; and "Group" may be incorporated thereinto the typical ones of service and/or information entry request forms IE f ...IE n (38) at the user interfaces lι...l n (14) shown in certain ones ofthe FIGS. 53-70, which the users U f ...U n (12) enter to complete the typical ones ofthe completed service and/or information entry request forms IFι...IF n (230) at the user interfaces I f l n (14) shown in certain ones ofthe FIGS. 53-70. The users Ui ...U n (12), for example, may enter: the typical queries QQ n ι - ..QQ nm (53); any values within the ranges allowable for the typical server addresses AQ n1 ...AQ nm (54); and any values allowable for the typical optional instructions VJ n i.-.VJ nk (52), such as, for example, any allowable "Search Engine Results"; "URL's per Search Engine"; "URL Details"; "Timeout (seconds) per Search Engine"; "Page"; "Searches per Group"; and "Group" thereinto the typical ones of service and/or information entry request fonns IE f ...lE n (38) at the user interfaces I In (14 shown in certain ones ofthe FIGS. 53-70, which the users U-|...Un (12) enter to complete the typical ones ofthe completed service and or information entry request forms lFι...IF n (230) at the user interfaces I f ... In (14). The typical ones ofthe user responses UR f ...UR n (37), as typical service and/or information response forms IS f ...lS n (39) at the user interfaces I ...l n (14), may then be communicated thereto the corresponding ones of the users U f ...U n (12), accordingly. Certain ones ofthe FIGS. 53-70 show typical ones ofthe user responses UR f ...UR n (37), as the typical service and/or information response forms IS f ...IS n (39) at the user interfaces l f ...l n (14), which may be communicated thereto the corresponding ones ofthe users U f ...U n (12). The scope ofthe client-server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and the multitasking process 104, however, is not limited to such values. Use of such values herein is meant only for illustrative purposes, in teaching certain aspects ofthe multitasking system 10 ofthe present invention, the client- server multitasking process 99, and the multitasking process 104 by example. N. ADDITIONAL FEATURES AND/OR OTHER CONSIDERATIONS The present invention is directed to a client-server multitasking system and process capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries ofthe same and/or different ones ofthe servers, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly, and communicating service and/or information responses to the requestors and/or users substantially simultaneously and on-the-fly. The client-server multitasking system and process is capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks, and be capable of searching search engines and/or other sites substantially simultaneously and on-the-fly. The client-server multitasking system and process is capable of retrieving substantially multiple simultaneous services and/or information having the same and/or different criteria from the same and/or different servers, sorting, grouping, and/or organizing the responses from the servers and/or the clients into information and/or services responses, and communicating the service and/or information responses to the requestors and/or users substantially simultaneously. The requestors and/or the users may make substantially simultaneous service and/or information requests of servers and clients, using the same and/or different queries, and/or the same and/or different instructions. The same and/or different uniform resource locators, target resources, and/or paths may be used. The client-server multitasking system and process is capable of making multiple substantially simultaneous same and/or different requests of same and/or different servers, organizing responses from the servers into service and/or information responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously. The client-server multitasking system and process is also capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the requestors, and/or the users, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system is capable of use in a variety of applications, and is capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system and process is also be capable of building a client-server multitasking system search engine and/or database therefrom responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof, be capable of being searched and/or queried, querying sites referenced therein the client-server multitasking system search engine and/or database, and updating information and/or services stored therein. The client-server multitasking system and process are capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly. A requestor and/or user is capable of making substantially multiple simultaneous same and/or different requests of same and/or different servers. The client server-multitasking system and process is capable of organizing responses from the servers into service and/or information responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously, and on-the-fly. The requestors and/or users are capable of making substantially simultaneous service and/or information requests of the same and/or different ones of servers and or clients, using the same and or different queries, and or the same and/or different instructions. The client-server multitasking system and process is capable of retrieving substantially multiple simultaneous services and/or information having the same and/or different criteria from the same and/or different servers, sorting, grouping, and/or organizing the responses from the servers and/or the clients into information and/or services responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously. The same and/or different ones of uniform resource locators, target resources, and/or paths may be used. The requestors and/or users are capable of making multiple simultaneous searches. The searches may have at least one or a plurality of same or different queries ofthe same and/or different servers and/or clients. The responses from the servers and/or the clients may be of being organized into the service and/or information response in a variety of formats. The responses may be sorted within the service and/or information response, such as, for example, by category, query, group, page, order of importance, ascending and/or descending order, alphabetically and/or numerically, or other characteristics, as determined by the requestor, and/or the user, and/or the client-server multitasking system, and/or the responses may be combined within the service and/or information response, such as, for example, interleaving the responses one with the other, such as, for example, by order of relevance or other parameters. The responses may also be capable of being grouped by search criteria, server, order of importance, or by numerical factors such as value, price, or other numerical quantifier. For example, the responses may be presentable, for example, in ascending or descending order in interleaved format, such as top ones, twos, threes, and so on, or presentable separately to the requestor and/or the user. The order may be order of importance or relevance related, or, for example, numerically valued, such as price or stock market value. The client-server multitasking system and process is be capable of information and or service retrieval from the same and/or different ones ofthe servers substantially simultaneously and on-the-fly, using the same and/or different ones ofthe queries, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly. The client-server multitasking system and process is capable of substantially multiple simultaneous searching, using the same and/or different ones of queries ofthe same and or different ones ofthe clients and/or servers, which may be search engines, and/or sites, and/or servers, and/or locations on the network, and additionally and/or alternatively building a client-server multitasking search engine and/or database. The client-server multitasking search engine and/or database is capable of storing the information and/or services retrieved therefrom the search engines, and/or sites, and/or servers, and/or locations being queried on the network therein, and building the client-server search engine and/or database. The client-server multitasking search engine should is also capable of being queried either directly and/or in combination therewith the substantially simultaneous searching, using the same and/or different queries ofthe same and/or different search engines, sites, servers, and/or databases. The client-server multitasking search engine and/or database should is also capable of updating information and/or services stored therein by querying sites, servers, search engines, and/or databases containing information and/or services referenced in client- server multitasking search engine and or database. The client-server multitasking system and process is also capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks. The client-server multitasking system and process are capable of substantially simultaneous searching ofthe same and/or different ones of search engines and or sites on the network substantially on-the-fly, with the same and/or different ones ofthe queries, and sorting, grouping, and or organizing responses therefrom substantially on-the-fly. The client-server multitasking system and process are also capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the requestors and/or the users, and/or instructions resident within, the client-server multitasking system and/or process. The client-server multitasking system and process are also capable drilling down and/or up to different levels within the search engines, sites, and/or servers being queried. The client-server multitasking system and process are capable of providing manual and/or timed updates. Such timed updates allow for motion related presentation to the requestor and/or the user. The client-server multitasking system and process are capable of incorporating information and/or services thereinto a variety of user interfaces at different locations therein the user interfaces, grouping, and/or organizing the information and/or services, and optionally eliminating duplicate infonnation and/or services. The client-server multitasking system and process are capable of incorporating links, graphics, video, text, and audio, and/or combinations thereof, and selective advertising, according to selectable search, query, sorting, and/or grouping criteria, and/or combinations thereof thereinto the information and/or services to be delivered thereto the user interfaces. The requestor and/or the user may place orders, such as purchases, and/or other types of orders, payments, confirmations thereof, and/or combinations thereof, either directly and/or therethrough servers and/or sites thereon the network. The client-server multitasking system is capable of use in a variety of applications, and is capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system is capable of, for example, determining best query results, with respect to a plurality of search engine results; purchasing and/or price comparisons, viewing and/or reviewing prices/values and trends for different sites, determining lowest costs and lowest cost analyses for wholesale and retail purposes; product availability, e.g., airline tickets, pricing, and ticket availability, from different airlines to the same and/or different locations; purchasing of commodities and/or stocks form the same and/or different sites with updates every few seconds and/or minutes; obtaining prices and/or values in different stock markets substantially simultaneously; and searching for jobs on the same and/or different job sites, using the same and/or different job criteria, for example, on a daily basis, the job sites having changing job availability; and/or a combination thereof, all substantially simultaneously. The client-server multitasking system is capable of presenting information and/or services for review and/or updating from the same and/or different ones of sites, servers, and/or applications substantially simultaneously, and trend analysis thereof, using a variety of sorting, grouping and/or organizing criteria, according to the needs ofthe requestor, and/or the user, and/or resident within the client-server multitasking system. The client server-multitasking system and process are capable of service and/or information retrieval from at least one server, organization, communication, and presentation of such services and/or information to at least one requestor and or user, and/or optional storage, and or retrieval of such services and or information from the optional storage. The client-server multitasking system and process are capable of building a client-server multitasking system search engine and/or database therefrom responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof. The client-server multitasking system search engine and/or database having stored infonnation and/or services therein are also searchable, are capable of full text searches thereof, and are searchable by the servers and/or the clients on the network, either separately and/or in combination therewith the substantially simultaneous multiple same and/or different searches and/or queries ofthe same and/or different servers on the network. Infonnation therein the client-server multitasking system search engine and/or database are also searchable and/or retrievable, and are capable of being incorporated therein the service and/or information responses delivered thereto the user interfaces, according to search criteria, selectively and/or automatically, by the requestor and/or the user. The client-server multitasking system search engine and/or database are capable of spidering, and or roboting, and/or querying sites, services and/or information to be stored therein and/or stored therein the client-server multitasking system search engine and or database, and updating the services and/or infonnation to be stored and/or stored therein the client-server multitasking system search engine and/or database. The client-server multitasking system and process, then, are capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries ofthe same and/or different ones ofthe servers, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly, and communicating service and/or information responses to the requestors and/or users substantially simultaneously and on-the-fly. The client-server multitasking system and process are capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks, and are capable of searching search engines and/or other sites substantially simultaneously and on-the-fly. The client-server multitasking system and process are capable of sorting, grouping, and or organizing results therefrom the servers, search engines, and or sites, in accordance with instructions from the requestors, and/or users, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system are capable of use in a variety of applications, and capable of information comparison and or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system and process are capable of building a client- server multitasking system search engine and/or database therefrom responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof, is capable of being searched and/or queried, querying sites referenced therein the client-server multitasking system search engine and/or database, and updating information and/or services stored therein. The client-server multitasking system and process are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information therefrom the same and/or different ones ofthe servers and/or clients having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information thereinto user responses for delivery to and use by the requestors and/or users. The client-server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and the multitasking process 104, the server PS (18) and/or the clients C ...C n (16), then, are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information therefrom the same and/or different ones ofthe servers S ...S z (20), and/or the optional servers SO f ...SO p (22), and or the clients C ...C n (16), having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information thereinto the user responses UR f ...UR n (37) for delivery to the user interfaces I f ...l n (14) and use by the users U f ...U n (12). The client-server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process, the user interfaces I ...l n (14), and/or the clients C f ...C n (16), and/or the server PS (18), and/or the servers S ...S z (20), and/or the optional servers SO f ...SO p (22) may be constructed of hardware, firmware, software, machines, and/or operating systems, and/or combinations thereof, and/or other suitable means, and/or other components and/or systems, and/or combinations thereof. Such hardware, firmware, software, machines, and/or operating systems, and/or combinations thereof, other components and/or systems, and/or other suitable means, and/or combinations thereof may have therein and/or be resident therein, but are not limited to computer components and/or systems, television and/or telecommunications components and/or systems, merger of television and computer systems, and/or merger of television and/or computer and/or telecommunications systems, networks, simulators, interactive technologies and/or systems, cybernetics and/or cybernetic systems, and/or combinations thereof. The clients C f ...C n (16), the server PS (18), the servers S f ...S z (20), and or the optional servers SO f ...SO p (22) may be search engines, and/or sites, and/or servers, and/or clients, and/or URL's, and/or databases, and/or locations on the network, and/or other suitable components and/or systems, and/or other suitable means, and/or combinations thereof, which may be capable of communicating on the network 24. The scope ofthe client-server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and the multitasking process 104, however, is not limited to search engines, and/or sites, and/or servers, and/or clients, and/or URL's, and/or databases, and/or locations on the network, and or other suitable components and/or systems, and/or other suitable means, and/or combinations thereof, which may be capable of communicating on the network 24, as it is recognized that other components, systems, technologies, and/or operating systems exist and/or emerge that may make use ofthe benefits ofthe present invention, and are either on the horizon and/or are recognized to be forthcoming. The client-server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process, the user interfaces I f ...l n (14), and/or the clients C f ...C n (16), and/or the server PS (18), and/or the servers S f ...S z (20), and/or the optional servers SO f ...SO p (22), may then be hardware, firmware, software, and/or machines, and/or operating systems, and/or other suitable means, and/or combinations thereof, and may have and/or be resident within general purpose computers, special purpose computers, televisions, computer-television combinations, telecommunications systems, networks, mergers of computer and/or television technology and/or telecommunications technology and/or network technology, media, film, entertainment, interactive technologies and/or systems, cybernetics and/or cybernetic systems and/or technology, components, and/or systems, and/or other suitable means, and/or combinations thereof, and may be integrated one with the other and/or with other components and/or systems of one another, and may each be substantially the same and/or different one from the other. The client-server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process, the user interfaces I f ...l n (14), and/or the clients C f ...C n (16), and/or the server PS (18), and/or the servers S f ...S z (20), and/or the optional servers SO f ...SO p (22) may each have the same and/or different hardware, firmware, software, and/or ones of operating systems, and/or other suitable means, and/or combinations thereof. The optional databases 41 and/or 42 may also be hardware, firmware, software, and/or machine based, and/or other suitable means, and/or a combinations thereof, have the same and/or different ones of operating systems and/or combinations thereof, and may have memory components associated therewith. The client-server multitasking system and process is capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks. Such networks may be Earth based, satellite based, and/or space based, and/or other suitable means, and/or combinations thereof. The scope ofthe client-server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and the multitasking process 104, however, is not limited to such components, systems, technologies, operating systems and/or networks, as other components, systems, technologies, and/or operating systems exist and/or emerge that may make use ofthe benefits ofthe present invention, and are either on the horizon and/or are recognized to be forthcoming. Determination as to whether the server PS (18) performs the multitasking process 104, and/or whether particular ones ofthe clients C f .. ,C n (16) perform the multitasking process 104, may optionally be made at the particular ones ofthe clients C|...C n (16) and/or the server PS (18). Such determination may optionally be made by the users U ...U n (12), and/or be based upon processing power, capabilities, and/or configurations ofthe particular ones of the clients C f ...C n (16), the server PS (18), and the network 24 considerations (traffic, load, and/or other considerations). The client-server multitasking search engine and/or database is capable of updating information and/or services stored therein by querying sites, servers, search engines, and/or databases containing information and/or services referenced in client-server multitasking search engine and/or database. The client-server multitasking system and process is capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks, and is capable of searching search engines and/or other sites substantially simultaneously and on-the-fly. The client-server multitasking system and process is capable of substantially simultaneous searching ofthe same and/or different ones of search engines and/or sites on the network substantially on-the-fly, with the same and/or different ones ofthe queries, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly. The client-server multitasking system and process is also capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and or sites, in accordance with instructions from the requestors, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system and process is also capable drilling down and/or up to different levels within the search engines, sites, and/or servers being queried. Now again, the typical ones ofthe service and/or information entry request forms IE f ...IE n (38) at the user interfaces I f ...l n (14) shown in FIGS. 1-70 are typical examples ofthe service and/or information entry request forms IE f ...IE n (38) at the user interfaces I f ...l n (14), a much larger variety of which is possible. Names and/or links and/or other information are incorporated therein the typical ones ofthe service and/or information entry request forms IE f ...lE n (38) shown in FIGS. 1-70 for illustrative purposes, and are not intended to limit the large variety ofthe service and/or information entry request forms IE f ...lE n (38) and the names and/or links and/or information that are possible, and that may be incorporated thereinto the service and/or information entry request forms IE f ...IE n (38) at the user interfaces I f ...l n (14). Now again, The typical ones ofthe completed service and/or information entry request forms IF f ...IF n (230) at the user interfaces I ...l n (14) are typical examples ofthe completed service and/or information entry request forms IF f ...IF n (230) at the user interfaces I ... I n (14), a much larger variety of which is possible. Typical queries QQni ...QQnm (53), typical server addresses AQ n1 ...AQ nm (54), and typical optional instructions VJ nf ...VJ n k (52) therein the typical ones ofthe completed service and/or information entry request forms IF f .. JF n (230) at the user interfaces I f ...l n (14) shown in FIGS. 1-70 are typical examples for illustrative purposes, and are not intended to limit the substantially infinite variety ofthe queries QQ n1 ...QQ nm (53), the server addresses AQ n ...AQ πm (54), and the optional instructions VJ n ...VJ nk (52) that may be entered thereinto the service and/or infonnation entry request forms IEf ...IE n (38), to derive the completed service and/or information entry request forms IF f ...lF n (230) at the user interfaces I f ...l n (14). Likewise, names and/or links and/or other information are incorporated therein the typical ones ofthe completed service and or information entry request forms IF f ...IF n (230) for illustrative purposes, and are not intended to limit the large variety ofthe completed service and or information entry request forms IF f ...lF n (230) and the names and/or links and/or information that are possible, and that may be incorporated thereinto the completed service and/or information entry request forms IF f ...IF n (230) at the user interfaces I ... I n (14). Now again, the typical ones ofthe user responses UR f ...UR n (37), as typical service and/or information response forms IS f ...lS n (39) at the user interfaces l f ...l n (14) are typical examples ofthe user responses UR f ...UR n (37), as typical service and/or information response forms IS f ...IS n (39) at the user interfaces I f ...l n (14), a much larger variety of which is possible. Certain ones of FIGS. 1-70 illustrate typical examples of typical ones ofthe user responses UR f ...UR n (37), as typical service and/or information response forms IS f ...IS n (39) at the user interfaces I f ...l n (14) to the typical queries typical queries QQ nf ...QQ nm (53), the typical ones ofthe server addresses AQ n ... AQ nm (54), and the typical optional instructions VJ n ι .. -VJ nk (52) having been entered therein the typical ones ofthe completed service and/or information entry request forms IF f ...lF n (230) at the user interfaces l f ...l„ (14). The typical examples ofthe typical ones ofthe user responses UR f ...UR n (37), as typical service and/or information response forms IS f ...lS n (39) at the user interfaces I f ...l n (14) are for illustrative purposes, and are not intended to limit the substantially infinite variety ofthe user responses UR f ...UR n (37), as the service and/or information response forms IS f ...IS n (39) at the.user interfaces I f ...l n (14), the queries QQ n1 ...QQ nm (53), the server addresses AQ n ...AQnm (54), and the optional instructions VJ nf ...VJ n k (52) that may be entered thereinto the service and/or information entry request forms IE f ...IE n (38), to derive the to the completed service and/or infonnation entry request forms IF f ...lF n (230), and which result in the user responses UR f ...UR n (37), as the service and/or infonnation response forms IS f ...IS n (39) at the user interfaces I ...l n (14). Likewise, names and/or links and/or other information are incorporated therein the typical ones ofthe user responses UR f ...UR n (37), as the service and/or information response forms lS 1 ...IS n (39) at the user interfaces I f ...l n (14) are shown for illustrative purposes, and are not intended to limit the large variety ofthe user responses UR f ...UR n (37), as the service and/or information response forms IS f ...IS n (39) at the user interfaces I f ...l n (14), and the names and or links and/or information that are possible, and that may be incorporated thereinto the user responses UR f ...UR n (37), as the service and/or information response forms IS ...IS n (39) at the user interfaces I f .. ,l n (14). The server addresses AQ n1 ...AQ nm (54), such as WebCrawler, Altavista, Lycos, Infoseek, Excite, Yahoo, LookSmart, HotBot, Dejanews, Amazon, Borders, BarnesandNoble, Google, and/or others that may have been used herein are for illustrative purposes, to illustrate typical ones ofthe service and/or information entry request forms IE f ...IE n (38) at the user interfaces I f ...l n (14), typical ones ofthe completed service and/or information entry request forms IF f ... IF n (230) at the user interfaces l f ...l n (14), and/or typical ones ofthe user responses UR f ...UR n (37), as the service and/or information response forms IS f ...IS n (39) at the user interfaces I f ...l n (14), and other examples used herein, are used merely to illustrate typical examples ofthe server addresses AQ n1 ...AQ nm (54) and results therefrom that may be possible. The examples shown in FIGS. 1-70, and other examples used herein, are examples ofthe substantially infinite variety ofthe server addresses AQ n1 ...AQ nm (54) that may be used with the client-server multitasking system 10 ofthe present invention and the results that may be obtained therefrom. The typical server addresses AQ n1 ...AQ nm (54), such as WebCrawler, Altavista, Lycos, Infoseek, Excite, Yahoo, LookSmart, HotBot, Dejanews, Amazon, Borders, BarnesandNoble, Google, and/or others that may have been used herein are for illustrative purposes only and are not intended to limit the scope ofthe client-server multitasking system 10 of the present invention. It should also be obvious that the typical queries QQ n ...QQ nm (53) used in the examples shown in FIGS. 1-70 and other examples used herein are for illustrative purposes and are merely typical examples ofthe substantially infinite variety of the queries QQ n ι...QQ nm (53) that may be used with the client-server multitasking system 10 ofthe present invention and the results that may be obtained therefrom, and are not intended to limit the substantially infinite variety ofthe queries QQ n ι - . -QQnm (53) that may be used with the client-server multitasking system 10 of the present invention and the results that may be obtained therefrom. The typical queries QQ n1 ...QQ nm (53) used in the examples shown in FIGS. 1-70 and other examples used herein are for illustrative purposes only and are not intended to limit the scope ofthe client-server multitasking system 10 ofthe present invention. The typical labelled individual information groups LL n11 ...LL nzu (86), the typical optional links LD n m ---LD πm r (82), and/or the typical optional descriptions DD nm1 ...DD nmr (83), and/or the typical optional prices/values PDnmi " -PDnmr (84), and/or the typical optional images ID nm ...ID nmr (85), and/or advertisements and/or advertisement links, and/or URL's, and/or locations, and/or other items and/or objects shown in FIGS. 1-70 and other examples used herein are typical examples for illustrative purposes only and are not intended to limit the scope ofthe client-server multitasking system 10 ofthe present invention. A substantially infinite variety ofthe labelled individual information groups LL n11 ...LL nzu (86), the optional links LD nmf ...LD nmr (82), and/or the optional descriptions DD nm1 ...DD nmr (83), and/or the optional prices/values PD nmf ...PD nm r (84), and/or the optional images IDnm f ...IDnmr (85), and/or advertisements and/or advertisement links, and/or URL's, and/or locations, and/or other items and/or objects may result from the substantially infinite varieties and combinations thereof of the queries QQni ...QQ nm (53) and the substantially infinite varieties and combinations thereof of the server addresses AQ n1 ...AQ nm (54) ofthe client-server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process. Likewise, the typical grouping/sorting criteria shown herein in the examples is for illustrative purposes only and is not intended to limit the scope ofthe client-server multitasking system 10 ofthe present invention. It is possible to sort the responses within the service and/or information response, such as, for example, by category, query, group, page, order of importance, ascending and/or descending order, alphabetically and/or numerically, or other characteristics, as determined by the requestor, and/or the user, and/or the client-server multitasking system, or to combine the responses within the service and/or information response, such as, for example, interleaving the responses one with the other, such as, for example, by order of relevance or other parameters. The responses then are capable of being grouped by search criteria, server, order of importance, or by numerical factors such as value, price, or other numerical quantifier. For example, the responses may be presentable, for example, in ascending or descending order in interleaved format, such as top ones, twos, threes, and so on, or presentable separately to the requestor and/or the user. The order may be order of importance or relevance related, or, for example, numerically valued, such as price or stock market value. A substantially infinite variety of results may be generated from the substantially infinite variety of grouping/sorting criteria possible with the client-server multitasking system 10 ofthe present invention. A substantially infinite variety of URL's, links, locations, sites, servers, and/or clients, other items and/or objects may be used with the client-server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process. Examples of URL's, links, locations, sites, servers, and/or clients, other items and or objects shown in FIGS. 1-70 are typical examples of URL's, links, locations, sites, servers, and/or clients, other items and/or objects that may be of used therewith the client-server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and the multitasking process 104, and are used herein for illustrative purposes only, and are not intended to limit the scope ofthe client- server multitasking system 10 ofthe present invention, the client-server multitasking process 99, and/or the multitasking process 104. A substantially infinite variety of advertisements and/or links may be used with the client-server multitasking system 10 ofthe present invention. The advertisements and/or links to such sites as Netscape and/or ABC News, Disney Discovery, Warner, ABC, Universal, CBS, NBC, TV Guide, NYtimes, ESPN, WSjournal, CNN, and/or other sites used in the examples shown in FIGS. 1-70 and other examples used herein are for illustrative purposes only and are not intended to limit the scope ofthe client-server multitasking system 10 ofthe present invention. It should also be obvious that advertisements and/or links to such sites as Netscape and/or ABC News, and/or other sites that may be used herein are for illustrative purposes only and are not intended to limit the scope ofthe client- server multitasking system 10 ofthe present invention. Each ofthe typical service and/or information entry request forms IE n at the user interface l n , which the user U n may communicate other typical user input Ul n thereinto, may also have news stories, which may be updated intermittently on a substantially routine basis. The client-server multitasking system and process are also capable of performing as a multiple query search engine, which performs multiple queries of multiple sites, and of performing as a single point of sale for purchasing multiple products from multiple sources. Although the present invention has been described in considerable detail with reference to certain preferred versions thereof, other versions are possible. Therefore, the spirit and scope ofthe appended claims should not be limited to the description ofthe preferred versions contained herein.

Claims: CLAIMS What is claimed is: 1. A multitasking process comprising: a) parsing, processing, and/or formatting a service and/or information request thereinto a current request group; b) opening connections therewith and making at least one request thereof at least one server; c) parsing, processing, formatting, grouping, and/or organizing at least one response therefrom said at least one server thereinto at least one addressable response information group; d) formulating information therefrom said current request group thereinto a request pointer/address group having at least one pointer/address; e) formulating at least one addressable query pointer/address group having at least one other pointer/address; f) incorporating information and/or services therefrom said at least one addressable response information group thereinto at least one addressable query information group; and g) incorporating said at least one addressable query information group thereinto a service and/or information response. 2. The multitasking process of claim 1, further comprising parsing, processing, and/or formatting said service and/or information request thereinto at least one other request group. 3. The multitasking process of claim 1, further comprising parsing, processing, and/or formatting said service and/or information request thereinto at least one optional instruction. 4. The multitasking process of claim 1 , further comprising directing said pointers/addresses therefrom said request pointer/address group to point/address said addressable query pointer/address groups. 5. The multitasking process of claim 4, further comprising directing said other pointers/addresses therefrom said addressable query pointer/address groups to point/address information and/or services therein said addressable response information groups. 6. The multitasking process of claim 5, further comprising directing said other pointers/addresses therefrom said addressable query pointer/address groups to point/address information and/or services therein said addressable response information groups based upon grouping and/or sorting criteria. 7. The multitasking process of claim 1, wherein said requests of said servers are the same and/or different one from the other. 8. The multitasking process of claim 1, wherein said servers are the same and/or different one from the other. 9. The multitasking process of claim 1 , wherein said requests are the same and/or different one from the other ofthe same and/or different ones of said servers. 10. The multitasking process of claim 1 , wherein said requests have the same and/or different ones of queries. 11. The multitasking process of claim 11 , wherein said requests have the same and/or different ones of queries. 12. The multitasking process of claim 1, wherein said multitasking process is performed substantially on-the- fly. 13. The multitasking process of claim 1, wherein said connections are opened substantially simultaneously and said requests are made substantially simultaneously. 14. The multitasking process of claim 1, wherein further duplicate information and/or services therein said addressable response information groups is discarded. 15. The multitasking process of claim 1, wherein information and/or services therefrom said addressable response information groups is incorporated thereinto at least one individual information group therein at least one said addressable query infonnation group. 16. The multitasking process of claim 15, wherein said individual infonnation groups are labelled and/or identified. 17. The multitasking process of claim 16, wherein said labelled and/or identified individual information groups are alternatingly interleaved one with the other and labelled and/or identified and associated correspondingly therewith said responses therefrom said servers. 18. A multitasking process comprising: a) parsing, processing, and/or formatting a service and/or information request thereinto a current request group; b) opening connections therewith and making at least one request thereof at least one server; c) parsing, processing, formatting, grouping, and/or organizing at least one response therefrom said at least one server thereinto at least one addressable response information group; d) formulating information therefrom said current request group thereinto a request pointer/address group having at least one pointer/address; e) incorporating information and/or services therefrom said at least one addressable response information group thereinto at least one addressable query information group; and f) incorporating said at least one addressable query information group thereinto a service and/or information response. 19. The multitasking process of claim 18, further comprising directing said pointers/addresses therefrom said request pointer/address group to point/address information and/or services therein said addressable response information groups. 20. A client-server multitasking system comprising: a) means for parsing, processing, and/or formatting a service and/or information request thereinto a current request group; b) means for opening connections therewith and making at least one request thereof at least one server; c) means for parsing, processing, formatting, grouping, and/or organizing at least one response therefrom said at least one server thereinto at least one addressable response information group; d) means for formulating information therefrom said current request group thereinto a request pointer/address group having at least one pointer/address; e) means for formulating at least one addressable query pointer/address group having at least one other pointer/address; f) means for incorporating information and/or services therefrom said at least one addressable response information group thereinto at least one addressable query information group; and g) means for incorporating said at least one addressable query information group thereinto a service and/or information response. 21. A multitasking process comprising: a) means for parsing, processing, and/or formatting a service and/or information request thereinto a current request group; b) means for opening connections therewith and making at least one request thereof at least one server; c) means for parsing, processing, formatting, grouping, and/or organizing at least one response therefrom said at least one server thereinto at least one addressable response information group; d) means for formulating information therefrom said current request group thereinto a request pointer/address group having at least one pointer/address; e) means for incorporating information and/or services therefrom said at least one addressable response information group thereinto at least one addressable query information group; and f) means for incorporating said at least one addressable query information group thereinto a service and/or information response.

Inventors: LUNENFELD HARVEY, LUNENFELD, HARVEY
Applicants: LUNENFELD HARVEY, LUNENFELD, HARVEY
Application year: 2001
Main classification: G06F9
IPC codes: G06F17