Client-server multitasking

[0002] 1. Field of the Invention

[0003] The present invention relates generally to clients and servers and more particularly to client-server multitasking.

[0004] 2. Background Art

[0005] 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.

[0006] A requestor and/or user should be capable of making substantially multiple simultaneous same and/or different requests of same and/or different servers. The client server-multitasking system and process should be 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 users substantially simultaneously, and on-the-fly.

[0007] The requestors and/or users should be 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 should be 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.

[0008] The requestors and/or the users should be capable of making multiple simultaneous searches. The searches should be capable of having 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 should be capable of being organized into the service and/or information response in a variety of formats. It should be 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 requester, 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 should 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 should 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.

[0009] The client-server multitasking system and process should be 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.

[0010] The client-server multitasking system and process should be 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 should be 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 also be 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 also be 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.

[0011] The client-server multitasking system and process should also be 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.

[0012] The client-server multitasking system and process should be 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.

[0013] The client-server multitasking system and process should also be capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the requesters, and/or the users, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system and process should also be capable drilling down and/or up to different levels within the search engines, sites, and/or servers being queried.

[0014] The client-server multitasking system and process should be capable of providing manual and/or timed updates. Such timed updates should allow for motion related presentation to the requestor and/or the user.

[0015] The client-server multitasking system and process should be 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 information and/or services.

[0016] The client-server multitasking system and process should be 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 user should also be capable of placing 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.

[0017] The client-server multitasking system should be capable of use in a variety of applications, and be capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system should be 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 should be 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.

[0018] A client server-multitasking system and process are needed, which 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 the 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 should 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. The client-server multitasking system search engine and/or database having stored information and/or services therein should also be searchable, be capable of full text searches thereof, and be 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 should also be searchable and/or retrievable, and should be 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 should also be 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.

[0019] The client-server multitasking system and process should be 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 requesters and/or users.

[0020] For the foregoing reasons, there is a need for 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 should be 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 should be 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 should also be 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 should 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 should be 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 requesters and/or users.

[0021] 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.

[0022] 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 requesters 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.

[0023] The same and/or different uniform resource locators, target resources, and/or paths may be used.

[0024] 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.

[0025] 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.

[0026] 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.

[0027] A requester 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 requesters and/or the users substantially simultaneously, and on-the-fly.

[0028] 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.

[0029] 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.

[0030] The client-server multitasking system and process is be 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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 information and/or services.

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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 information 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 information group thereinto a service and/or information response.

[0044] 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:

[0045] FIG. 1 is a schematic representation of a client-server multitasking system, constructed in accordance with the present invention;

[0046] FIG. 2 is a more detailed schematic representation of the client-server multitasking system;

[0047] FIG. 3 is a schematic representation of user input UI_nfrom user U_nthereinto user interface I_nof the client-server multitasking system;

[0048] FIG. 4 is a schematic representation of a server S_zof the client-server multitasking system;

[0049] FIG. 5A depicts a typical service and/or information entry request form IE_nat the user interface I_n, which the user U_nmay communicate typical user input UI_nthereinto;

[0050] FIG. 5B depicts the typical service and/or information entry request form IE_nat the user interface I_nof FIG. 5B with reference alphanumerics;

[0051] FIG. 6 depicts another typical service and/or information entry request form IE_nat the user interface I_n, which the user U_nmay communicate other typical user input UI_nthereinto;

[0052] FIG. 7 depicts another typical service and/or information entry request form IE_nat the user interface I_n, which the user U_nmay communicate other typical user input UI_nthereinto;

[0053] FIG. 8 depicts another typical service and/or information entry request form IE_nat the user interface I_n, which the user U_nmay communicate other typical user input UI_nthereinto;

[0054] FIG. 9 depicts another typical service and/or information entry request form IE_nat the user interface I_n, which the user U_nmay communicate other typical user input UI_nthereinto;

[0055] FIG. 10 depicts another typical service and/or information entry request form IE_nat the user interface I_n, which the user U_nmay communicate other typical user input UI_nthereinto;

[0056] FIG. 11 depicts a typical completed service and/or information entry request form IF_nat the user interface I_n;

[0057] FIG. 12 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0058] FIG. 13 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0059] FIG. 14A depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0060] FIG. 14B depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0061] FIG. 14C depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0062] FIG. 15 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0063] FIG. 16 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0064] FIG. 17 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0065] FIG. 18 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0066] FIG. 19 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0067] FIG. 20 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0068] FIG. 21 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0069] FIG. 22 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0070] FIG. 23 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0071] FIG. 24 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0072] FIG. 25 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0073] FIG. 26 depicts another typical completed service and/or information entry request form IF_nat the user interface I_n;

[0074] FIGS. 27A-27C depict a typical user response UR_n, as a typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0075] FIGS. 28A-28C depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0076] FIGS. 29A-29C depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0077] FIGS. 30A-30B depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0078] FIGS. 31A-31B depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0079] FIGS. 32A-32B depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0080] FIGS. 33A-33C depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0081] FIGS. 34A-34C depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0082] FIGS. 35A-35C depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0083] FIGS. 36A-36C depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0084] FIGS. 37A-37D depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0085] FIGS. 38A-38D depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0086] FIGS. 39A-39C depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0087] FIGS. 40A-40M depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0088] FIGS. 41A-41F depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0089] FIGS. 42A-42O depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0090] FIGS. 43A-43O depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0091] FIGS. 44A-44C depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0092] FIGS. 45A-45C depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0093] FIGS. 46A-46E depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0094] FIGS. 47A-47C depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0095] FIGS. 48A-48D depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0096] FIGS. 49A-49I depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0097] FIGS. 50A-50K depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0098] FIGS. 51A-51G depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0099] FIGS. 52A-52C depict another typical user response UR_n, as the typical service and/or information response form IS_nat the user interface I_n, which may be communicated thereto the user U_n, illustrated in partial views;

[0100] FIG. 53A is a schematic representation of a server PS of the client-server multitasking system having an optional database;

[0101] FIG. 53B is a schematic representation of a client C_nof the client-server multitasking system having an optional database;

[0102] FIG. 54 is a schematic representation of a particular one of the clients C₁. . . C_nof the client-server multitasking system, designated as the particular client C_n, 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 Q_n1. . . Q_nm, therethrough the server PS;

[0103] FIG. 55 is a schematic representation of the particular client C_nof 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 Q_n1. . . Q_nm;

[0104] FIG. 56 is a schematic representation of the particular client C_nof 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 Q_n1. . . Q_nm, and also therethrough the server PS;

[0105] FIG. 57 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;

[0106] FIG. 58 is a schematic representation of a particular service and/or information request IQ_n;

[0107] FIG. 59 is a schematic representation of a particular service and/or information request IQ_nparsed, 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_n1. . . Q_nm, obtain the responses R_n1. . . R_nm, and incorporate information therefrom into a particular service and/or information response IR_n;

[0108] FIG. 60 is a schematic representation of the particular service and/or information request IQ_nparsed, 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_n1. . . Q_nm, obtain the responses R_n1. . . R_nm, 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. 59;

[0109] FIG. 61 is a schematic representation of the particular service and/or information response IR_nhaving a service and/or information 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;

[0110] FIG. 62 is a schematic representation of a particular user service and/or information request iq_n;

[0111] FIG. 63 is a schematic representation of a particular user service and/or information request iq_nparsed, processed, and/or formatted into the current request group QA_nc, the request groups QA_n1. . . QA_nz, and the corresponding optional instructions VJ_n1. . . VJ_nk, and utilization of information therefrom to make the requests Q_n1. . . Q_nm, obtain the responses R_n1. . . R_nm, and incorporate information therefrom into the particular user service and/or information response ir_n;

[0112] FIG. 64 is a schematic representation of the particular user service and/or information request iq_nparsed, processed, and/or formatted into the current request group QA_nc, the request groups QA_n1. . . QA_nz, and the corresponding optional instructions VJ_n1. . . VJ_nk, and utilization of information therefrom to make the requests Q_n1. . . Q_nm, obtain the responses R_n1. . . R_nm, and incorporate information therefrom into the particular user service and/or information response ir_n, having other grouping/sorting that may be used additionally and/or alternatively to that of FIG. 63;

[0113] FIG. 65 is a schematic representation of the particular user service and/or information response ir_nhaving 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;

[0114] FIG. 66A is a schematic representation of a response information group RG_nmhaving addressable individual information groups LG_nm1. . . LG_nmrshowing optional addressable pointer/address indices IN_nm1. . . IN_nmrcorrespondingly associated therewith optional addressable individual information groups LG_nm1. . . LG_nmr, which may be addressed/pointed therewith pointer/address PP_nm1;

[0115] FIG. 66B is a schematic representation of the addressable response information group RG_nmhaving the addressable individual information groups LG_nm1. . . LG_nmrshowing the optional addressable pointer/address indices IN_nm1. . . IN_nmrcorrespondingly associated therewith the optional addressable individual information groups LG_nm1. . . LG_nmr, which may be addressed/pointed therewith the pointer/address PP_nm2;

[0116] FIG. 66C is a schematic representation of the addressable response information group RG_nmhaving the addressable individual information groups LG_nm1. . . LG_nmrshowing the optional addressable pointer/address indices IN_nm1. . . IN_nmrcorrespondingly associated therewith the optional addressable individual information groups LG_nm1. . . LG_nmr, which may be addressed/pointed therewith the pointer/address PP_nmr;

[0117] FIG. 67 is a schematic representation of the individual information groups LG_nm1. . . LG_nmrhaving corresponding optional links LD_nm1. . . LD_nmr, and/or corresponding optional descriptions DD_nm1. . . DD_nmr, and/or corresponding optional prices/values PD_nm1. . . PD_nmr, and/or corresponding optional images ID_nm1. . . ID_nmr;

[0118] FIG. 68 is a schematic representation of a labelled individual information group LL_nmr;

[0119] FIG. 69 is a schematic representation of an addressable query information group GI_nz;

[0120] FIG. 70 is a schematic representation of steps of a client-server multitasking process of the present invention;

[0121] FIG. 71 is a schematic representation of a multitasking process of deriving the service and/or information response IR_nand/or the user service and/or information response ir_n, with reference to FIGS. 59 and 63;

[0122] FIG. 72 is a schematic representation of a multitasking process of deriving the service and/or information response IR_nand/or the user service and/or information response ir_nhaving other grouping/sorting that may be used additionally and/or alternatively to that of FIGS. 59 and 63, as shown with reference to FIGS. 60 and 64;

[0123] FIG. 73 is a schematic representation of a step of the multitasking process of FIGS. 71 and 72 shown in more detail;

[0124] FIG. 74 is a schematic representation of another step of the multitasking process of FIG. 71 shown in more detail;

[0125] FIG. 75 is a schematic representation of another step of the multitasking process of FIG. 72 shown in more detail;

[0126] FIG. 76 is a schematic representation of user review of user response UR_nand/or selection of additional services and/or information;

[0127] FIG. 77 is a schematic representation of the user input UI_nthereinto the service and/or information entry request form IE_n;

[0128] FIG. 78 is a schematic representation of the service and/or information entry request form IE_nshowing fields, links, and elements of the service and/or information entry request form IE_n;

[0129] FIG. 79 is a schematic representation of a completed service and/or information entry request form IF_nshowing typical elements, values, and field names;

[0130] FIG. 80 is a schematic representation of the completed service and/or information entry request form IF_n, a user service and/or information request iq_n, and the client C_nof the client-server multitasking system;

[0131] FIG. 81 is a schematic representation of the user service and/or information request iq_n;

[0132] FIG. 82 is a schematic representation of the service and/or information request IQ_n;

[0133] FIG. 83 is an alternate schematic representation of the user service and/or information request iq_nof FIG. 81;

[0134] FIG. 84 is an alternate schematic representation of the service and/or information request IQ_nof FIG. 82;

[0135] FIG. 85 is a more detailed schematic representation of the service and/or information request IQ_nof FIGS. 82 and 84 showing typical field names and values;

[0136] FIG. 86 is an alternate more detailed schematic representation of the service and/or information request IQ_nof FIGS. 82 and 84;

[0137] FIG. 87 is a schematic representation showing queries QQ_n1. . . QQ_nmand corresponding server addresses AQ_n1. . . AQ_nm;

[0138] FIG. 88 shows the schematic representation of FIG. 87 having typical values;

[0139] FIG. 89 shows the schematic representation of FIG. 87 having other typical values;

[0140] FIG. 90 shows the schematic representation of FIG. 87 having other typical values;

[0141] FIG. 91 shows the schematic representation of FIG. 87 having other typical values;

[0142] FIG. 92 is a schematic representation of information that may be used for formulating a typical particular one of the requests Q_n1. . . Q_nm, designated as the request Q_nm, and optional instructions VJ_nm1. . . VJ_nkfrom the particular service and/or information request IQ_nand opening a connection OC_nm;

[0143] FIG. 93 is a schematic representation of information that may be used for formulating the typical particular one of the requests Q_n1. . . Q_nm, designated as the request Q_nm, and the optional instructions VJ_nm1. . . VJ_nkfrom the particular user service and/or information request iq_nand opening the connection OC_nm;

[0144] FIG. 94 is an alternate schematic representation of information that may be used for formulating the typical particular one of the requests Q_n1. . . Q_nm, designated as the request Q_nm, and optional instructions VJ_nm1. . . VJ_nkfrom the particular service and/or information request IQ_nand opening a connection OC_nmof FIG. 92;

[0145] FIG. 95 is an alternate schematic representation of information that may be used for formulating the typical particular one of the requests Q_n1. . . Q_nm, designated as the request Q_nm, and the optional instructions VJ_nm1. . . VJ_nkfrom the particular user service and/or information request iq_nand opening the connection OC_nmof FIG. 93;

[0146] FIG. 96 is a schematic representation of queries QQ_n1. . . QQ_nm, corresponding server addresses AQ_n1. . . AQ_nm, and optional instructions VJ_nm1. . . VJ_nkthat may be parsed, processed, and/or formatted from the service and/or information request IQ_nand/or the user service and/or information request iq_n;

[0147] FIG. 97 is a schematic representation of a request pointer/address group QZ_ns, having a particular one of query pointer/address groups QG_n1. . . QG_nz, designated as the query pointer/address group QG_nz, associated ones of the addressable response information groups RG_n1. . . RG_nm, the pointers/addresses PP_n11. . . PP_nmr, and the query information group GI_nzassociated therewith the query pointer/address group QG_nz;

[0148] FIG. 98 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 GI_nzassociated therewith the query pointer/address group QG_nz;

[0149] FIG. 99 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 GI_nzassociated therewith the query pointer/address group QG_nz;

[0150] FIG. 100 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. 98, having typical ones of queries QQ_n1. . . QQ_nzand corresponding server addresses AQ_n1. . . AQ_nzassociated therewith;

[0151] FIG. 101 is another schematic representation of the typical ones of the query pointer/address groups QG_n1. . . QG_nzhaving the sorting criteria addressing scheme of FIG. 98, having the typical ones of the of queries QQ_n1. . . QQ_nzand the corresponding ones of the server addresses AQ_n1. . . AQ_nzof FIG. 100 associated therewith;

[0152] FIG. 102 is a generic schematic representation of the query pointer/address groups QG_n1. . . QG_nz, having the sorting criteria addressing scheme of FIG. 98, having the ones of queries QQ_n1. . . QQ_nzand the corresponding ones of the server addresses AQ_n1. . . AQ_nzassociated therewith;

[0153] FIG. 103 is a schematic representation of a request Q_nmof the client-server multitasking system;

[0154] FIG. 104 is a schematic representation of a response R_nmof the client-server multitasking system;

[0155] FIG. 105 is a schematic representation of an entity body RH_nmof the response R_nmof FIG. 104 having optional response individual information groups LS_nm1. . . LS_nmr, and/or optional information LI_nm;

[0156] FIG. 106 is a schematic representation of the addressable response information group RG_nmhaving the addressable individual information groups LG_nm1. . . LG_nmrparsed, and/or processed, and/or formatted, and/or organized, and/or grouped thereinto the addressable response information group RG_nmtherefrom the optional entity body RH_nmof FIG. 105;

[0157] FIG. 107 is a schematic representation of the optional response individual information group LS_nmrparsed, and/or processed, and/or formatted, and/or organized, and/or grouped thereinto the addressable individual information group LG_nmr;

[0158] FIG. 108 is a schematic representation of the optional links LD_nm1. . . LD_nmr, and/or the optional descriptions DD_nm1. . . DD_nmr, and/or the optional prices/values PD_nm1. . . PD_nmr, and/or the optional images ID_nm1. . . ID_nmrparsed individually and/or separately, and incorporated thereinto the addressable response information group RG_nmtherefrom the optional entity body RH_nm;

[0159] FIG. 109 is a schematic representation of a typical one of the addressable query information group GI_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_nz1. . . RL_nzx, the optional query description QT_nz, the optional server descriptions and/or links ST_nz1. . . ST_nzf, and the optional advertisements and/or links LT_nz1. . . LT_nztincorporated thereinto certain typical ones of the typical service and/or information response forms IS_nof FIGS. 27A-52C, inclusive;

[0160] FIG. 110 is a another schematic representation of a typical one of the addressable query information group GI_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_nz1. . . RL_nzx, the optional query description QT_nz, the optional server descriptions and/or links ST_nz1. . . ST_nzfand the optional advertisements and/or links LT_nz1. . . LT_nztincorporated thereinto certain typical ones of the typical service and/or information response forms IS_nof FIGS. 27A-52C, inclusive.

[0161] The preferred embodiments of the present invention will be described with reference to FIGS. 1-110 of the drawings. Identical elements in the various figures are identified with the same reference alphanumerics.

[0162] A. Overview

[0163] 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_n(14), corresponding clients C₁. . . C_n(16), server PS (18), servers S₁. . . S_z(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₁. . . C_n(16) therethrough the corresponding user interfaces I₁. . . I_n(14).

[0164] Each of the users U₁. . . U_n(12) enter corresponding user inputs UI₁. . . UI_n(25) having one or more same and/or different user requests qu₁₁. . . qu_nu(26) thereinto the corresponding user interfaces I₁. . . I_n(14), as shown in FIG. 3. The user requests qu₁₁. . . qu_nu(26) are communicated from the user interfaces I₁. . . I_n(14) to the corresponding clients C₁. . . C_n(16) within corresponding user service and/or information requests iq₁. . . iq_n(27), having the user requests qu₁₁. . . 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.

[0165] Each of the user interfaces I₁. . . I_n(14) communicate the user service and/or information requests iq₁. . . iq_n(27) thereto the corresponding clients C₁. . . C_n(16), which optionally format the corresponding user service and/or information requests iq₁. . . iq_n(27) into corresponding service and/or information requests IQ₁. . . IQ_n(28), as required. Each of the service and/or information requests IQ₁. . . IQ_n(28) have information therein that may be used to formulate one or more same and/or different requests Q₁₁. . . Q_nm(29) to be made of one or more of the same and/or different ones of the servers S₁. . . S_z(20), which may hereinafter be called server designations S₁₁. . . 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 Q₁₁. . . Q_nm(29) as the corresponding server designations S₁₁. . . S_nm(30), as shown in FIGS. 2 and 4. FIG. 4 shows the server designations S₁₁. . . S_nm(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₁₁. . . 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.

[0166] Each of the service and/or information requests IQ₁. . . IQ_n(28) may be communicated thereto the server PS (18), which parses, processes, and/or formats the service and/or information requests IQ₁. . . IQ_n(28) into the requests Q₁₁. . . Q_nm(29).

[0167] The corresponding clients C₁. . . C_n(16) may also and/or alternatively optionally parse, process, and/or format the corresponding user service and/or information requests iq₁. . . iq_n(27) into one or more of the same and/or different requests Q₁₁. . . 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₁₁. . . S_nm(30), as required.

[0168] Certain ones of the clients C₁. . . C_n(16) may communicate corresponding certain ones of the service and/or information requests IQ₁. . . 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₁. . . IQ_n(28) into certain ones of the requests Q₁₁. . . Q_nm(29), as required, and communicates the certain ones of the requests Q₁₁. . . 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₁₁. . . S_nm(30).

[0169] Alternate ones of the clients C₁. . . C_n(16) may communicate corresponding alternate ones of the requests Q₁₁. . . Q_nm(29) to corresponding alternate ones of the servers S₁. . . S_z(20), in accordance with the designation scheme corresponding to the corresponding alternate ones of the server designations S₁₁. . . S_nm(30).

[0170] Other alternate ones of the clients C₁. . . C_n(16) may communicate corresponding other alternate ones of the service and/or information requests IQ₁. . . IQ_n(28) to the server PS (18), which parses, processes and/or formats the other alternate ones of the service and/or information requests IQ₁. . . 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_nm(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₁. . . C_n(16) may also parse, process, and/or format the user service and/or information requests iq₁. . . iq_n(27) into one or more of the same and/or different yet other alternate ones of the requests Q₁₁. . . Q_nm(29), and communicate the yet other alternate ones of the requests Q₁₁. . . Q_nm(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_nm(30).

[0171] Each of the service and/or information requests IQ₁. . . IQ_n(28) may, thus, be communicated therefrom the corresponding clients C₁. . . C_n(16) to the server PS (18). The requests Q₁. . . Q_nm(29) may be communicated therefrom the server PS (18) and/or therefrom the corresponding clients C₁. . . C_n(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 I₁. . . I_n(14) and/or the corresponding clients C₁. . . C_n(16), and/or information generated by the server PS (18) and/or the servers S₁. . . S_z(20), and/or ancillary instructions, a combination thereof, and/or other suitable means.

[0172] Each of the servers S₁. . . S_z(20) corresponding to the designation scheme S₁₁. . . S_nm(30) replies to the server PS (18) and/or the clients C₁. . . C_n(16), accordingly, and communicates corresponding responses R₁₁. . . R_nm(32), associated with the requests Q₁₁. . . Q_nm(29), to the server PS (18) and/or the clients C₁. . . C_n(16) making the requests Q₁₁. . . Q_nm(29), as shown in FIG. 2 for typical ones of the requests Q₁₁. . . Q_nm(29) and the corresponding responses R₁₁. . . R_nm(32).

[0173] The server PS (18) and/or the appropriate clients C₁. . . C_n(16) parse, process, format, sort, group, and/or organize the responses R₁₁. . . R_nm(32) into corresponding service and/or information responses IR₁. . . IR_n(34), having corresponding parsed, processed, formatted, sorted, grouped, and/or organized service and/or information groups G₁. . . G_n(35) (shown later in FIGS. 27A-52C, inclusive) acceptable to the corresponding clients C₁. . . C_n(16) and the corresponding respective user interfaces I₁. . . I_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).

[0174] 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 I₁. . . I_n(14). The user interfaces I₁. . . I_n(14) incorporate the user service and/or information responses ir₁. . . ir_n(36) into corresponding user responses UR₁. . . UR_n(37), which are derived at the user interfaces I₁. . . I_n(14), and communicated by the user interfaces I₁. . . I_n(14) thereto the corresponding users U₁. . . U_n(12). The users U₁. . . U_n(12) review the corresponding user responses UR₁. . . UR_n(37) at the user interfaces I₁. . . I_n(14) and/or select additional services and/or information therefrom.

[0175] B. Typical Service and/or Information Entry Request Forms

[0176] FIGS. 5A, 5B, and 6-10 show typical ones of service and/or information entry request forms IE₁. . . IE_n(38) at the user interfaces I₁. . . I_n(14), which the users U₁. . . U_n(12) may communicate typical ones of the user inputs UI₁. . . UI_n(25) thereinto, as requests for information and/or services. The typical ones of the service and/or information entry request forms IE₁. . . IE_n(38) at the user interfaces I₁. . . I_n(14) shown in FIGS. 5A, 5B, and 6-10 are typical examples of the service and/or information entry request forms IE₁. . . IE_n(38) at the user interfaces I₁. . . I_n(14), a much larger variety of which is possible. Names and/or links and/or other information are incorporated therein the typical ones of the service and/or information entry request forms IE₁. . . IE_n(38) shown in FIGS. 5A, 5B, and 6-10 for illustrative purposes, and are not intended to limit the large variety of the service and/or information entry request forms IE₁. . . 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 IE₁. . . IE_n(38) at the user interfaces I₁. . . I_n(14).

[0177] C. Typical Completed Service and/or Information Entry Request Forms

[0178] FIGS. 11-26 show typical ones of completed service and/or information entry request forms IF₁. . . IF_n(230) at the user interfaces I₁. . . I_n(14).

[0179] FIG. 11 shows a typical particular one of the completed service and/or information entry request forms IF₁. . . IF_n(230), hereinafter designated the completed service and/or information entry request form IF_n(230), at a particular one of the user interfaces I₁. . . I_n(14), hereinafter designated the user interface I_n(14), having same and different ones of the typical queries QQ_n1. . . QQ_nm(53), different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52). Typical same ones of the typical queries QQ_n1. . . QQ_nm(53), are “Cat”, “Dog”, and “Mouse”, which are different one from the other.

[0180] FIG. 12 shows the typical completed service and/or information entry request forms IF_n(230), at the user interface I_n(14), having same and different ones of the typical queries QQ_n1. . . QQ_nm(53), different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52). Typical same ones of the typical queries QQ_n1. . . QQ_nm(53) are “Cat”, “Dog”, and “Mouse”, which are different one from the other. Typical same ones of the 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_n1. . . VJ_nk(52) have 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 I_n(14) having 5 “URL's per Search Engine”, rather than 10 “URL's per Search Engine”, as instructed in FIG. 11.

[0181] FIG. 13 shows the typical completed service and/or information entry request forms IF_n(230), at the user interface I_n(14) having a single typical one of the typical queries QQ_n1. . . QQ_nm(53) as “Big Elephants”.

[0182] FIGS. 14A, 14B, and 14C show the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14), having same and different ones of the typical queries QQ_n1. . . QQ_nm(53), different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52), showing “Current Group” as “Group I”, “Group II”, and “Group III”, in FIGS. 14A, 14B, and 14C, respectively. Typical same ones of the typical queries QQ_n1. . . QQ_nm(53) are “Catcher in the Rye”, “Catcher”, “Rye”, “Sports”, and “Rye Bread”, which are different one from the other. The typical server addresses AQ_n1. . . AQ_nm(54) are different one from the other. The typical optional instructions VJ_n1. . . VJ_nk(52) have a 5 second “Timeout (seconds) per Search Engine”, rather than a 3 second “Timeout (seconds) per Search Engine” as in FIGS. 11-13. 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 I_n(14) within a period of less than the “Timeout (seconds) per Search Engine” specified in the typical optional instructions VJ_n1. . . 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 U₁(12) to specify in the event of slow ones of the responses R_n1. . . R_nm(32) from certain ones of the servers S₁. . . S_z(20).

[0183] FIG. 15 shows the typical completed service and/or information entry request forms IF_n(230), at the user interface I_n(14), having same and different ones of the typical queries QQ_n1. . . QQ_nm(53), different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52). Typical same ones of the typical queries QQ_n1. . . QQ_nm(53) are “Charles Dickens”, “A Tale of Two Cities”, and “Oliver Twist”, which are different one from the other. All blank entries beneath the entry above take on the characteristics of the completed entry above. Therefore, Searches 2, 3, and 4 take on the typical queries QQ_n2. . . QQ_n4(53) of “Charles Dickens” of Search 1, above. Likewise, Searches 7, 8, and 9 take on the typical queries QQ_n7. . . QQ_n9(53) of “Oliver Twist” of Search 6, above. Search 5 takes on the typical query QQ_n5(53) of “A Tale of Two Cities”.

[0184] The typical optional instructions VJ_n1. . . VJ_nk(52) of FIG. 15 have “Separate”, 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 I_n(14) in separate groups, i.e., grouped by the typical server addresses AQ_n1. . . AQ_nm(54), rather than interleaved one with the other, as instructed in FIGS. 11-14.

[0185] The typical optional instructions VJ_n1. . . VJ_nk(52) “Interleaved” of FIGS. 11-14 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 I_n(14) having information and/or services therein the responses R_n1. . . R_nm(32) to be interleaved one with the other (or alternating one with the other) therein the appropriate addressable query information groups GI_n1. . . GI_nz(63). The labelled individual information groups LL_n11. . . LL_nzu(86) therein the addressable query information groups GI_n1. . . GI_nz(63) are alternatingly interleaved one with the other and labelled and/or identified and associated correspondingly therewith the responses R_n1. . . R_nm(32) therefrom the servers S₁. . . S_z(20). The “Interleaved” information and/or services may typically be incorporated therein the appropriate addressable query information groups GI_n1. . . GI_nz(63) in substantially the same sequence as the information and/or services are therein the responses R_n1. . . 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.

[0186] The typical server addresses AQ_n1. . . AQ_nm(54) are different one from the other in FIG. 15. The typical optional instructions VJ_n1. . . VJ_nk(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 IS_n(39) at the user interface I_n(14) having 5 “Searches per Group”, rather than 3 “Searches per Group”, as in FIGS. 11-14. The typical optional instructions VJ_n1. . . VJ_nk(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 IS_n(39) at the user interface I_n(14) having 8 “URL's per Search Engine”.

[0187] FIG. 16 shows the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14), having the same ones of the typical queries QQ_n1. . . QQ_nm(53), different ones of the typical server addresses AQ _n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52). The typical optional instructions VJ_n1. . . VJ_nk(52) have “URL Details” as “List”, 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 I_n(14) “List” format rather than “Summary” format, as instructed in FIGS. 11-15. The “URL Details” as “Summary” instruct the client C_n(16) and/or the server PS (18) to return the typical user response UR_n(37) showing descriptions and/or other information and/or services, in addition to links, therein the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), while “URL Details” as “List” instruct the client C_n(16) and/or the server PS (18) to return the typical user response UR_n(37) showing only links therein the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14).

[0188] The typical optional instructions VJ_n1. . . VJ_nk(52) have 25 “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 I_n(14) having 25 “URL's per Search Engine”. The typical optional instructions VJ_n1. . . VJ_nk(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 IS_n(39) at the user interface I_n(14) having 9 “Searches per Group”. The typical optional instructions VJ_n1. . . VJ_nk(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 IS_n(39) at the user interface I_n(14) at “Page” 3 of the “Current Group”, rather than “Page” 1 of the “Current Group”, as in FIGS. 11-15. The typical optional instructions VJ_n1. . . VJ_nk(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 IS_n(39) at the user interface I_n(14) to use a 2 second “Timeout (seconds) per Search Engine”.

[0189] FIG. 17 shows another one of the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14), having the same ones of the typical queries QQ_n1. . . QQ_nm(53), different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52). The typical optional instructions VJ_n1. . . 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 IS_n(39) at the user interface I_n(14) having 18 “URL's per Search Engine”. The typical optional instructions VJ_n1. . . VJ_nk(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 IS_n(39) at the user interface I_n(14) at “Group” 2, having 4 “Searches per Group”, at “Page” 2 of the “Current Group”, with a 2 second “Timeout (seconds) per Search Engine”, and to return the results “Separately”.

[0190] FIG. 18 shows another one of the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14), having different ones of the typical queries QQ_n1. . . QQ_nm(53), different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52).

[0191] FIG. 19 shows another one of the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14), having different ones of the typical queries QQ_n1. . . QQ_nm(53), as in FIG. 18, the same ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52).

[0192] FIG. 20 shows the typical completed service and/or information entry request forms IF_n(230), at the user interface I_n(14) having a single typical one of the typical queries QQ_n1. . . QQ_nm(53) as “sports”.

[0193] FIG. 21 show another one of the typical completed service and/or information entry request forms IF_n(230), at the user interface I_n(14) having a single typical one of the typical queries QQ_n1. . . QQ_nm(53) as “television”.

[0194] FIG. 22 shows another one of the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14), having different ones of the typical queries QQ_n1. . . QQ_nm(53), .i.e., “sports” and “television”, different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52).

[0195] FIG. 23 shows another one of the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14), having the same ones of the typical queries QQ_n1. . . QQ_nm(53), i.e., “weather”, different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52).

[0196] FIG. 24 shows another one of the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14), having different ones of the typical queries QQ_n1. . . QQ_nm(53), .i.e., “education”, “universities,” and “training”, different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52).

[0197] FIG. 25 shows another one of the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14), having different ones of the typical queries QQ_n1. . . QQ_nm(53), .i.e., “weather”, “climate,” and “training”, different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52).

[0198] FIG. 26 shows another one of the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14) having a single typical one of the typical queries QQ_n1. . . QQ_nm(53) as “weather”.

[0199] The typical ones of the completed service and/or information entry request forms IF₁. . . IF_n(230) at the user interfaces I₁. . . I_n(14) shown in FIG. 11-26 are typical examples of the completed service and/or information entry request forms IF₁. . . IF_n(230) at the user interfaces I₁. . . I_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_n1. . . VJ_nk(52) therein the typical ones of the completed service and/or information entry request forms IF₁. . . IF_n(230) at the user interfaces I₁. . . I_n(14) shown in FIG. 11-26 are typical examples for illustrative purposes, and are not intended to limit the substantially infinite variety of the queries QQ_n1. . . QQ_nm(53), the server addresses AQ_n1. . . AQ_nm(54), and the optional instructions VJ_n1. . . VJ_nk(52) that may be entered thereinto the service and/or information entry request forms IE₁. . . IE_n(38), to derive the completed service and/or information entry request forms IF₁. . . IF_n(230) at the user interfaces I₁. . . I_n(14). Likewise, names and/or links and/or other information are incorporated therein the typical ones of the completed service and/or information entry request forms IF_n. . . IF_n(230) shown in FIGS. 11-26 for illustrative purposes, and are not intended to limit the large variety of the completed service and/or information entry request forms IF₁. . . 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 IF₁. . . IF_n(230) at the user interfaces I₁. . . I_n(14).

[0200] Any ones of the typical queries QQ_n1. . . 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_n1. . . VJ_nk(52) may be incorporated thereinto the typical ones of service and/or information entry request forms IE₁. . . IE_n(38) at the user interfaces I₁. . . I_n(14) of FIGS. 5A, 5B, and 6-10, 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 I₁. . . I_n(14) of FIGS. 11-26

[0201] 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₁. . . IE_n(38) at the user interfaces I₁. . . I_n(14) of FIGS. 5A, 5B, and 6-10, 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 I₁. . . I_n(14) of FIGS. 11-26.

[0202] The users U₁. . . U_n(12), for example, may enter: the typical queries QQ_n1. . . 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_n1. . . 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 forms IE₁. . . IE_n(38) at the user interfaces ₁1 . . . I_n(14) of FIGS. 5A, 5B, and 6-10, 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 I₁. . . I_n(14). The typical ones of the user responses UR₁. . . UR_n(37), as typical service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14), may then be communicated thereto the corresponding ones of the users U₁. . . U_n(12), accordingly. FIGS. 27A-52C, inclusive, show typical ones of the user responses UR₁. . . UR_n(37), as the typical service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14), which may be communicated thereto the corresponding ones of the users U₁. . . U_n(12). The scope of the client-server multitasking system 10 of the 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 of the multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104 by example.

[0203] D. Typical Service and/or Information Response Forms

[0204] FIGS. 27A-52C, inclusive, show typical ones of the user responses UR₁. . . UR_n(37), as typical service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14), which may be communicated thereto the corresponding ones of the users U₁. . . U_n(12). A typical particular one of the user responses UR₁. . . UR_n(37), as a particular typical one of the service and/or information response forms IS₁. . . IS_n(39) at the particular one of the user interfaces I₁. . . I_n(14) may hereinafter be designated as the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14).

[0205] FIGS. 27A-52C, inclusive, also show information therein each of the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), pertaining to the “Current Group”, the “Previous Group”, if appropriate, the “Next Group”, if appropriate, and each “Group” by alphanumerics. FIGS. 27A-52C, inclusive, also show information therein each of the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interfaces I_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.

[0206] FIGS. 27A-29C, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 11, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group I, Group II, and Group III, respectively.

[0207] The user U_n(12) may optionally select Group II, and/or Group III therefrom the typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14) of FIGS. 27A-27C, and/or Group I and/or Group III at the user interface I_n(14) of FIGS. 28A-28C, and/or Group I, and/or Group II at the user interface I_n(14) of FIGS. 29A-29C. 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 of the service and/or information entry request form IE_n(38) at the user interfaces I₁. . . I_n(14), and completing the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14) therewith the appropriate selections to be made.

[0208] The user U_n(12) may also make other selections by entering such into the typical one of the service and/or information entry request form IE_n(38) at the user interfaces I₁. . . I_n(14), and completing the typical completed service and/or information entry request form IF_n(230), at the user interface I_n(14) therewith the appropriate selections to be made, and/or by making such selections therethrough the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(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.

[0209] FIGS. 27A-29C, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), having the service and/or information group G_n(35) having the addressable query information groups GI_n1. . . GI_nz(63) therein, the labelled individual information groups LL_n11. . . LL_nzu(86) therein the addressable query information groups G_n1. . . G_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 of the typical queries QQ_n1. . . QQ_nm(53), different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52).

[0210] FIGS. 27A-29C, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), resulting from the typical ones of the queries QQ_n1. . . QQ_nm(53), “Cat”, “Mouse”, and “Dog”, the same ones of the typical queries QQ_n1. . . QQ_n3(53) and QQ_n9(53) being “Cat”, other same ones of the typical queries QQ_n4(53) and QQ_n7(53) being “Mouse”, but different from “Cat”, and other same ones of the typical queries QQ_n5, QQ_n6(53), and QQ_n8(53) being “Dog”, but different from “Cat” and/or “Mouse”, the typical ones of the queries QQ_n1. . . QQ_nm(53), “Cat”, “Dog”, and “Mouse”, being different one from the other.

[0211] The typical same ones of the typical queries QQ_n1. . . QQ_n3(53) as “Cat” are incorporated thereinto the addressable query information groups GI_n1(63) of Group I.

[0212] The typical one of the queries QQ_n4(53) as “Mouse” is incorporated thereinto the addressable query information groups GI_n1(63) of Group II. The other same ones of the typical queries QQ_n5and QQ_n6(53) as “Dog are incorporated thereinto the addressable query information groups GI_n2(63) of Group II.

[0213] The typical one of the queries QQ_n7(53) as “Mouse” is incorporated thereinto the addressable query information groups GI_n1(63) of Group III. The typical one of the queries QQ_n8(53) as “Dog” is incorporated thereinto the addressable query information groups GI_n2(63) of Group III. The typical one of the queries QQ_n9(53) as “Cat” is incorporated thereinto the addressable query information groups GI_n3(63) of Group III.

[0214] FIGS. 27A-29C, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 11 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. 27A-29C, inclusive.

[0215] The typical optional instructions VJ_n1. . . 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 I_n(14) having substantially “10” ones of the typical labelled individual information groups LL_n11. . . LL_nzu(86) per each one of the typical server addresses AQ_n1. . . AQ_nm(54) in the typical “Current Group”, retrieved therefrom the responses R_n1. . . R_nm(32). I_nthis case, the typical labelled individual information groups LLn_n11. . . LL_nzu(86) may be “Uniform Resource Locators”, or “URL's” and/or other services and/or information associated therewith.

[0216] The typical optional instructions VJ_n1. . . 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 IS_n(39) at the user interface I_n(14) having “3 Searches per Group” for the group selected, which is designated in the typical optional instructions VJ_n1. . . VJ_nk(52) having “Group” as “1”.

[0217] “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_n1. . . AQ_n3(54) of “WebCrawler”, “Altavista”, and “Lycos”.

[0218] 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 I_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 IS_n(39) at the user interface I_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 information response form IS_n(39) at the user interface I_n(14).

[0219] The typical optional instructions VJ_n1. . . 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”.

[0220] The actual number of the typical “URL's per Group” may vary from the number of the “URL's per Search Engine” multiplied by the number of the “Searches per Group”, as duplicate ones of the “URL's” and/or other services and/or information associated therewith may typically be optionally discarded.

[0221] 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 I_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”.

[0222] 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 I_n(14). If the “Next Page” is selected, then the next” 10 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 IS_n(39) at the user interface I_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 IS_n(39) at the user interface I_n(14).

[0223] The typical optional instructions VJ_n1. . . 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 IS_n(39) at the user interface I_n(14) having ones of the typical labelled individual information groups LL_n11. . . 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_n1. . . AQ_nm(54) in the typical “Current Group”, portions of which have been retrieved therefrom the responses R_n1. . . R_nm(32), interleaved one with the other (or alternating one with the other) therein the appropriate addressable query information groups GI_n1. . . G_nz(63). The “Interleaved” information and/or services may typically be incorporated therein the appropriate addressable query information groups GI_n1. . . GI_nz(63) therein the “Current Group” in substantially the same sequence as the information and/or services are therein the responses R_n1. . . 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 information groups LL_n11. . . LL_nzu(86) may be “Uniform Resource Locators”, or “URL's” and/or other services and/or information associated therewith.

[0224] “Separate” 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 I_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 I_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 GI_n1. . . GI_nz(63) therein the “Current Group”.

[0225] The typical optional instructions VJ_n1. . . 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_n(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 of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14).

[0226] “List” 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 I_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 I_n(14) typically showing only links to URL's and/or other links therein the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14).

[0227] 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 I_n(14) within a period of less than the “Timeout (seconds) per Search Engine” specified in the typical optional instructions VJ_n1. . . 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 U₁(12) to specify in the event of slow ones of the responses R_n1. . . R_nm(32) from certain ones of the servers S₁. . . S_z(20).

[0228] If the time it takes to retrieve information from certain ones of the servers S₁. . . S_z(20) having the typical ones of the queries QQ_n1. . . QQ_nm(53) at the typical ones of the 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 of the non-responding certain ones of the servers S₁. . . S_z(20), as shown later in FIGS. 44A-44C. Information and/or services only from those ones of the servers S₁. . . S_z(20) responding within the “Timeout” period are then incorporated thereinto the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14).

[0229] FIGS. 30A-32B, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 12, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group I, Group II, and Group III, respectively.

[0230] FIGS. 30A-32B, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), having the service and/or information group G_n(35) having the addressable query information groups GI_n1. . . GI_nzu(63) therein, the labelled individual information groups LL_n1. . . LL_nzu(86) therein the addressable query information groups GI_n1. . . 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 of the typical queries QQ_n1. . . QQ_nm(53), and the same and different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52), rather than results just from different ones of the typical server addresses AQ_n1. . . AQ_nm(54) as in FIGS. 27A-29C, inclusive.

[0231] FIGS. 30A-32B, inclusive, show the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), resulting from the typical ones of the queries QQ_n1. . . QQ_nm(53), “Cat”, “Dog”, and “Mouse”, the same ones of the typical queries QQ_n1, QQ_n3(53), and QQ_n9(53) being “Cat”, other same ones of the typical queries QQ_n2(53), QQ_n5(53), QQ_n6(53), and QQ_n8(53) being “Dog”, but different from “Cat”, and other same ones of the typical queries QQ_n4and QQ_n7(53) being “Mouse”, but different from “Cat” and/or “Dog”, the typical ones of the queries QQ_n1. . . QQ_nm(53), “Cat”, “Dog”, and “Mouse”, being different one from the other.

[0232] FIGS. 30A-32B, inclusive, also show the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), resulting from the typical ones of the server addresses AQ_n1. . . AQ_nm(54), “HotBot”, “WebCrawler”, “Yahoo”, “LookSmart”, and “Dejanews”, the same ones of the typical server addresses AQ_n1and AQ_n2(54) being “HotBot”, other same ones of the typical server addresses AQ_n3. . . AQ_n5(54), being “WebCrawler”, but different from “HotBot”, another one of the server addresses AQ_n6(54), being “Yahoo”, but different from “HotBot” and/or “WebCrawler”, another one of the server addresses AQ_n7(54), being “LookSmart”, but different from “HotBot” and/or “WebCrawler” and/or “Yahoo”, and other same ones of the 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 of the server addresses AQ_n1. . . AQ_nm(54), “HotBot”, “WebCrawler”, “Yahoo”, “LookSmart”, and “Dejanews”, being different one from the other.

[0233] The typical same ones of the typical queries QQ_n1and QQ_n3(53) as “Cat” are incorporated thereinto the addressable query information groups GI_n1(63) of Group I. The typical one of the queries QQ_n2(53) as “Cat” is incorporated thereinto the addressable query information groups GI_n2(63) of Group II.

[0234] The typical one of the queries QQ_n4(53) as “Mouse” is incorporated thereinto the addressable query information groups GI_n1(63) of Group II. The other same ones of the typical queries QQ_n5and QQ_n6(53) as “Dog are incorporated thereinto the addressable query information groups Gl_n2(63) of Group II.

[0235] The typical one of the queries QQ_n7(53) as “Mouse” is incorporated thereinto the addressable query information groups GI_n1(63) of Group III. The typical one of the queries QQ_n8(53) as “Dog” is incorporated thereinto the addressable query information groups GI_n2(63) of Group III. The typical one of the queries QQ_n9(53) as “Cat” is incorporated thereinto the addressable query information groups GI_n3(63) of Group III.

[0236] FIGS. 30A-32B, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 12 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. 30A-32B, inclusive.

[0237] Now again, FIGS. 30A-32B, inclusive, show the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), resulting from the same and different ones of the typical queries QQ_n1. . . QQ_nm(53), the same and different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . 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 I_n(14) having 5 “URL's per Search Engine”, rather than 10 “URL's per Search Engine”, as in FIGS. 27A-29C, inclusive.

[0238] FIGS. 33A-33C show a typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), with reference to FIG. 13, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group I, having the typical ones of the queries QQ_n1. . . QQ_nm(53) as “Big Elephants”. The user U_n(12) may optionally select Group II, and/or Group III therefrom the typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14) of FIGS. 33A-33C.

[0239] FIGS. 33A-33C show the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 13 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. Groups I and/or II may be selected therefrom the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface In (14) of FIGS. 33A-33C.

[0240] FIGS. 34A-36C, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIGS. 14A, 14B, and 14C, respectively, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group I, Group II, and Group III, respectively. FIGS. 34A-36C, inclusive, show the results “Interleaved”. Typical ones of links, prices, descriptions, savings, and shipping schedules are indicated for products in Group I. The prices may be compared, for example, one with the other for the same and/or different items, shipping schedules compared, and a decision can be made as to which items to order, as a result of the information provided therein the typical one of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14). Typical similar items may have the same and/or similar titles, such as for example in book titles, but publication dates, for example, and/or editions may be the same and/or different, and shipping schedules may be the same and/or different. Prices, and cost savings may be traded off against shipping schedules, packaging (i.e., for example, hardcover and/or soft cover), author, publisher, for example, and/or other factors important to the user U_n(12). The user U_n(12) may select the items and/or items to order therefrom such information that the user U_n(12) considers to be important. The user U_n(12) may place the order and/or orders directly therethrough the links and/or URL's therein the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14). The user U_n(12) may additionally and/or alternatively collect the order and/or orders therein a shopping cart and/or shopping carts associated with the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), and place the order and/or orders therethrough the client C_n(16) and/or the server PS (18).

[0241] Now again, FIGS. 34A-36C, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), having the service and/or information group G_n(35) having the addressable query information groups GIn₁. . . GI_nz(63) therein, the labelled individual information groups LL_n11. . . LL_nzu(86) therein the addressable query information groups GI_n1. . . 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 of the typical queries QQ_n1. . . QQ_nm(53), different ones of the typical server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52). Typical same ones of the typical queries QQ_n1. . . QQ_nm(53) are “Catcher in the Rye”, “Catcher”, “Rye”, “Sports”, and “Rye Bread”, which are different one from the other. The typical server addresses AQ_n1. . . AQ_nm(54) are different one from the other.

[0242] FIGS. 34A-36C, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIGS. 14A, 14B, and 14C having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “5”; “Page” as “1”; “Searches per Group as “3”; and “Group” as I, II, and III, respectively, for FIGS. 34A-36C, inclusive.

[0243] Now again, the typical optional instructions VJ_n1. . . VJ_nk(52) have a 5 second “Timeout (seconds) per Search Engine”, rather than a 3 second “Timeout (seconds) per Search Engine” as in FIGS. 27A-33C, inclusive. 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 I_n(14) within a period of less than the “Timeout (seconds) per Search Engine” specified in the typical optional instructions VJ_n1. . . 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 U₁(12) to specify in the event of slow ones of the responses R_n1. . . R_nm(32) from certain ones of the servers S₁. . . S_z(20).

[0244] FIGS. 37A-39C, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 15, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group I, Group II, and Group III, respectively. Links, Prices, descriptions, savings, and shipping schedules are indicated for products in Group I, and Group II. FIGS. 38A-38D show the results “Separately” for Group II, and FIGS. 39A-39C show the results “Interleaved” for Group II. Links, Prices, descriptions, savings, and shipping schedules are indicated for products in Groups I and II in FIGS. 37A-39C, inclusive.

[0245] FIGS. 37A-39C, inclusive, show typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 15 having: “Search Engine Results” as “Separate”; “URL's per Search Engine” as “8”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “1”; “Page” as “1”; “Searches per Group as “5”; and “Group” as I, II, and III, respectively for FIGS. 37A-39C, inclusive.

[0246] Now again, the typical optional instructions VJ_1n. . . VJ_nk(52) have “Separate”, 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 I_n(14) in separate groups, i.e., grouped by the typical server addresses AQ_n1. . . AQ_nm(54), rather than interleaved one with the other, as in FIGS. 27A-36C, inclusive.

[0247] FIGS. 40A-40M show a typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), with reference to FIG. 16, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto a single Group.

[0248] FIGS. 40A-40M show the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 16 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “25”; “URL Details” as “List”; “Timeout (seconds) per Search Engine” as “2”; “Page” as “3”; “Searches per Group as “9”; and “Group” as I. Groups I and/or II may be selected therefrom the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14) of FIGS. 40A-40M.

[0249] Now again, the “URL Details” as “Summary” instruct the client C_n(16) and/or the server PS (18) to return the typical user response UR_n(37) showing descriptions and/or other information and/or services, in addition to links, therein the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), as in FIGS. 27A-39C, inclusive, while “URL Details” as “List” instruct the client C_n(16) and/or the server PS (18) to return the typical user response UR_n(37) showing only links and/or URL's therein the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), as in FIGS. 40A-40M.

[0250] FIGS. 41A-41F show a typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), with reference to FIG. 17, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group II.

[0251] FIGS. 41A-41F show the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 17 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 of the user response UR_n(37), as the typical service and/or information response forms IS(39) at the user interface I_n(14) of FIGS. 41A-41F.

[0252] FIGS.42A-42O show a typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), with reference to FIG. 18, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto a single Group.

[0253] FIGS. 42A-42O show the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 18 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “25”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “5”; “Page” as “1”; “Searches per Group as “9”; and “Group” as “1”.

[0254] FIGS. 43A-43O show a typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), with reference to FIG. 19, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto a single Group.

[0255] FIGS. 43A-43O show the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 19 having: “Search Engine Results” as “interleave”; “URL's per Search Engine” as “25”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “9”; and “Group” as “1”.

[0256] FIGS. 44A-44C show a typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), with reference to FIG. 20, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group I. FIGS. 44A-44C also show the results of a “Timeout” occurring.

[0257] FIGS. 44A-44C show the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 20 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. Groups I and/or II may be selected therefrom the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14) of FIGS. 44A-44C.

[0258] FIGS. 45A-45C show a typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), with reference to FIG. 21, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group I.

[0259] FIGS. 45A-45C show the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 21 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. Groups I and/or II may be selected therefrom the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14) of FIGS. 45A-45C.

[0260] FIGS. 46A-46E show a typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), with reference to FIG. 22, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group I. FIGS. 46A-46E also show the links/advertisements/images automatically inserted thereinto the typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), which may be associated therewith the typical queries QQ_1n. . . QQ_nm(53). In the typical case shown in FIGS. 46A-46E, links/advertisements/images associated therewith the typical queries QQ_n1. . . QQ_nm(53) of “sports” and “television” have been automatically inserted thereinto the typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14).

[0261] FIGS. 46A-46E show the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 22 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “15”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “5”; and “Group” as “1”. Next Group: II may be selected therefrom the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14) of FIGS. 46A-46E.

[0262] FIGS. 47A-47C and 48A-48D show a typical ones of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 23, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group I. FIGS. 47A-47C and 48A-48D also show the results of a full text search of the optional database 41 and/or the optional database 42, which may be associated therewith the typical queries QQ_n1. . . QQ_nm(53), and which additionally and/or alternatively may function as an internal search engine. The full text search results are incorporated therefrom the additional optional responses RA_n1. . . RA_nm(40). The results of the full text search of the optional database 41 and/or the optional database 42 may be additionally and/or alternatively automatically inserted thereinto the typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), in addition to the typical queries QQ_n1. . . QQ_nm(53) at the typical ones of the server addresses AQ_n1. . . AQ_nm(54). In the typical case shown in FIGS. 47A-47C and 48A-48D, full text search results associated therewith the typical query QQ_n1. . . QQ_nm(53) of “weather” have been automatically inserted thereinto the typical ones of the user responses UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), in addition to the typical queries QQ_n1. . . QQ_nm(53) at the typical ones of the server addresses AQ_n1. . . AQ_nm(54). The typical full text search results start and end with “Hotlist: Weather Science” in FIGS. 47A-47C. The typical full text search results start with “Hotlist: Weather Science” and end with “search for: ‘weather’” in FIGS. 48A-48D.

[0263] FIGS. 47A-47C and 48A-48D show the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 23 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 “1”. Next Group: I and/or Group: III may be selected therefrom the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14) of FIGS. 47A-47C and 48A-48D.

[0264] FIGS. 49A-49I show a typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), with reference to FIG. 24, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group I. FIGS. 49A-49I also show the typical results of the server PS (18) and/or the client C_n(16) automatically optionally spidering the sites obtained as a result of the typical queries QQ_n1. . . QQ_nm(53) at the typical ones of the server addresses AQ_n1. . . AQ_nm(54), and incorporating the spidered results thereinto the optional database 41 and/or the optional database 42. The spidered results incorporated thereinto the optional database 41 and/or the optional database 42 may be searched as in FIGS. 47A-47C and 48A-48D with reference to FIG. 23 and/or based upon other ones of the typical queries QQ_n1. . . QQ_nm(53) at the typical ones of the server addresses AQ_n1. . . AQ_nm(54), and the full text search results may be obtained therefrom the additional optional responses RA_n1. . . RA_nm(40).

[0265] FIGS. 49A-49I also show the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 24 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 “1”. Next Group: I and/or Group: III may be selected therefrom the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14) of FIGS. 49A-491.

[0266] FIGS. 50A-50K show a typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), with reference to FIG. 25, having information and/or services therefrom the responses R_n1. . . R_nm(32) incorporated therein, and incorporated thereinto Group I. FIGS. 50A-50K also show the typical results of the server PS (18) and/or the client C_n(16) semi-automatically optionally spidering the sites obtained as a result of the typical queries QQ_n1. . . QQ_nm(53) at the typical ones of the server addresses AQ_n1. . . AQ_nm(54), and incorporating the spidered results thereinto the optional database 41 and/or the optional database 42. The spidered results incorporated thereinto the optional database 41 and/or the optional database 42 may also be searched as in FIGS. 47A-47C and 48A-48D with reference to FIG. 23 and/or based upon other ones of the typical queries QQ_n1. . . QQ_nm(53) at the typical ones of the server addresses AQ_n1. . . AQ_nm(54), and the full text search results may be obtained therefrom the additional optional responses RA_n1. . . RA_nm(40).

[0267] The user U_n(12) may optionally select those sites to be spidered and incorporated thereinto the optional database 41 and/or the optional database 42, as in the typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14) in FIGS. 50A-50K. FIGS. 51A-51G show the typical results of the server PS (18) and/or the client C_n(16) optionally spidering the sites obtained as a result of the typical queries QQ_n1. . . QQ_nm(53) at the typical ones of the server addresses AQ_n1. . . AQ_nm(54), and input resulting therefrom user selection of sites to be spidered therefrom FIGS. 50A-50K, and incorporating the spidered results thereinto the optional database 41 and/or the optional database 42.

[0268] The results of the optional spidering typically obtained therefrom the typical process used therewith FIGS. 50A-50K and 51A-51G may be substantially the same as the typical process used therewith FIGS. 49A-49I, if all the sites shown in FIGS. 50A-50K are selected for incorporation into the database 41 and/or the optional database 42. The typical process of FIGS. 49A-49I offers an automatic approach to constructing the optional database 41 and/or the optional database 42, and the typical process of FIGS. 50A-50K and 51A-51G offers the flexibility of weeding out and/or selecting sites to be incorporated thereinto the database 41 and/or the optional database 42.

[0269] FIGS. 50A-50K also show the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14), with reference to FIG. 25 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 “1”. Next Group: I and/or Group: III may be selected therefrom the typical one of the user response UR_n(37), as the typical service and/or information response forms IS_n(39) at the user interface I_n(14) of FIGS. 50A-50K.

[0270] FIGS. 52A-52C show a typical one of the user response UR_n(37), as the typical service and/or information response form IS_n(39) at the user interface I_n(14), with reference to FIG. 26, having information and/or services therefrom the additional optional responses RA_n1. . . RA_nm(40). FIGS. 52A-52C show the results solely of a full text search of the optional database 41 and/or the optional database 42, which may be associated therewith the typical queries QQ_n1. . . QQ_nm(53). The full text search results are incorporated therefrom the additional optional responses RA_n1. . . RA_nm(40). The typical full text search results start with “Hotlist: Weather Science” and end with “High Plains Climate Center Home Page”in FIGS. 52A-52C.

[0271] The typical ones of the user responses UR₁. . . UR_n(37), as typical service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14) shown in FIGS. 27A-52C, inclusive, are typical examples of the user responses UR₁. . . UR_n(37), as typical service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14), a much larger variety of which is possible. FIGS. 27A-52C, inclusive, illustrate typical examples of typical ones of the user responses UR₁. . . UR_n(37), as typical service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14) to the typical queries QQ_n1. . . QQ_nm(53), the typical ones of the server addresses AQ_n1. . . AQ_nm(54), and the typical optional instructions VJ_n1. . . VJ_nk(52) having been entered therein the typical ones of the completed service and/or information entry request forms IF₁. . . IF_n(230) at the user interfaces I₁. . . I_n(14) shown in FIGS. 11-26.

[0272] The typical examples of the typical ones of the user responses UR₁. . . UR_n(37), as typical service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14) are for illustrative purposes, and are not intended to limit the substantially infinite variety of the user responses UR₁. . . UR_n(37), as the service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14), the queries QQ_n1. . . QQ_nm(53), the server addresses AQ_n1. . . AQ_nm(54), and the optional instructions VJ_n1. . . VJ_nk(52) that may be entered thereinto the service and/or information entry request forms IE₁. . . IE_n(38), to derive the to the completed service and/or information entry request forms IF₁. . . IF_n(230), and which result in the user responses UR₁. . . UR_n(37), as the service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14). Likewise, names and/or links and/or other information are incorporated therein the typical ones of the user responses UR₁. . . UR_n(37), as the service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14), shown in FIGS. 27A-52C, inclusive, for illustrative purposes, and are not intended to limit the large variety of the user responses UR₁. . . UR_n(37), as the service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14), and the names and/or links and/or information that are possible, and that may be incorporated thereinto the user responses UR₁. . . UR_n(37), as the service and/or information response forms IS₁. . . IS_n(39) at the user interfaces I₁. . . I_n(14).

[0273] E. Optional Database

[0274] The server PS (18) and/or the clients C₁. . . C_n(16) may also incorporate corresponding additional optional responses RA₁₁. . . RA_nm(40) into the service and/or information responses IR₁. . . IR_n(34), which may be obtained by accessing optional databases 41 and/or 42, shown in FIGS. 53A and 53B, which may be optionally resident within the server PS (18) and/or the clients C₁. . . C_n(16), respectively.

[0275] The server PS (18) and/or the clients C₁. . . C_n(16) may optionally store the responses R₁₁. . . R_nm(32) communicated therefrom the servers S₁₁. . . S_z(20), in accordance with the designation scheme corresponding to the server designations S₁₁. . . 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₁₁. . . RA_nm(40).

[0276] 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 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 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 RA₁₁. . . RA_nm(40).

[0277] Each of the users U₁. . . U_n(12) may optionally communicate corresponding additional optional requests q₁₁. . . q_np(44) therethrough the corresponding user interfaces I₁. . . 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 IR₁. . . IR_n(34) and/or other information presented to and/or available and/or known to the users U₁. . . U_n(12) therethrough the corresponding user interfaces I₁. . . I_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_n(14) to the corresponding users U₁. . . U_n(12), as shown in FIG. 2 for typical ones of the requests q₁₁. . . q_np(44) and the corresponding responses r₁₁. . . r_np(46).

[0278] F. Additional Details

[0279] Now, in more detail, the clients C₁. . . C_n(16) and the servers S₁. . . S_z(20) reside on the network 24. The users U₁. . . U_n(12) and the corresponding clients C₁. . . C_n(16) communicate one with the other therethrough the corresponding user interfaces I₁. . . I_n(14). The user U₁(12), thus, communicates with the client C₁(16), one with the other, therethrough the user interface I₁(14); the user U₂(12), thus, communicates with the client C₂(16), one with the other, therethrough the user interface I₂(14); the user U_n(12), thus, communicates with the client C_n(16), one with the other, therethrough the user interface I_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 I_n(14), as best shown later in FIGS. 54-56. The user U_n(12) may be used to designate any one of the users U₁. . . U_n(12); the user interface I_n(14) may be used to designate any one of the user interfaces I₁. . . I_n(14); the client C_n(16) may be used to designate any one of the users clients C₁. . . C_n(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.

[0280] There may be n different or same the service and/or information requests IQ₁. . . IQ_n(28) present on the network 24 at any time. Each of the service and/or information requests IQ₁. . . IQ_n(28) may have one or more of the same and/or different requests Q₁₁. . . Q_nm(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 S₁₁. . . 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₁. . . IQ_n(28). Requests Q_n1. . . Q_nm(29) may be used to designate the particular requests Q₁₁. . . Q_nm(29) associated therewith and corresponding to the service and/or information request IQ_n(28).

[0281] Each of the requests Q₁₁. . . Q_1mfrom the client C₁(16) may each be different one from the other or the same; each of the requests Q₂₁. . . Q_2mfrom the client C₂(16) may each be different one from the other or the same; and each of the requests Q_n1. . . 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 Q₁₁. . . Q_1m(29), the requests Q₂₁. . . Q_2m(29), and the requests Q_n1. . . Q_nm(29), thus, may each be different one from the other, or the same, and so on. The requests Q₁₁. . . 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 S₁₁. . . S_nm(30). There may be m different or same ones of the requests Q_n1. . . Q_nm(29) from the client C_n(16) at any time, and n×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.

[0282] This designation format, in which the first alphanumeric subscript after the parameter of interest, for example, as in the parameters Q_n1. . . Q_nmrepresenting the requests Q_n1. . . Q_nm(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_n1. . . Q_nm(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_n1. . . S_nm(30) associated with the nth user U_n, which is designated as the user U_n(12). The same and/or different requests Q_n1. . . Q_nm(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_n1. . . S_nm(30), associated with and corresponding to the user U_n(12).

[0283] 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 I₁. . . I_n(14) may be integral with the clients C₁. . . C_n(16) or separate from the clients C₁. . . C_n(16). Therefore, certain ones of the user interfaces I₁. . . I_n(14) may be integral with the clients C₁. . . C_n(16), while yet other ones of the user interfaces I₁. . . I_n(14) may be separate from the clients C₁. . . C_n(16).

[0284] 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) 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₁. . . UR_n(37) for delivery to the user interfaces I₁. . . I_n(14) and use by the users U₁. . . U_n(12).

[0285] Now, the user interfaces I₁. . . I_n(14) may each be different, one from the other, or the same, and may change characteristics over time. Each of the user interfaces I₁. . . I_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 C₁. . . C_n(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 I₁. . . I_n(14). The user interface I₁. . . I_n(14) may change state.

[0286] The user interface I₁. . . I_n(14) may also change as a function of optional timers and/or timed instructions associated therewith the user interfaces I₁. . . I_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₁. . . U_n(12). Changes in the user interface I_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 I₁. . . I_n(14), as well.

[0287] The user interfaces I₁. . . I_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.

[0288] The user interfaces I₁. . . I_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 I₁. . . I_n(14) may be integral with the clients C₁. . . C_n(16) or separate.

[0289] A. Overview

[0290] FIGS. 54-56 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₁. . . S_nm(30) corresponding to the requests Q_n1. . . 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 I_n(14).

[0291] The user U_n(12) enters the corresponding user input UI_n(25) having one or more same and/or different user requests qu_n1. . . qu_nu(26) thereinto the user interface I_n(14). The user requests qu_n1. . . qu_nu(26) are communicated from the user interface I_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.

[0292] The user interface I_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 IQ_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_n1. . . Q_nm(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.

[0293] 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_n1. . . Q_nm(29), and communicates the certain requests Q_n1. . . Q_nm(29) to the corresponding certain ones of the servers S₁. . . S_z(20) designated by the server designations S_1n. . . S_nm(30), as shown for typical ones of the certain requests Q_n1. . . Q_nm(29) in FIG. 54.

[0294] 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_n1. . . Q_nm(29), and communicate the alternate requests Q_n1. . . Q_nm(29) to the corresponding alternate ones of the servers S₁. . . S_z(20) designated by the server designations S_n1. . . S_nm(30), as shown for typical alternate ones of the requests Q_n1. . . Q_nm(29) in FIG. 55.

[0295] 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 IQ_n(28) into the other alternate ones of the requests Q_n1. . . Q_nm(29), and communicates the other alternate ones of the requests Q_n1. . . Q_nm(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_n1. . . Q_nm(29), and communicate the yet other alternate ones of the requests Q_n1. . . Q_nm(29) to the corresponding yet other alternate ones of the servers S_n1. . . S_nm(30), as shown for typical other alternate ones of the requests Q_n1. . . Q_nm(29) and typical yet other alternate ones of the requests Q_n1. . . Q_nm(29) in FIG. 56.

[0296] Each of the servers S₁. . . S_z(20) designated by the server designations S_n1. . . 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 S₁₁. . . S_nm(30), accordingly, and communicates the corresponding responses R_n1. . . R_nm(32), associated with the requests Q_n1. . . Q_nm(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 R_n1. . . R_nm(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 I_n(14). The server PS (18) communicates the service and/or information response IR_n(34) to the client C_n(16), as required.

[0297] 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_n(36) thereto the user interfaces I_n(14). The user interface I_n(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 I_n(14) thereto the user U_n(12).

[0298] 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. 59, 60, 63, and 64) 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

[0299] 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 I_n(14) to the user U_n(12).

[0300] The server PS (18) and/or the clients C_n(16) may optionally store the responses R_n1. . . R_nm(32) communicated from the servers S₁. . . S_z(20) designated by the server designations S_n1. . . 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_n1. . . RA_nm(40).

[0301] 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 IR_n(34), and accessed as the additional optional responses RA_n1. . . RA_nm(40).

[0302] The user U_n(12) may optionally communicate the corresponding additional optional requests q_n1. . . q_np(44) therethrough the user interface I_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 I_n(14). The optional servers SO₁. . . SO_p(22) reply to the client C_n(16) with the corresponding responses r_n1. . . r_np(46), which the client C_n(16) communicates therethrough the user interface I_n(14) to the user U_n(12), as shown in FIGS. 54-56 for typical ones of the requests q_n1. . . q_np(44) and the corresponding responses r_n1. . . r_np(46).

[0303] B. Diagrammatic Regrouping

[0304] Now, in more detail, FIG. 57 shows a schematic representation of ones of the users U₁. . . U_n(12), the corresponding user interfaces I₁. . . I_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. 57, the nomenclature previously described and utilized will be used throughout.

[0305] Now, as shown in FIG. 57, for illustrative purposes only, ones of the clients C₁. . . C_n(16) communicating with the server PS (18), as in FIG. 54, may optionally be designated clients CA₁. . . CA_w(16A), and so on. Ones of the clients C₁. . . C_n(16) communicating with the servers S₁. . . S_z(20), as in FIG. 55, may optionally be designated clients CB₁. . . CB_x(16B), and so on. Ones of the clients C₁. . . C_n(16) communicating with the server PS (18) and with the servers S₁. . . S_z(20), as in FIG. 56, may optionally be designated clients CC₁. . . CC_y(16C), and so on.

[0306] The users U₁. . . U_n(12) and the corresponding user interfaces I₁. . . I_n(14) corresponding to the clients C₁. . . C_n(16) may, likewise, optionally be designated in FIG. 57 only: correspondingly to the clients CA₁. . . CA_w(16A), as users UA₁. . . UA_w(12A) and user interfaces IA₁. . . IA_w(14A), respectively; correspondingly to the clients CB₁. . . CB_x(16B), as users UB₁. . . UB_x(12B) and user interfaces IB₁. . . IB_x(14B), respectively; and correspondingly to the clients CC₁. . . CC_y(16C), as users UC₁. . . UC_y(12C) and IC₁. . . IC_y(14C), respectively.

[0307] The clients C₁. . . C_n(16) being accounted for, the total of the clients CA₁. . . CA_w(16A), CB₁. . . CB_x(16B), and CC₁. . . CC_y(16C) of FIG. 57 add up to n, where n may be any number greater or equal to one, such that the subscripts w+x+y=n.

[0308] B. The Server PS (18)

[0309] FIG. 58 shows a typical particular one of the service and/or information requests IQ₁. . . 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 I_n(14), and/or other information resident within the server PS (18).

[0310] FIG. 59 shows the particular service and/or information request IQ_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_n1. . . 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). The current request group QA_nc(50) may be any particular one the request groups QA_n1. . . QA_nz(51), which may be selected by the user U_n(12).

[0311] Upon receipt of the service and/or information requests IQ₁. . . IQ_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 IQ₁. . . IQ_n(28) into the corresponding current request groups QA_1c. . . QA_nc(50) having corresponding queries QQ₁₁. . . QQ_nm(53) and 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 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. 59.

[0312] The server PS (18) also parses, processes, and/or formats each of the service and/or information requests IQ₁. . . IQ_n(28) into the corresponding request groups QA₁₁. . . 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. 59.

[0313] The server PS (18) opens connections with and makes the requests Q_n1. . . 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_n1. . . Q_nm(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_n1. . . QQ_nm(53) and the corresponding server addresses AQ_n1. . . AQ_nm(54) therein the current request group QA_nc(50).

[0314] The servers S₁. . . S_z(20) corresponding to the server designations S₁₁. . . S_nm(30), designated 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), respond to the requests Q_n1. . . Q_nm(29) with the corresponding responses R_n1. . . R_nm(32).

[0315] The server PS (18) parses, and/or processes, and/or formats, and/or groups, and/or organizes each of the responses R_n1. . . R_nm(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_n1. . . RG_nm(57).

[0316] The server PS (18) may also make additional optional requests QP_n1. . . 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_n1. . . 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).

[0317] Information 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 a corresponding request pointer/address group Q_zn(60) having pointers/addresses PG_n1. . . PG_nz(61) associated therewith.

[0318] Each of the pointers/addresses PG_n1. . . 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_n1. . . RG_nm(57) to be incorporated thereinto addressable query information groups GI_n1. . . GI_nz(63).

[0319] 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 I_n(14) therethrough the user input UI_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).

[0320] The grouping and/or sorting criteria gives the user U_n(12) the ability to formulate the query information groups GI_n1. . . GI_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 I_n(14).

[0321] Each of the addressable query pointer/address groups QG_n1. . . QG_nz(62) are associated therewith the corresponding ones of the addressable query information groups GI_n1. . . GI_nz(63). The addressable query pointer/address group QG_n1(62) is, thus, associated therewith the addressable query information group GI_n1(63); the addressable query pointer/address group QG_n2(62) is, thus, associated therewith the addressable query information group GI_n2(63); the addressable query pointer/address group QG_nz(62) is, thus, associated therewith the addressable query information group GI_nz(63), and so on.

[0322] 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).

[0323] Each of the addressable query pointer/address groups QG_n1. . . QG_nz(62) has pointers/addresses PP_n11. . . PP_nmr(64) directed to address/point information therein the addressable response information groups RG_n1. . . 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).

[0324] Information and/or services within each of the addressable response information groups RG_n1. . . RG_nm(57) is addressed therewith the pointers/addresses PP_n11. . . PP_nmr(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 GI_n1. . . GI_nz(63) corresponding to the pointers/addresses PP₁₁. . . PP_nmr(64), which are formulated by the addressable query pointer/address groups QG_n1. . . QG_nz(62), in accordance with the grouping and/or sorting criteria.

[0325] 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_n1. . . Q_nm(29), and may be incorporated into the service and/or information response IR_n(34), as part of other information OI_n(65), for future use.

[0326] Each of the addressable query information groups GI_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).

[0327] The optional instructions VJ_n1. . . VJ_nk(52) may be used by the server PS (18) in making the requests Q_n1. . . Q_nm(29) and/or the additional optional requests QP_n1. . . QP_nm(58) of the optional database 41, and/or in processing, formatting, grouping, and organizing the responses R_n1. . . R_nm(32) from the ones of the servers S₁. . . S_z(20) corresponding to the server designations S_n1. . . S_nm(30), and/or the additional optional responses RA_n1. . . RA_nm(40), into the corresponding service and/or information responses IR₁. . . IR_n(34), for grouping and/or sorting criteria instructions, and/or may be used for other purposes.

[0328] FIG. 60 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_n(51), and corresponding optional instructions VJ_n1. . . VJ_nk(52), and utilization of information therefrom to make the requests Q_n1. . . 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. 59.

[0329] The user U_n(12) is typically given the option therethrough the optional instructions VJ_n1. . . VJ_nk(52) as to the grouping and/or sorting criteria to be entered thereinto the user interface I_n(14) therethrough the user input UI_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. 59, and/or the grouping and/or sorting criteria of FIG. 60.

[0330] Information 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 a corresponding request pointer/address group QY_n(68) having pointers/addresses PF_n11. . . PF_nmr(69) associated therewith, as shown in FIG. 60.

[0331] Each of the pointers/addresses PF_n11. . . PF_nmr(69) are directed to point/address the corresponding addressable response information groups RG_n1. . . RG_nm(57), and aid in obtaining information and/or services therefrom the corresponding addressable response information groups RG_n1. . . RG_nm(57) to be incorporated thereinto the addressable query information groups GI_n1. . . GI_nz(63), as shown in FIG. 60.

[0332] 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_n1. . . R_nm(32) and/or the additional optional responses RA_n1. . . 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_n1. . . R_nm(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.

[0333] FIG. 61 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_n1. . . 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).

[0334] The service and/or information group G_n(35) has the query information groups GI_n1. . . GI_nz(63), optional database response groups 75, and optional additional advertisements and/or links 76.

[0335] 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).

[0336] 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 I_n(14) therethrough the user input UI_n(25), and receive order confirmation therethrough the user interface I_n(14). The client C_n(16) may communicate the order placement therefrom the user interface I_n(14) thereto the server PS (18), which may communicate the order placement thereto the servers S₁. . . S_z(20) and/or the optional servers SO₁. . . SO_p(22). The server PS (18) may alternatively and/or additionally communicate the order confirmation received therefrom the servers S₁. . . 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 I_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.

[0337] C. Certain Ones of the Clients

[0338] Certain ones of the clients C₁. . . C_n(16) may alternatively and/or additionally 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 of the servers S₁. . . S_z(20) to be communicated with corresponding to the requests Q₁₁. . . Q_nm(29), and formulate the corresponding user service and/or information response ir₁. . . ir_n(36), as previously described.

[0339] FIG. 62 shows a typical particular one of the user service and/or information requests iq₁. . . iq_n(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_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 I_n(14), and/or other information resident within the client C_n(16).

[0340] FIG. 63 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_zn(51), and the corresponding optional instructions VJ_n1. . . VJ_nk(52), and utilization of information therefrom to make the requests Q_n1. . . Q_nm(29), obtain the responses R_n1. . . R_nm(32), and incorporate information therefrom into the particular user service and/or information response ir_n(36);

[0341] 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 Q₁₁. . . Q_nm(29) as the corresponding server designations S₁₁. . . S_nm(30), as shown in FIG. 59, and certain ones of the 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 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. 63.

[0342] The clients 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 GI_n1. . . GI_nz(63) substantially the same as the server PS (18) parses, processes, and/or formats the service and/or information requests IQ_n(28) therefrom the addressable response information groups RG_n1. . . RG_nm(57) thereinto the addressable query information groups GI_n1. . . GI_nz(63), except that the client C_n(16) may organize the addressable query information groups GI_n1. . . GI_nz(63) thereinto the user service and/or information response ir_n(36), as in FIG. 63, and the server PS (18) organizes the addressable query information groups GI_n1. . . G_nz(63) thereinto the corresponding service and/or information response IR_n(34), as in FIG. 59.

[0343] Upon receipt of the user service and/or information requests iq₁. . . iq_n(27) at the corresponding clients C₁. . . C_n(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₁. . . iq_n(27) into the corresponding current request groups QA_1c. . . QA_nc(50) having the corresponding queries QQ₁₁. . . QQ_nm(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 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 user service and/or information requests iq₁. . . iq_n(27) in FIG. 63.

[0344] The corresponding clients C₁. . . C_n(16) may also parse, process, and/or format the corresponding user service and/or information response ir₁. . . ir_n(36) into the corresponding request groups QA₁₁. . . 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 VJ₁₁. . . VJ_nk(52), also shown for a particular one of the user service and/or information requests iq_n(27) in FIG. 63.

[0345] 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_n1. . . 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_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).

[0346] The servers S₁. . . S_z(20) corresponding to the server designations S₁. . . S_nm(30), designated 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), respond to the requests Q_n1. . . Q_nm(29) with the corresponding responses R_n1. . . R_nm(32).

[0347] 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_n1. . . S_nm(30) into the corresponding addressable response information groups RG_n1. . . RG_nm(57).

[0348] The client C_n(16) may also make additional optional requests QP_n1. . . 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_n1. . . RA_nm(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).

[0349] Now again, for the client C_n(16), information 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 QZ_n(60) having the pointers/addresses PG_n1. . . PG_nz(61) associated therewith.

[0350] Now again, for the client C_n(16), each of the pointers/addresses PG_n1. . . 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 RG_n1. . . RG_nm(57) to be incorporated thereinto the addressable query information groups GI_n1. . . GI_nz(63).

[0351] Yet again, for the client C_n(16), 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 I_n(14) therethrough the user input UI_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).

[0352] Now again, the grouping and/or sorting criteria gives the user U_n(12) the ability to formulate the query information groups GI_n1. . . GI_nz(63) and the way in which information from the addressable response information groups RG_n1. . . RG_nm(57) is presented to the user U_n(12) therethrough the user interface I_n(14).

[0353] Now again, for the client C_n(16), each of the addressable query pointer/address groups QG_n1. . . QG_nz(62) are associated therewith the corresponding ones of the addressable query information groups GI_n1. . . G_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).

[0354] Now again, for the client C_n(16), each of the addressable query pointer/address groups QG_n1. . . QG_nz(62) has pointers/addresses PP_n11. . . PP_nmr(64) directed to address/point services and/or information therein the addressable response information groups RG_n1. . . 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).

[0355] Yet again, for the client C_n(16), the information and/or services therein each of the addressable response information groups RG_n1. . . RG_nm(57) is addressed therewith the pointers/addresses PP_n11. . . PP_nmr(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 GI_n1. . . G_nz(63) corresponding to the pointers/addresses PP_n11. . . PP_nmr(64), which are formulated by the addressable query pointer/address groups QG_n1. . . QG_nz(62), in accordance with the grouping and/or sorting criteria.

[0356] 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 of the requests Q_n1. . . Q_nm(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.

[0357] Now again, for the client C_n(16), each of the addressable query information groups GI_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).

[0358] The optional instructions VJ_n1. . . VJ_nk(52) may be used by the client C_n(16), in making the requests Q_n1. . . Q_nm(29) and/or the additional optional requests QP_n1. . . QP_nm(58) of the optional database 42, and/or in processing, formatting, grouping, and organizing the responses R_n1. . . R_nm(32) from the ones of the servers S₁. . . S_z(20) corresponding to the server designations S_n1. . . S_nm(30), and/or the additional optional responses RA_n1. . . 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.

[0359] FIG. 64 is a schematic representation of 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_n1. . . VJ_nk(52), and utilization of information therefrom to make the requests Q_n1. . . Q_nm(29), obtain the responses R_n1. . . R_nm(32), and incorporate information therefrom into the particular user service and/or information response ir_n(36), having simpler grouping/sorting that may be used additionally and/or alternatively to that of FIG. 63.

[0360] The user U_n(12) is typically given the option therethrough the optional instructions VJ_n1. . . VJ_nk(52) as to the grouping and/or sorting criteria to be entered thereinto the user interface I_n(14) therethrough the user input UI_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. 63, and/or the grouping and/or sorting criteria of FIG. 64.

[0361] 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 GI_n1. . . GI_nz(63) substantially the same as the server PS (18) parses, processes, and/or formats the service and/or information requests IQ_n(28) therefrom the addressable response information groups RG_n1. . . RG_nm(57) thereinto the addressable query information groups GI_n1. . . GI_nz(63), except that the client C_n(16) may organize the addressable query information groups GI_n1. . . GI_nz(63) thereinto the user service and/or information response ir_n(36), as in FIG. 64, and the server PS (18) organizes the addressable query information groups GI_n1. . . GI_nz(63) thereinto the corresponding service and/or information response IR_n(34), as in FIG. 60.

[0362] Now again, for the client C_n(16), information 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_n11. . . PF_nmr(69) associated therewith, as shown in FIG. 64.

[0363] Now again, for the client C_n(16), each of the pointers/addresses PF_n11. . . PF_nmr(69) are directed to point/address the corresponding addressable response information groups RG_n1. . . RG_nm(57), and aid in obtaining information and/or services therefrom the corresponding addressable response information groups RG_n1. . . RG_nm(57) to be incorporated thereinto the addressable query information groups GI_n1. . . GI_nz(63), as shown in FIG. 64.

[0364] 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 information and/or services therefrom the responses the responses R_n1. . . R_nm(32) and/or the additional optional responses RA_n1. . . 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_n1. . . R_nm(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.

[0365] FIG. 65 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).

[0366] Now again, the service and/or information group G_n(35) has the query information groups GI_n1. . . GI_nz(63), the optional database response groups 75, and the optional additional advertisements and/or links 76.

[0367] Yet again, 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 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).

[0368] 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 I_n(14) therethrough the user input UI_n(25), and receive order confirmation therethrough the user interface I_n(14). The client C_n(16) may communicate the order placement therefrom the user interface I_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₁. . . S_z(20) and/or the optional servers SO₁. . . SO_p(22) thereto the user interface I_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.

[0369] D. Formulating Query Information Groups

[0370] Each of the particular addressable response information groups RG_n1. . . RG_nm(57), designated as the addressable response information group RG_nm(57), has optional addressable individual information groups LG_nm1. . . LG_nmr(80), which may be addressed therewith the pointers/addresses PP_nm1. . . PP_nmr(64), as shown in FIGS. 59, 63, 66A, 66B, and 66C.

[0371] Each of the addressable response information groups RG_n1. . . RG_nm(57) and each of the optional addressable individual information groups LG_n11. . . LG_nmr(80) therein each of the addressable response information groups RG_n1. . . RG_nm(57) may be addressed therewith the pointers/addresses PP_n1. . . PP_nmr(64).

[0372] Now again, the addressable response information group RG_nm(57) has the optional addressable individual information groups LG_nm1. . . LG_nmr(80), which may be addressed therewith the pointers/addresses PP_nm1. . . PP_nmr(64). Each of the addressable individual information groups LG_nm1. . . LG_nmr(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 of the addressable individual information groups LG_nm1. . . LG_nmr(80), therefrom the addressable response information group RG_nm(57), and incorporate information and/or services therefrom the addressable individual information groups LG_nm1. . . LG_nmr(80) thereinto certain ones of the addressable query information groups GI_n1. . . GI_nz(63), in accordance with the grouping and/or sorting criteria addressing scheme.

[0373] The addressable response information group RG_nm(57) having the optional addressable individual information groups LG_nm1. . . LG_nmr(80) may have optional addressable pointer/address indices IN_nm1. . . IN_nmr(81) correspondingly associated therewith the optional addressable individual information groups LG_nm1. . . LG_nmr(80), which may be addressed/pointed therewith the pointers/addresses PP_nm1. . . PP_nmr(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 of the addressable individual information groups LG_nm1. . . LG_nmr(80), and incorporate information and/or services therefrom the addressable individual information groups LG_nm1. . . LG_nmr(80) thereinto the certain ones of the addressable query information groups GI_n1. . . G_nz(63), in accordance with the grouping and/or sorting criteria addressing scheme.

[0374] FIGS. 66A, 66B, and 66C show the addressable response information group RG_nm(57) having the addressable individual information groups LG_nm1. . . LG_nmr(80) showing the optional addressable pointer/address indices IN_nm1. . . IN_nmr(81) correspondingly associated therewith the optional addressable individual information groups LG_nm1. . . LG_nmr(80), which may be addressed/pointed therewith the pointer/addresses PP_nm1(64), PP_nm2(64), and PP_nmr(64), respectively.

[0375] The optional addressable pointer/address index IN_nm1(81) is correspondingly associated therewith the optional addressable individual information group LG_nm1(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_nmr(81) is, thus, correspondingly associated therewith the optional addressable individual information group LG_nm1(80).

[0376] The pointers/addresses PG_n1. . . PG_nz(61) may be formulated as arrays and/or lists. The pointers/addresses PP_nm1. . . PP_nmr(64) and/or the pointers/addresses PF_nm1. . . PF_nmr(69) may be formulated as arrays and/or lists. The arrays may be multidimensional arrays, and the lists may be lists within lists.

[0377] The optional addressable individual information group LG_nmr(80) is associated therewith and corresponds to a particular one of the addressable individual information groups LG_nm1. . . LG_nmr(80) therein a particular one of the addressable response information groups RG_n1. . . RG_nm(57), designated as the addressable response information group RG_nm(57). The first subscript of the optional addressable individual information groups LG_nmr(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 of the 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_n1. . . RG_nm(57). The third subscript of the optional addressable individual information groups LG_nmr(80) is associated therewith and corresponds to a particular one of “1” through “r” i.e., 1 . . . r, of the optional addressable individual information group LG_nm1. . . LG_nmr(80) within the addressable response information group RG_nm(57).

[0378] The subscripts of the optional addressable pointer/address indices IN_nm1. . . IN_nmr(81) are correspondingly associated therewith the subscripts of the corresponding addressable individual information groups LG_nm1. . . LG_nmr(80).

[0379] 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.

[0380] For example, the pointers/addresses PG_n1. . . PG_nz(61) of the request pointer/address group QZ_n(60) may be pointed/addressed thereto certain ones of the 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_n11. . . PP_nmr(64) of each of the pointed/addressed addressable query pointer/address groups QG_n1. . . QG_nz(62) may be pointed thereto the pointer/address indices IN_n11. . . IN_nmr(81) of the optional addressable individual information groups LG_nm1. . . LG_nmr, i.e., 1 . . . r, and the pointers/addresses PP_n1. . . PP_nmr(64), i.e., 1 . . . m, corresponding to the addressable response information groups RG_n1. . . RG_nm(57) formulated by the addressable query pointer/address groups QG_n1. . . QG_nz(62) may be pointed thereto certain ones of the addressable response information groups RG_n1. . . 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_nm1. . . LG_nmrfrom the addressable response information groups RG_n1. . . RG_nm(57) is incorporated thereinto the certain ones of the addressable query information groups GI_n1. . . G_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_n(60).

[0381] Alternatively and/or additionally, the pointers/addresses PG_n1. . . PG_nz(61) of the request pointer/address group QZ_n(60) may be incremented therethrough each of the addressable query pointer/address groups QG_n1. . . QG_nz(62). The pointers/addresses PP_n11. . . PP_nmr(64) of each of the pointed/addressed addressable query pointer/address groups QG_n1. . . QG_nz(62) may be pointed to the pointer/address indices IN_n11. . . IN_nmr(81) of the optional addressable individual information groups LG_nm1. . . LG_nmr, i.e., 1 . . . r, and incremented once, and then the pointers/addresses PP_n11. . . PP_nmr(64), i.e., 1 . . . m, corresponding to the addressable response information groups RG_n1. . . RG_nm(57) formulated by the addressable query pointer/address groups QG_n1. . . QG_nz(62) may be incremented therethrough each of the 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 LG_nm1. . . LG_nmrfrom the addressable response information groups RG_n1. . . RG_nm(57) is incorporated thereinto the certain ones of the addressable query information groups GI_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).

[0382] Alternatively and/or additionally, the pointers/addresses PP_n11. . . PP_nmr(64), i.e., 1 . . . m, may be incremented, corresponding to the addressable response information groups RG_n1. . . RG_nm(57) formulated by the addressable query pointer/address groups QG_n1. . QG_nz(62), and then the pointers/addresses PP_n1. . . PP_nmr(64), i.e., 1 . . . r, pointing to the pointer/address indices IN_n11. . . IN_nmr(81) of the optional addressable individual information groups LG_nm1. . . LG_nmrmay then be incremented. This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LG_nm1. . . LG_nmrfrom the addressable response information groups RG_n1. . . RG_nm(57) is incorporated thereinto the certain ones of the addressable query information groups GI_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).

[0383] Alternatively and/or additionally, the pointers/addresses PF_nm1. . . PF_nmr(69), i.e., 1 . . . m, may be incremented, corresponding to the addressable response information groups RG_n1. . . RG_nm(57) formulated by the addressable query pointer/address groups QG_n1. . . QG_nz(62), and then the pointers/addresses PF_nm1. . . PF_nmr(69), i.e., 1 . . . r, pointing to the pointer/address indices IN_n1. . . IN_nmr(81) of the optional addressable individual information groups LG_nm1. . . LG_nmrmay then be incremented. This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LG_nm1. . . LG_nmrfrom the addressable response information groups RG_n1. . . RG_nm(57) is incorporated thereinto the certain ones of the addressable query information groups GI_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).

[0384] The typical sorting and/or grouping criteria and the addressing/pointing schemes mentioned immediately above, for example, may group certain ones of the queries QQ_n1. . . QQ_nm(53) having the same and/or substantially the same values grouped therein a particular one of the query information groups GI_1n. . . GI_nz(63), designated as the query information group GI_nz(63), as shown in certain ones of FIGS. 27A-52C, inclusive.

[0385] 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 of the capabilities of the client-server multitasking system 10 of the present invention.

[0386] The addressable individual information groups LG_nm1. . . 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_nm1. . . LG_nmr(80) are incorporated thereinto the addressable response information groups RG_n1. . . RG_nm(57) therefrom the responses R_n1. . . R_nm(32).

[0387] Alternatively and/or additionally the addressable individual information groups LG_nm1. . . LG_nmr(80) may be incorporated thereinto the addressable response information groups RG_n1. . . RG_nm(57) therefrom the responses R_n1. . . R_nm(32) in an as-is condition and/or in raw form.

[0388] The optional addressable individual information groups LG_nm1. . . LG_nmr(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 of the information and/or services therein the response R_nm(32).

[0389] Each of the addressable individual information groups LG_nm1. . . LG_nmr(80) may have and/or be parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into corresponding optional links LD_nm1. . . LD_nmr(82), and/or corresponding optional descriptions DD_nm1. . . DD_nmr(83), and/or corresponding optional prices/values PD_nm1. . . PD_nmr(84), and/or corresponding optional images ID_nm1. . . ID_nmr(85), as shown in FIG. 67.

[0390] The optional links LD_nm1. . . LD_nmr(82), the corresponding optional descriptions DD_nm1. . . DD_nmr(83), the corresponding optional prices/values PD_nm1. . . PD_nmr(84), and the corresponding optional images ID_nm1. . . ID_nmr(85), corresponding to the addressable individual information groups LG_nm1. . . LG_nmr(80) are typically associated correspondingly one with the other.

[0391] The optional link LD_nm1(82), the corresponding optional description DD_nm1(83), the corresponding optional price/value PD_nm1(84), and the corresponding optional image ID_nm1(85), corresponding to the optional individual information group LG_nm1(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_nmr(83), the corresponding optional price/value PD_nmr(84), and the corresponding optional image ID_nmr(85), corresponding to the addressable individual information group LG_nmr(80) are, thus, typically associated correspondingly one with the other.

[0392] The addressable individual information groups LG_nm1. . . LG_nmr(80), which may have the corresponding optional links LD_nm1. . . LD_nmr(82), and/or the corresponding optional descriptions DD_nm1. . . DD_nmr(83), and/or the corresponding optional prices/values PD_nm1. . . PD_nmr(84), and/or the corresponding optional images ID_nm1. . . ID_nmr(85) are appended therewith labels/identifiers, as shown in FIG. 68, and incorporated thereinto certain ones of the addressable query information groups GI_n1. . . GI_nz(63), depending upon the grouping and/or sorting criteria. FIG. 69 shows a particular one of the addressable query information groups GI_n1. . . GI_nz(63), designated as the query information group GI_nz(63).

[0393] Now again, the optional addressable individual information group LG_nmr(80) is associated therewith and corresponds to a particular one of the addressable individual information groups LG_nm1. . . LG_nmr(80) therein a particular one of the addressable response information groups RG_n1. . . RG_nm(57), designated as the addressable response information group RG_nm(57). The first subscript of the optional addressable individual information groups LG_nmr(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 of the 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_n1. . . RG_nm(57). The third subscript of the optional addressable individual information groups LG_nmr(80) is associated therewith and corresponds to a particular one of “1” through “r”, i.e., 1 . . . r, of the optional addressable individual information group LG_nm1. . . LG_nmr(80) within the addressable response information group RG_nm(57).

[0394] FIG. 68 shows a labelled individual information group LL_nzu(86) associated therewith a particular one of the addressable query information groups GI_n1. . . GI_nz(63), designated as the addressable query information group GI_nz(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 SI_nm(90), and/or optional server link identifier LX_nmr(91) appended thereto the addressable individual information group LG_nmr(80).

[0395] The first alphanumeric subscript of the 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 of the labelled individual information group LL_nzu(86) is associated therewith and corresponds to a particular one of “1” through “z”, i.e., 1 . . . z, of the addressable query information groups GI_n1. . . GI_nz(63), designated as the addressable query information group GI_nz(63), which the labelled individual information group LL_nzu(86) is incorporated therein. The third alphanumeric subscript of the 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_nz1. . . LL_nzu(86) within the addressable query information group GI_nz(63).

[0396] The optional group identifier GL_nc(87) labels and/or identifies the current request group QA_nc(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 of the 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 of the optional group identifier GL_nc(87) is associated therewith and corresponds to the particular one of the request groups QA_n1. . . QA_nz(51 ) selected by the user U_n(12) as the current request group QA_nc(50).

[0397] 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_ncu(86). The first alphanumeric subscript of the 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 of the optional query link identifier LN_ncu(88) is also associated therewith and corresponds to the particular one of the 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 of the 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_nz1. . . LL_nzu(86) therein the addressable query information group GI_nz(63).

[0398] 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_nmr(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 of the optional servers SO₁. . . SO_p(22) and/or certain ones of the 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 of the 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 of the optional resource location identifier SU_nw(89) is associated therewith and corresponds to a particular one of “1” through “w”, i.e., 1 . . . w, of the optional resource location identifiers SU_n1. . . SU_nw(89) therein the labelled individual information group LL_nzu(86).

[0399] The optional server and/or query identifier SI_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_nmr(80) therein the corresponding labelled individual information group LL_nzu(86) of the current request group QA_nc(50). The first alphanumeric subscript of the optional server and/or query identifier SI_nm(90) 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 of the optional server and/or query identifier SI_nm(90) is associated therewith and corresponds to a particular one of “1” through “m”, i.e., 1 . . . m, of the optional server and/or query identifiers SI_n1. . . SI_nm(90), which may be correspondingly associated therewith the corresponding ones of the queries QQ_n1. . . QQ_nm(53) and/or the corresponding ones of the server addresses AQ_n1. . . AQ_nm(54).

[0400] The optional server link identifier LX_nmr(91) labels and/or identifies the location of the optional addressable individual information group LG_nmr(80) therein the corresponding addressable response information groups RG_nm(57). The first alphanumeric subscript of the 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 of the optional server link identifier LX_nmr(91) is associated therewith and corresponds to the addressable response information group RG_nm(57). The third alphanumeric subscript of the optional server link identifier LX_nmr(91) is associated therewith and corresponds to a particular one of “1” through “r”, i.e., 1 . . . r, of the optional server link identifiers LX_nm1. . . LX_nmr(91), which may be correspondingly associated therewith the locations of certain ones of the optional addressable individual information group LG_nm1. . . LG_nmr(80) therein the addressable response information groups RG_nm(57). The certain ones of the optional addressable individual information groups LG_nm1. . . LG_nmr(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_nm1. . . LX_nmr(91), are correspondingly associated therewith the locations of the information and/or services therein the response R_nm(32). The optional server link identifiers LX_nm1. . . LX_nmr(91), thus, identify and/or label the location of services and/or information therein the response R_nm(32).