US 7,165,091 B2Grant
Metasearching a plurality of queries and consolidating results
Issue Date:2007-01-16
•68 Claims
•341 Drawing Sheets
Abstract
A process and system for metasearching activated by a request executed by a user on a client device to request a metasearch engine to send a plurality of search queries to a plurality of search engines, the request specifying to which of the plurality of search engines each of the plurality of search queries is to be sent to, each of the plurality of search queries comprising a keyword phrase, each of the keyword phrases comprising at least one keyword specified in the request by the user, at least two of the keyword phrases being different from each other, comprising incorporating, by the metasearch engine, received search results into at least two different display lists corresponding to the at least two different keyword phrases, incorporating means for inputting at least one quantity of at least one item that may be ordered, and communicating a response to the client device.
Metadata
Inventor
- Harvey Lunenfeld
Application Information
Application Number:US 11/023,809
Filing Date:2004-12-28
Priority Date:2000-02-22
Art Unit:2142
Classifications
IPC:
G06F13/00
Patent Drawings (341 sheets)
Description
CROSS-REFERENCES
[0001] This application is a continuation of U.S. patent application Ser. No. 09/791,264, filed Feb. 22, 2001, now U.S. Pat. No. 6,836,769, which is a continuation-in-part of U.S. patent application Ser. No. 09/510,749, filed Feb. 22, 2000, now U.S. Pat. No. 6,789,073.
[0002] The present application is related to copending U.S. patent application Ser. No. 10/934,627, filed Sep. 3, 2004, which is a continuation of U.S. patent application Ser. No. 09/510,749, filed Feb. 22, 2000, now U.S. Pat. No. 6,789,073. The present application is also related to copending U.S. patent application Ser. No. 10/451,128, filed Aug. 21, 2002, which is the National Stage Application of International Application No. PCT/US01/05926, filed Feb. 22, 2001, which is a continuation-in-part of U.S. patent application Ser. No. 09/510,749, filed Feb. 22, 2000, now U.S. Pat. No. 6,789,073. The present application is also related to Canadian Patent Application No. 2,400,926, filed Aug. 20, 2002, now Canadian Patent No. CA 2,400,926, which is the Canadian National Stage Application of International Application No. PCT/US01/05926, filed Feb. 22, 2001, which claims the benefit of priority to U.S. patent application Ser. No. 09/510,749, filed Feb. 22, 2000, now U.S. Pat. No. 6,789,073. The present application is also related to copending Australian Patent Application No. 2001241718, filed Sep. 19, 2002, which is the Australian National Stage Application of International Application No. PCT/US01/05926, filed Feb. 22, 2001, which claims the benefit of priority to U.S. patent application Ser. No. 09/510,749, filed Feb. 22, 2000, now U.S. Pat. No. 6,789,073. The present application is also related to copending European Patent Application No. EP20010912999, filed Sep. 16, 2002, which is the European Regional Stage Application of International Application No. PCT/US01/05926, filed Feb. 22, 2001, which claims the benefit of priority to U.S. patent application Ser. No. 09/510,749, filed Feb. 22, 2000, now U.S. Pat. No. 6,789,073. The above referenced documents are not admitted to be prior art with respect to the present invention by their mention herein.
BACKGROUND OF THE INVENTION
[0003] 1. Field of the Invention
[0004] The present invention relates generally to clients and servers and more particularly to client-server multitasking.
[0005] 2. Background Art
[0006] 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.
[0007] A requestor and/or user should be capable of making substantially multiple simultaneous same and/or different requests of the 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.
[0008] 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.
[0009] 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 requestor, and/or the user, and/or the client-server multitasking system, or to combine the responses within the service and/or information response, such as, for example, interleaving the responses one with the other, such as, for example, by order of relevance or other parameters. The responses 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. The responses should be presentable, for example, in ascending or descending order in the 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.
[0010] 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.
[0011] 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 from the search engines, and/or sites, and/or servers, and/or locations being queried on the network, 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 with 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 the client-server multitasking search engine and/or database.
[0012] 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.
[0013] 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.
[0014] The client-server multitasking system and process should also be capable of sorting, grouping, and/or organizing results from the servers, search engines, and/or sites, in accordance with instructions from the requestors, and/or the users, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system and process should also be capable of drilling down and/or up to different levels within the search engines, sites, and/or servers being queried.
[0015] 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.
[0016] The client-server multitasking system and process should be capable of incorporating information and/or services into a variety of user interfaces at different locations in the user interfaces, grouping, and/or organizing the information and/or services, and optionally eliminating duplicate information and/or services.
[0017] 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 into the information and/or services to be delivered to 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 through servers and/or sites on the network.
[0018] 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.
[0019] 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 from 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 with the substantially simultaneous multiple same and/or different searches and/or queries of the same and/or different servers on the network. Information in the client-server multitasking system search engine and/or database should also be searchable and/or retrievable, and should be capable of being incorporated into the service and/or information responses delivered to 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 in the client-server multitasking system search engine and/or database, and updating the services and/or information to be stored and/or stored in the client-server multitasking system search engine and/or database.
[0020] The client-server multitasking system and process should be capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information from 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 into user responses for delivery to and use by the requestors and/or users.
[0021] The client-server multitasking system and process should be capable of performing as a multiple query search engine, which performs multiple queries of multiple sites, and performing as a single point of sale for purchasing multiple products from multiple sources.
[0022] 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 from 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 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 and process should also be capable of building a client-server multitasking system search engine and/or database from 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 in 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 from 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 into user responses for delivery to and use by the requestors and/or users.
SUMMARY
[0023] 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 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.
[0024] The client-server multitasking system and process are capable of retrieving substantially multiple simultaneous services and/or information having the same and/or different criteria from the same and/or different servers, sorting, grouping, and/or organizing the responses from the servers and/or the clients into information and/or services responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously. The requestors and/or the users may make substantially simultaneous service and/or information requests of servers and clients, using the same and/or different queries, and/or the same and/or different instructions. The same and/or different uniform resource locators, target resources, and/or paths may be used.
[0025] The client-server multitasking system and process are capable of making multiple substantially simultaneous same and/or different requests of the 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.
[0026] The client-server multitasking system and process are also capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the requestors and/or the users, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system 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 are also capable of building a client-server multitasking system search engine and/or database from responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof, are capable of being searched and/or queried, querying sites referenced in the client-server multitasking system search engine and/or database, and updating information and/or services stored therein.
[0027] 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.
[0028] A requestor and/or user is capable of making substantially multiple simultaneous same and/or different requests of the same and/or different servers. The client server-multitasking system and process are capable of organizing responses from the servers into service and/or information responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously, and on-the-fly.
[0029] 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 are 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.
[0030] 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. 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.
[0031] The client-server multitasking system and process are 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.
[0032] The client-server multitasking system and process are 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 are capable of storing the information and/or services retrieved from the search engines, and/or sites, and/or servers, and/or locations being queried on the network, and building the client-server search engine and/or database. The client-server multitasking search engine is also capable of being queried either directly and/or in combination with 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 are 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 the client-server multitasking search engine and/or database.
[0033] The client-server multitasking system and process are 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.
[0034] 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.
[0035] The client-server multitasking system and process are also capable of sorting, grouping, and/or organizing results from 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 of drilling down and/or up to different levels within the search engines, sites, and/or servers being queried.
[0036] 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.
[0037] The client-server multitasking system and process are capable of incorporating information and/or services into a variety of user interfaces at different locations in the user interfaces, grouping, and/or organizing the information and/or services, and optionally eliminating duplicate information and/or services.
[0038] 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 into the information and/or services to be delivered to 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 through servers and/or sites on the network.
[0039] 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.
[0040] 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 service 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 from 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 with the substantially simultaneous multiple same and/or different searches and/or queries of the same and/or different servers on the network. Information in the client-server multitasking system search engine and/or database are also searchable and/or retrievable, and are capable of being incorporated into the service and/or information responses delivered to the user interface, 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 in the client-server multitasking system search engine and/or database, and updating the services and/or information to be stored and/or stored in the client-server multitasking system search engine and/or database.
[0041] The client-server multitasking system and process are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information from the same and/or different ones of the servers and/or clients having the same and/or different structures, formats, organization, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information into user responses for delivery to and use by the requestors and/or users.
[0042] 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 from 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 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 are capable of building a client-server multitasking system search engine and/or database from 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 in 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 from 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 into user responses for delivery to and use by the requestors and/or users.
[0043] The client-server multitasking system and process are also capable of performing as a multiple query search engine, which performs multiple queries of multiple sites, and performing as a single point of sale for purchasing multiple products from multiple sources.
[0044] A multitasking process having features of the present invention comprises: parsing, processing and/or formatting a service and/or information request into a current request group; opening connections with and making at least one request of at least one server; parsing, processing, formatting, grouping, and/or organizing at least one response from the at least one server into at least one addressable response information group; formulating information from the current request group into 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 from the at least one addressable response information group into at least one addressable query information group; and incorporating the at least one addressable query information group into a service and/or information response.
[0045] 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 into a current request group; means for opening connections with and making at least one request of at least one server; means for parsing, processing, formatting, grouping, and/or organizing at least one response from the at least one server into at least one addressable response information group; means for formulating information from the current request group into 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 from the at least one addressable response information group into at least one addressable query information group; and means for incorporating the at least one addressable query information group into a service and/or information response.
DRAWINGS
[0046] 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:
[0047] FIG. 1 is a schematic representation of a client-server multitasking system, constructed in accordance with the present invention.
[0048] FIG. 2 is a more detailed schematic representation of the client-server multitasking system;
[0049] FIG. 3 is a schematic representation of user input UIn from user Un into user interface In of the client-server multitasking system;
[0050] FIG. 4 is a schematic representation of a server Sz of the client-server multitasking system;
[0051] FIG. 5A depicts a typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate typical user input UIn thereinto;
[0052] FIG. 5B depicts the typical service and/or information entry request form IEn at the user interface In of FIG. 5B with reference alphanumerics;
[0053] FIG. 6 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn thereinto;
[0054] FIG. 7 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn thereinto;
[0055] FIG. 8 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn thereinto;
[0056] FIG. 9 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn thereinto;
[0057] FIG. 10 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn thereinto;
[0058] FIG. 11 depicts a typical completed service and/or information entry request form IFn at the user interface In;
[0059] FIG. 12 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0060] FIG. 13 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0061] FIG. 14A depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0062] FIG. 14B depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0063] FIG. 14C depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0064] FIG. 15 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0065] FIG. 16 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0066] FIG. 17 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0067] FIG. 18 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0068] FIG. 19 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0069] FIG. 20 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0070] FIG. 21 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0071] FIG. 22 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0072] FIG. 23 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0073] FIG. 24 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0074] FIG. 25 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0075] FIG. 26 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0076] FIGS. 27A , 27B, and 27C depict a typical user response URn, as a typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0077] FIGS. 28A , 28B, and 28C depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0078] FIGS. 29A , 29B, and 29C depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0079] FIGS. 30A and 30B depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0080] FIGS. 31A and 31B depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0081] FIGS. 32A and 32B depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0082] FIGS. 33A , 33B, and 33C depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0083] FIGS. 34A , 34B, and 34C depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0084] FIGS. 35A , 35B, and 35C depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0085] FIGS. 36A , 36B, and 36C depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0086] FIGS. 37A , 37B, 37C, and 37D depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0087] FIGS. 38A , 38B, 38C, and 38D depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0088] FIGS. 39A , 39B, and 39C depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0089] FIGS. 40A , 40B, 40C, 40D, 40E, 40F, 40G, 40H, 40I, 40J, 40K, 40L, and 40M depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0090] FIGS. 41A , 41B, 41C, 41D, 41E, and 41F depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0091] FIGS. 42A , 42B, 42C, 42D, 42E, 42F, 42G, 42H, 42I, 42J, 42K, 42L, 42M, 42N, and 42O depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0092] FIGS. 43A , 43B, 43C, 43D, 43E, 43F, 43G, 43H, 43I, 43J, 43K, 43L, 43M, 43N, and 43O depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0093] FIGS. 44A , 44B, and 44C depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0094] FIGS. 45A , 45B, and 45C depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0095] FIGS. 46A , 46B, 46C, 46D, and 46E depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0096] FIGS. 47A , 47B, and 47C depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0097] FIGS. 48A , 48B, 48C, and 48D depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0098] FIGS. 49A , 49B, 49C, 49D, 49E, 49F, 49G, 49H, and 49I depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0099] FIGS. 50A , 50B, 50C, 50D, 50E, 50F, 50G, 50H, 50I, 50J, and 50K depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0100] FIGS. 51A , 51B, 51C, 51D, 51E, 51F, and 51G depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0101] FIGS. 52A , 52B, and 52C depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0102] FIG. 53A is a schematic representation of a server PS of the client-server multitasking system having an optional database;
[0103] FIG. 53B is a schematic representation of a client Cn of the client-server multitasking system having an optional database;
[0104] FIG. 54 is a schematic representation of a particular one of the clients C1. . . Cn of the client-server multitasking system, designated as the particular client Cn, communicating with ones of the servers S1 . . . Sz, in accordance with the designation scheme corresponding to the corresponding ones of the server designations Sn1 . . . Snm, corresponding to the requests Qn1. . . Qnm, through the server PS;
[0105] FIG. 55 is a schematic representation of the particular client Cn of the client-server multitasking system communicating with ones of the servers S1. . . Sz, in accordance with the designation scheme corresponding to the corresponding ones of the server designations Sn1. . . Snm, corresponding to the requests Qn1. . . Qnm;
[0106] FIG. 56 is a schematic representation of the particular client Cn of the client-server multitasking system communicating with ones of the servers S1. . . Sz, in accordance with the designation scheme corresponding to the corresponding ones of the server designations Sn1. . . Snm, corresponding to the requests Qn1. . . Qnm, and also through the server PS;
[0107] 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;
[0108] FIG. 58 is a schematic representation of a particular service and/or information request IQn;
[0109] FIG. 59 is a schematic representation of a particular service and/or information request IQn parsed, processed, and/or formatted into a current request group QAnc, request groups QAn1. . . QAnz, and corresponding optional instructions VJn1. . . VJnk, and utilization of information therefrom to make the requests Qn1. . . Qnm, obtains the responses Rn1. . . Rnm, and incorporate information therefrom into a particular service and/or information response IRn;
[0110] FIG. 60 is a schematic representation of the particular service and/or information request IQn parsed, processed, and/or formatted into a current request group QAnc, request groups QAn1. . . QAnz, and corresponding optional instructions VJn1. . . VJnk, and utilization of information therefrom to make the requests Qn1. . . Qnm, obtain the responses Rn1. . . Rnm, and incorporate information therefrom into the particular service and/or information response IRn, having other grouping/sorting that may be used additionally and/or alternatively to that of FIG. 59 ;
[0111] FIG. 61 is a schematic representation of the particular service and/or information response IRn having a service and/or information group Gn, additional request links SLn1. . . SLnw, optional order form, optional additional advertisements and/or links, optional hidden information, and the optional service and/or information entry request form;
[0112] FIG. 62 is a schematic representation of a particular user service and/or information request iqn;
[0113] FIG. 63 is a schematic representation of a particular user service and/or information request iqn parsed, processed, and/or formatted into the current request group QAnc, the request groups QAn1. . . QAnz, and the corresponding optional instructions VJn1. . . VJnk, and utilization of information therefrom to make the requests Qn1. . . Qnm, obtain the responses Rn1. . . Rnm, and incorporate information therefrom into the particular user service and/or information response irn;
[0114] FIG. 64 is a schematic representation of the particular user service and/or information request iqn parsed, processed, and/or formatted into the current request group QAnc, the request groups QAn1. . . QAnz, and the corresponding optional instructions VJn1. . . VJnk, and utilization of information therefrom to make the requests Qn1. . . Qnm, obtain the responses Rn1. . . Rnm, and incorporate information therefrom into the particular user service and/or information response irn, having other grouping/sorting that may be used additionally and/or alternatively to that of FIG. 63 ;
[0115] FIG. 65 is a schematic representation of the particular user service and/or information response irn having the service and/or information group Gn, the additional request links SLn1. . . SLnw, 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;
[0116] FIG. 66A is a schematic representation of a response information group RGnm having addressable individual information groups LGnm1 . . . LGnmr showing optional addressable pointer/address indices INnm1 . . . INnmr correspondingly associated with optional addressable individual information groups LGnm1 . . . LGnmr, which may be addressed/pointed with pointer/address PPnm1;
[0117] FIG. 66B is a schematic representation of the addressable response information group RGnm having the addressable individual information groups LGnm1. . . LGnmr showing the optional addressable pointer/address indices INnm1. . . INnmr correspondingly associated with the optional addressable individual information groups LGnm1. . . LGnmr, which may be addressed/pointed with the pointer/address PPnm2;
[0118] FIG. 66C is a schematic representation of the addressable response information group RGnm having the addressable individual information groups LGnm1. . . LGnmr showing the optional addressable pointer/address indices INnm1. . . INnmr correspondingly associated with the optional addressable individual information groups LGnm1. . . LGnmr, which may be addressed/pointed with the pointer/address PPnmr;
[0119] FIG. 67 is a schematic representation of the individual information groups LGnm1. . . LGnmr having corresponding optional links LDnm1. . . LDnmr, and/or corresponding optional descriptions DDnm1. . . DDnmr, and/or corresponding optional prices/values PDnm1, . . . PDnmr, and/or corresponding optional images IDnm1. . . IDnmr;
[0120] FIG. 68 is a schematic representation of a labelled individual information group LLnmr;
[0121] FIG. 69 is a schematic representation of an addressable query information group GInz;
[0122] FIG. 70 is a schematic representation of steps of a client-server multitasking process of the present invention;
[0123] FIG. 71 is a schematic representation of a multitasking process of deriving the service and/or information response IRn and/or the user service and/or information response irn, with reference to FIGS. 59 and 63 ;
[0124] FIG. 72 is a schematic representation of a multitasking process of deriving the service and/or information response IRn and/or the user service and/or information response irn having 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 ;
[0125] FIG. 73 is a schematic representation of a step of the multitasking process of FIGS. 71 and 72 shown in more detail;
[0126] FIG. 74 is a schematic representation of another step of the multitasking process of FIG. 71 shown in more detail;
[0127] FIG. 75 is a schematic representation of another step of the multitasking process of FIG. 72 shown in more detail;
[0128] FIG. 76 is a schematic representation of user review of user response URn and/or selection of additional services and/or information;
[0129] FIG. 77 is a schematic representation of the user input UIn into the service and/or information entry request form IEn;
[0130] FIG. 78 is a schematic representation of the service and/or information entry request form IEn showing fields, links, and elements of the service and/or information entry request form IEn;
[0131] FIG. 79 is a schematic representation of a completed service and/or information entry request form IFn showing typical elements, values, and field names;
[0132] FIG. 80 is a schematic representation of the completed service and/or information entry request form IFn, a user service and/or information request iqn, and the client Cn of the client-server multitasking system;
[0133] FIG. 81 is a schematic representation of the user service and/or information request iqn;
[0134] FIG. 82 is a schematic representation of the service and/or information request IQn;
[0135] FIG. 83 is an alternate schematic representation of the user service and/or information request iqn of FIG. 81 ;
[0136] FIG. 84 is an alternate schematic representation of the service and/or information request IQn of FIG. 82 ;
[0137] FIG. 85 is a more detailed schematic representation of the service and/or information request IQn of FIGS. 82 and 84 showing typical field names and values;
[0138] FIG. 86 is an alternate more detailed schematic representation of the service and/or information request IQn of FIGS. 82 and 84 ;
[0139] FIG. 87 is a schematic representation showing queries QQn1. . . QQnm and corresponding server addresses AQn1. . . AQnm;
[0140] FIG. 88 shows the schematic representation of FIG. 87 having typical values;
[0141] FIG. 89 shows the schematic representation of FIG. 87 having other typical values;
[0142] FIG. 90 shows the schematic representation of FIG. 87 having other typical values;
[0143] FIG. 91 shows the schematic representation of FIG. 87 having other typical values;
[0144] FIG. 92 is a schematic representation of information that may be used for formulating a typical particular one of the requests Qn1. . . Qnm, designated as the request Qnm, and optional instructions VJnm1. . . VJnk from the particular service and/or information request IQn and opening a connection OCnm;
[0145] FIG. 93 is a schematic representation of information that may be used for formulating the typical particular one of the requests Qn1. . . Qnm, designated as the request Qnm, and the optional instructions VJnm1. . . VJnk from the particular user service and/or information request iqn and opening the connection OCnm;
[0146] FIG. 94 is an alternate schematic representation of information that may be used for formulating the typical particular one of the requests Qn1. . . Qnm, designated as the request Qnm, and optional instructions VJnm1. . . VJnk from the particular service and/or information request IQn and opening a connection OCnm of FIG. 92 ;
[0147] FIG. 95 is an alternate schematic representation of information that may be used for formulating the typical particular one of the requests Qn1. . . Qnm, designated as the request Qnm, and the optional instructions VJnm1. . . VJnk from the particular user service and/or information request iqn and opening the connection OCnm of FIG. 93 ;
[0148] FIG. 96 is a schematic representation of queries QQn1. . . QQnm, corresponding server addresses AQn1. . . AQnm, and optional instructions VJnm1. . . VJnk that may be parsed, processed, and/or formatted from the service and/or information request IQn and/or the user service and/or information request iqn;
[0149] FIG. 97 is a schematic representation of a request pointer/address group QZns, having a particular one of query pointer/address groups QGn1. . . QGnz, designated as the query pointer/address group QGnz, associated ones of the addressable response information groups RGn1. . . RGnm, the pointers/addresses PPn11. . PPnmr, and the query information group GInz associated with the query pointer/address group QGnz;
[0150] FIG. 98 is a schematic representation of a sorting criteria addressing scheme having a particular query pointer/address group QGnz, associated ones of response information groups RGnm, and query information group GInz associated with the query pointer/address group QGnz;
[0151] FIG. 99 is a schematic representation of an alternate sorting criteria addressing scheme having a particular query pointer/address group QGnz, associated ones of response information groups RGnm, and query information group GInz associated with the query pointer/address group QGnz;
[0152] FIG. 100 is a schematic representation of typical ones of the query pointer/address groups QGn1. . . QGnz, having the sorting criteria addressing scheme of FIG. 98 , having typical ones of queries QQn1. . . QQnz and corresponding server addresses AQn1. . . AQnz associated therewith;
[0153] FIG. 101 is another schematic representation of the typical ones of the query pointer/address groups QGn1. . . QGnz, having the sorting criteria addressing scheme of FIG. 98 , having the typical ones of the of queries QQn1. . . QQnz and the corresponding ones of the server addresses AQn1. . . AQnz of FIG. 100 associated therewith;
[0154] FIG. 102 is a generic schematic representation of the query pointer/address groups QGn1. . . QGnz, having the sorting criteria addressing scheme of FIG. 98 , having the ones of queries QQn1. . . QQnz and the corresponding ones of the server addresses AQn1. . . AQnz associated therewith;
[0155] FIG. 103 is a schematic representation of a request Qnm of the client-server multitasking system;
[0156] FIG. 104 is a schematic representation of a response Rnm of the client-server multitasking system;
[0157] FIG. 105 is a schematic representation of an entity body RHnm of the response Rnm of FIG. 104 having the optional response individual information groups LSnm1. . . LSnmr, and/or optional information LInm;
[0158] FIG. 106 is a schematic representation of the addressable response information group RGnm having the addressable individual information groups LGnm1. . . LGnmr parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into the addressable response information group RGnm from the optional entity body RHnm of FIG. 105 ;
[0159] FIG. 107 is a schematic representation of the optional response individual information group LSnmr parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into the addressable individual information group LGnmr;
[0160] FIG. 108 is a schematic representation of the optional links LDnm1. . . LDnmr, and/or the optional descriptions DDnm1. . . DDnmr, and/or the optional prices/values PDnm1. . . PDnmr, and/or the optional images IDnm1. . . IDnmr parsed individually and/or separately, and incorporated into the addressable response information group RGnm from the optional entity body RHnm;
[0161] FIG. 109 is a schematic representation of a typical one of the addressable query information group GInz, based upon certain sorting and/or grouping criteria, having the labelled individual information groups LLnz1 . . . LLnzu, the optional database labelled individual information groups RLnz1 . . . RLnzx, the optional query description QTnz, the optional server descriptions and/or links STnz1 . . . STnzf, and the optional advertisements and/or links LTnz1 . . . LTnzt incorporated into certain typical ones of the typical service and/or information response forms ISn of FIGS. 27A–52C , inclusive.
[0162] FIG. 110 is another schematic representation of a typical one of the addressable query information group GInz, based upon certain sorting and/or grouping criteria, having the labelled individual information groups LLnz1. . . LLnzu, the optional database labelled individual information groups RLnz1. . . RLnzx, the optional query description QTnz, the optional server descriptions and/or links STnz1. . . STnzf, and the optional advertisements and/or links LTnz1. . . LTnzt incorporated into certain typical ones of the typical service and/or information response forms ISn of FIGS. 27A–52C , inclusive;
[0163] FIG. 111 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0164] FIGS. 112A , 112B, 112C, 112D, 112E, 112F, 112G, and 112H depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0165] FIG. 113 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0166] FIGS. 114A , 114B, 114C, 114D, 114E, 114F, 114G, and 114H depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0167] FIG. 115 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0168] FIGS. 116A , 116B, 116C, 116D, 116E, 116F, 116G, and 116H depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0169] FIG. 117 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0170] FIGS. 118A , 118B, 118C, 118D, 118E, 118F, 118G, and 118H depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0171] FIG. 119 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0172] FIGS. 120A , 120B, 120C, 120D, 120E, 120F, 120G, and 120H depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0173] FIG. 121 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0174] FIGS. 122A , 122B, 122C, 122D, 122E, 122F, 122G, and 122H depict a typical combined user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, and an order entry form OFn, which the user Un may use to enter an order, illustrated in partial views;
[0175] FIGS. 123A , 123B, 123C, 123D, 123E, 123F, 123G, and 123H depict the typical combined user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, and the order entry form OFn, which the user Un may use to enter the order, of FIGS. 114A–114H , with typical order information entered therein, illustrated in partial views;
[0176] FIGS. 124A and 124B depict a typical preview form of an order OPn, resulting from submission of the order entry form OFn, of the typical combined user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, and the order entry form OFn, which the user Un may use to enter the order, of FIGS. 114A–114H , with the typical order information entered therein, as shown in FIGS. 123A–123H , illustrated in partial views;
[0177] FIGS. 125A and 125B depict a typical order placement form OLn, having the typical preview form of the order OPn, resulting from submission of the order entry form OFn, of the typical combined user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, and the order entry form OFn, which the user Un may use to enter the order, of FIGS. 114A–114H , with the typical order information entered therein, as shown in FIGS. 123A–123H , or which the user Un may enter through the typical preview form of the order OPn of FIGS. 124A and 124B , illustrated in partial views;
[0178] FIGS. 126A and 126B depict a typical completed order placement form OLn, having a preview of the order OPn, resulting from submission of the order entry form OFn, of the typical combined user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, and the order entry form OFn, which the user Un may use to enter the order, of FIGS. 114A–114H , with the typical order information entered therein, as shown in FIGS. 123A–123H , or which the user Un may enter through the typical preview form of the order OPn of FIGS. 124A and 124B , illustrated in partial views;
[0179] FIGS. 127A and 127B depict a typical order confirmation OCn, resulting from submission of the typical completed order placement form OLn for FIGS. 126A and 126B , illustrated in partial views;
[0180] FIGS. 128A , 128B, and 128C depict a typical e-mail order placement EPn, resulting from submission of the typical completed order placement form OLn of FIGS. 126A and 126B , illustrated in partial views;
[0181] FIGS. 129A , 129B, and 129C depict a typical e-mail confirmation of receipt of order ECn, resulting from submission of the typical completed order placement form OLn of FIGS. 126A and 126B , illustrated in partial views;
[0182] FIGS. 130A and 130B depict a typical e-mail order placement EPn of a portion of the order, resulting from submission of the typical completed order placement form OLn of FIGS. 126A and 126B , illustrated in partial views;
[0183] FIGS. 131A and 131B depict a typical e-mail order placement EPn of another portion of the order, resulting from submission of the typical completed order placement form OLn of FIGS. 126A and 126B , illustrated in partial views;
[0184] FIGS. 132A and 132B depict a typical e-mail order placement EPn of another portion of the order, resulting from submission of the typical completed order placement form OLn of FIGS. 126A and 126B , illustrated in partial views;
[0185] FIG. 133 is a schematic representation of certain typical optional instructions VJnm1. . . VJnk and/or certain additional request links SLn1. . . SLnw;
[0186] FIG. 134 is a schematic representation of other certain typical optional instructions VJnm1. . . VJnk and/or other certain additional request links SLn1. . . SLnw;
[0187] FIG. 135 depicts certain typical additional request links SLn1. . . SLnw;
[0188] FIG. 136 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn therethrough;
[0189] FIG. 137 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn therethrough;
[0190] FIG. 138 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn therethrough;
[0191] FIG. 139 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn therethrough;
[0192] FIG. 140 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn therethrough;
[0193] FIG. 141 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn therethrough;
[0194] FIG. 142 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0195] FIGS. 143A , 143B, 143C, 143D, 143E, 143F, 143G, and 143H depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0196] FIG. 144 depicts another typical completed service and/or information entry request form IFn at the user interface In;
[0197] FIGS. 145A , 145B, 145C, 145D, 145E, 145F, and 145G depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views;
[0198] FIG. 146 depicts another typical completed service and/or information entry request form IFn at the user interface In; and
[0199] FIGS. 147A , 147B, 147C, 147D, 147E, 147F, and 147G depict another typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, illustrated in partial views.
DESCRIPTION
[0200] The preferred embodiments of the present invention will be described with reference to FIGS. 1–147 of the drawings, all references to which include FIGS. 1–147G . Identical elements in the various figures are identified with the same reference alphanumerics.
I. SYSTEM
A. Overview
[0201] FIGS. 1 and 2 show a client-server multitasking system 10 of the present invention, having requestors U1. . . Un (12), hereinafter called users U1. . . Un (12), corresponding user interfaces I1. . . In (14), corresponding clients C1. . . Cn (16), server PS (18), servers S1. . . Sz (20), and optional servers SO1. . . SOp (22), constructed in accordance with the present invention, which reside on a network 24. Each of the users U1. . . Un (12) communicate with the corresponding clients C1. . . Cn (16) through the corresponding user interfaces I1. . . In (14).
[0202] Each of the users U1. . . Un (12) enter corresponding user inputs UI1. . . UIn (25) having one or more same and/or different user requests qu11. . . qunu (26) into the corresponding user interfaces I1. . . In (14), as shown in FIG. 3 . The user requests qu11. . . qunu (26) are communicated from the user interfaces I1. . . In (14) to the corresponding clients C1. . . Cn (16) within corresponding user service and/or information requests iq1. . . iqn (27), having the user requests qu11. . . qunu (26) and other optional information. The users U1. . . Un (12) may enter the corresponding user inputs UI1. . . UIn (25) at the same and/or different times.
[0203] Each of the user interfaces I1. . . In (14) communicate the user service and/or information requests iq1. . . iqn (27) to the corresponding clients C1. . . Cn (16), which optionally format the corresponding user service and/or information requests iq1. . . iqn (27) into corresponding service and/or information requests IQ1. . . IQn (28), as required. Each of the service and/or information requests IQ1. . . IQn (28) have information therein that may be used to formulate one or more same and/or different requests Q11. . . Qnm (29) to be made of one or more of the same and/or different ones of the servers S1. . . Sz (20), which may hereinafter be called server designations S11. . . Snm (30), in accordance with a designation scheme which designates the servers S1. . . Sz (20) to be communicated with corresponding to the requests Q11. . . Qnm (29) as the corresponding server designations S11. . . Snm (30), as shown in FIGS. 2 and 4 . FIG. 4 shows the server designations S11. . . Snm (30) for typical ones of the requests Q11. . . Qnm (29) and a typical one of the servers Sz (20). Each of the requests Q11. . . Qnm (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 S1. . . Sz (20) at the same time and/or different times.
[0204] Each of the service and/or information requests IQ1. . . IQn (28) may be communicated to the server PS (18), which parses, processes, and/or formats the service and/or information requests IQ1. . . IQn (28) into the requests Q11. . . Qnm (29).
[0205] The corresponding clients C1. . . Cn (16) may also and/or alternatively optionally parse, process, and/or format the corresponding user service and/or information requests iq1. . . iqn (27) into one or more of the same and/or different requests Q11. . . Qnm (29) to be made of one or more of the same and/or different ones of the servers S1. . . Sz (20), in accordance with the designation scheme corresponding to the corresponding ones of the server designations S11. . . Snm (30), as required.
[0206] Certain ones of the clients C1. . . Cn (16) may communicate corresponding certain ones of the service and/or information requests IQ1. . . IQn (28) to the server PS (18), which parses, processes and/or formats the certain ones of the service and/or information requests IQ1. . . IQn (28) into certain ones of the requests Q11. . . Qnm (29), as required, and communicates the certain ones of the requests Q11. . . Qnm (29) to the servers S1. . . Sz (20), in accordance with the designation scheme corresponding to the corresponding certain ones of the server designations S11. . . Snm (30).
[0207] Alternate ones of the clients C1. . .Cn (16) may communicate corresponding alternate ones of the requests Q11. . .Qnm (29) to corresponding alternate ones of the servers S1. . . Sz (20), in accordance with the designation scheme corresponding to the corresponding alternate ones of the server designations S11. . . Snm (30).
[0208] Other alternate ones of the clients C1. . . Cn (16) may communicate corresponding other alternate ones of the service and/or information requests IQ1. . . IQn (28) to the server PS (18), which parses, processes and/or formats the other alternate ones of the service and/or information requests IQ1. . . IQn (28) into other alternate ones of the requests Q11. . . Qnm (29), as required, communicates the other alternate ones of the requests Q11. . . Qnm (29) to corresponding other alternate ones of the servers S1. . . Sz (20), in accordance with the designation scheme corresponding to the corresponding other alternate ones of the server designations S11. . . Snm (30); and additionally the other alternate ones of the clients C1. . . Cn (16) may also parse, process, and/or format the user service and/or information requests iq1. . . iqn (27) into one or more of the same and/or different yet other alternate ones of the requests Q11. . . Qnm (29), and communicate the yet other alternate ones of the requests Q11. . . Qnm (29) to corresponding yet other alternate ones of the servers S1. . . Sz (20), in accordance with the designation scheme corresponding to the corresponding yet other alternate ones of the server designations S11. . . Snm (30).
[0209] Each of the service and/or information requests IQ1. . . IQn (28) may, thus, be communicated from the corresponding clients C1. . . Cn (16) to the server PS (18). The requests Q11. . . Qnm (29) may be communicated from the server PS (18) and/or from the corresponding clients C1. . . Cn (16) to the servers S1. . . Sz (20), and may depend upon instructions from and/or generated by the corresponding users U1. . . Un (12), and/or the corresponding user interfaces I1. . . In (14) and/or the corresponding clients C1. . . Cn (16), and/or information generated by the server PS (18) and/or the servers S1. . . Sz (20), and/or ancillary instructions, a combination thereof, and/or other suitable means.
[0210] Each of the servers S1. . . Sz (20) corresponding to the designation scheme S11. . . Snm (30) replies to the server PS (18) and/or the clients C1. . . Cn (16), accordingly, and communicates corresponding responses R11. . . Rnm (32), associated with the requests Q11. . . Qnm (29), to the server PS (18) and/or the clients C1. . . Cn (16) making the requests Q11. . . Qnm (29), as shown in FIG. 2 for typical ones of the requests Q11. . . Qnm (29) and the corresponding responses R11. . . Rnm (32).
[0211] The server PS (18) and/or the appropriate clients C1. . . Cn (16) parse, process, format, sort, group, and/or organize the responses R11. . . Rnm (32) into corresponding service and/or information responses IR1. . . IRn (34), having corresponding parsed, processed, formatted, sorted, grouped, and/or organized service and/or information groups G1. . . Gn (35) (shown later in FIGS. 27A–52C , inclusive) acceptable to the corresponding clients C1. . . Cn (16) and the corresponding respective user interfaces I1. . . In (14). The server PS (18) communicates the appropriate service and/or information responses IR1. . . IRn (34) to the corresponding clients C1. . . Cn (16).
[0212] The clients C1. . . Cn (16) format the service and/or information responses IR1. . . IRn (34) into corresponding user service and/or information responses ir1. . . irn (36), as required, and communicate the user service and/or information responses ir1. . . irn (36) to the corresponding user interfaces I1. . . In (14). The user interfaces I1. . . In (14) incorporate the user service and/or information responses ir1. . . irn (36) into corresponding user responses UR1. . . URn (37), which are derived at the user interfaces I1. . . In (14), and communicated by the user interfaces I1. . . In (14) to the corresponding users U1. . . Un (12). The users U1. . . Un (12) review the corresponding user responses UR1. . . URn (37) at the user interfaces I1. . . In (14) and/or select additional services and/or information therefrom.
B. TYPICAL SERVICE AND/OR INFORMATION ENTRY REQUEST FORMS
[0213] FIGS. 5A , 5B, and 6–10 show typical ones of service and/or information entry request forms IE1. . . IEn (38) at the user interfaces I1. . . In (14), which the users U1. . . Un (12) may communicate typical ones of the user inputs UI1. . . Un (25) thereinto, as requests for information and/or services. The typical ones of the service and/or information entry request forms IE1. . .IEn (38) at the user interfaces I1. . . In (14) shown in FIGS. 5A , 5B, and 6–10 are typical examples of the service and/or information entry request forms IE1. . . IEn (38) at the user interfaces I1. . . In (14), a much larger variety of which is possible. Names and/or links and/or other information are incorporated into the typical ones of the service and/or information entry request forms IE1. . . IEn (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 IE1. . . IEn (38) and the names and/or links and/or information that are possible, and that may be incorporated into the service and/or information entry request forms IE1. . . IEn (38) at the user interfaces I1. . . In (14).
C. TYPICAL COMPLETED SERVICE AND/OR INFORMATION ENTRY REQUEST FORMS
[0214] FIGS. 11–26 show typical ones of completed service and/or information entry request forms IF1. . . IFn (230) at the user interfaces I1. . . In (14).
[0215] FIG. 11 shows a typical particular one of the completed service and/or information entry request forms IF1. . . IFn (230), hereinafter designated the completed service and/or information entry request form IFn (230), at a particular one of the user interfaces I1. . . In (14), hereinafter designated the user interface In (14), having same and different ones of the typical queries QQn1. . . QQnm (53), different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52). Typical same ones of the typical queries QQn1. . . QQnm (53), are “Cat”, “Dog”, and “Mouse”, which are different one from the other.
[0216] FIG. 12 shows the typical completed service and/or information entry request forms IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1. . . QQnm (53), different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52). Typical same ones of the typical queries QQn1. . . QQnm (53) are “Cat”, “Dog”, and “Mouse”, which are different one from the other. Typical same ones of the typical server addresses AQn1. . . AQnm (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 VJn1. . . VJnk (52) have 5 “URL's per Search Engine”, which instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having 5 “URL's per Search Engine”, rather than 10 “URL's per Search Engine”, as instructed in FIG. 11 .
[0217] FIG. 13 shows the typical completed service and/or information entry request forms IFn (230), at the user interface In (14) having a single typical one of the typical queries QQn1. . . QQnm (53) as “Big Elephants”.
[0218] FIGS. 14A , 14B, and 14C show the typical completed service and/or information entry request form IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1. . . QQnm (53), different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (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 QQn1. . . QQnm (53) are “Catcher in the Rye”, “Catcher”, “Rye”, “Sports”, and “Rye Bread”, which are different one from the other. The typical server addresses AQn1. . . AQnm (54) are different one from the other. The typical optional instructions VJn1. . . VJnk (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 Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) within a period of less than the “Timeout (seconds) per Search Engine” specified in the typical optional instructions VJn1. . . VJnk (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 U1 (12) to specify in the event of slow ones of the responses Rn1. . . Rnm (32) from certain ones of the servers S1. . . Sz (20).
[0219] FIG. 15 shows the typical completed service and/or information entry request forms IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1. . . QQnm (53), different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52). Typical same ones of the typical queries QQn1. . . QQnm (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 QQn2. . . QQn4 (53) of “Charles Dickens” of Search 1, above. Likewise, Searches 7, 8, and 9 take on the typical queries QQn7. . . QQn9 (53) of “Oliver Twist” of Search 6, above. Search 5 takes on the typical query QQn5 (53) of “A Tale of Two Cities”.
[0220] The typical optional instructions VJn1. . . VJnk (52) of FIG. 15 have “Separate”, which instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) in separate groups, i.e., grouped by the typical server addresses AQn1. . . AQnm (54), rather than interleaved one with the other, as instructed in FIGS. 11–14 .
[0221] The typical optional instructions VJn1. . . VJnk (52) “Interleaved” of FIGS. 11–14 instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having information and/or services in the responses Rn1. . . Rnm (32) to be interleaved one with the other (or alternating one with the other) into the appropriate addressable query information groups GIn1. . . GInz (63). The labelled individual information groups LLn11. . . LLnzu (86) in the addressable query information groups GIn1. .. GInz (63) are alternatingly interleaved one with the other and labelled and/or identified and associated correspondingly with the responses Rn1. . . Rnm (32) from the servers S1. . .Sz (20). The “Interleaved” information and/or services may typically be incorporated into the appropriate addressable query information groups GIn1. . . GInz (63) in substantially the same sequence as the information and/or services are in the responses Rn1. . . Rnm (32) communicated from the servers S1. . . Sz (20). However, other sorting/grouping criteria may optionally be used, as will be discussed later.
[0222] The typical server addresses AQn1. . . AQnm (54) are different one from the other in FIG. 15 . The typical optional instructions VJn1. . . VJnk (52) also instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having 5 “Searches per Group”, rather than 3 “Searches per Group”, as in FIGS. 11–14 . The typical optional instructions VJn1. . . VJnk (52) also instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having 8 “URL's per Search Engine”.
[0223] FIG. 16 shows the typical completed service and/or information entry request form IFn (230), at the user interface In (14), having the same ones of the typical queries QQn1. . . QQnm (53), different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52). The typical optional instructions VJn1. . . VJnk (52) have “URL Details” as “List”, which instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) “List” format rather than “Summary” format, as instructed in FIGS. 11–15 . The “URL Details” as “Summary” instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37) showing descriptions and/or other information and/or services, in addition to links, in the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), while “URL Details” as “List” instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37) showing only links in the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14).
[0224] The typical optional instructions VJn1. . . VJnk (52) have 25 “URL's per Search Engine”, which instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having 25 “URL's per Search Engine”. The typical optional instructions VJn1. . . VJnk (52) also instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having 9 “Searches per Group”. The typical optional instructions VJn1. . . VJnk (52) also instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (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 VJn1. . . VJnk (52) also instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) to use a 2 second “Timeout (seconds) per Search Engine”.
[0225] FIG. 17 shows another one of the typical completed service and/or information entry request form IFn (230), at the user interface In (14), having the same ones of the typical queries QQn1. . . QQnm (53), different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52). The typical optional instructions VJn1. . . VJnk (52) have 18 “URL's per Search Engine”, which instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having 18 “URL's per Search Engine”. The typical optional instructions VJn1. . . VJnk (52) also instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (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”.
[0226] FIG. 18 shows another one of the typical completed service and/or information entry request form IFn (230), at the user interface In (14), having different ones of the typical queries QQn1. . . QQnm (53), different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52).
[0227] FIG. 19 shows another one of the typical completed service and/or information entry request form IFn (230), at the user interface In (14), having different ones of the typical queries QQn1. . . QQnm (53), as in FIG. 18 , the same ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52).
[0228] FIG. 20 shows the typical completed service and/or information entry request forms IFn (230), at the user interface In (14) having a single typical one of the typical queries QQn1. . . QQnm (53) as “sports”.
[0229] FIG. 21 show another one of the typical completed service and/or information entry request form IFn (230), at the user interface In (14) having a single typical one of the typical queries QQn1. . . QQnm (53) as “television”.
[0230] FIG. 22 shows another one of the typical completed service and/or information entry request form IFn (230), at the user interface In (14), having different ones of the typical queries QQn1. . . QQnm (53), i.e., “sports” and “television”, different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52).
[0231] FIG. 23 shows another one of the typical completed service and/or information entry request form IFn (230), at the user interface In (14), having the same ones of the typical queries QQn1. . . QQnm (53), i.e., “weather”, different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52).
[0232] FIG. 24 shows another one of the typical completed service and/or information entry request form IFn (230), at the user interface In (14), having different ones of the typical queries QQn1. . . QQnm (53), .i.e., “education”, “universities,” and “training”, different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52).
[0233] FIG. 25 shows another one of the typical completed service and/or information entry request form IFn (230), at the user interface In (14), having different ones of the typical queries QQn1. . . QQnm (53), .i.e., “weather”, “climate,” “training”, different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52).
[0234] FIG. 26 shows another one of the typical completed service and/or information entry request form IFn (230), at the user interface In (14) having a single typical one of the typical queries QQn1. . . QQnm (53) as “weather”.
[0235] The typical ones of the completed service and/or information entry request forms IF1. . . IFn (230) at the user interfaces I1. . . In (14) shown in FIGS. 11–26 are typical examples of the completed service and/or information entry request forms IF1. . . IFn (230) at the user interfaces I1. . . In (14), a much larger variety of which is possible. Typical queries QQn1. . . QQnm (53), typical server addresses AQn1. . . AQnm (54), and typical optional instructions VJn1. . . VJnk (52) in the typical ones of the completed service and/or information entry request forms IF1. . . IFn (230) at the user interfaces I1. . . In (14) shown in FIGS. 11–26 are typical examples for illustrative purposes, and are not intended to limit the substantially infinite variety of the queries QQn1. . . QQnm (53), the server addresses AQn1. . . AQnm (54), and the optional instructions VJn1. . . VJnk (52) that may be entered into the service and/or information entry request forms IE1. . . IEn (38), to derive the completed service and/or information entry request forms IF1. . . IFn (230) at the user interfaces I1. . . In (14). Likewise, names and/or links and/or other information are incorporated into the typical ones of the completed service and/or information entry request forms IF1. . . IFn (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 IF1. . . IFn (230) and the names and/or links and/or information that are possible, and that may be incorporated into the completed service and/or information entry request forms IF1. . . IFn (230) at the user interfaces I1. . . In (14).
[0236] Any ones of the typical queries QQn1. . . QQnm (53), any values within the ranges allowable for the typical server addresses AQn1. . . AQnm (54), and any values allowable for the typical optional instructions VJn1. . . VJnk (52) may be incorporated into the typical ones of service and/or information entry request forms IE1. . . IEn (38) at the user interfaces I1. . . In (14) FIGS. 5A , 5B, and 6–10, which the users U1. . . Un (12) enter to complete the typical ones of the completed service and/or information entry request forms IF1. . . IFn (230) at the user interfaces I1. . . In (14) of FIGS. 11–26 .
[0237] 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 into the typical ones of service and/or information entry request forms IE1IEn (38) at the user interfaces I1. . . In (14) of FIGS. 5A , 5B, and 6–10, which the users U1. . . Un (12) enter to complete the typical ones of the completed service and/or information entry request forms IF1. . . IFn (230) at the user interfaces I1. . . In (14) of FIGS. 11–26 .
[0238] The users U1. . . Un (12), for example, may enter: the typical queries QQn1. . . QQnm (53); any values within the ranges allowable for the typical server addresses AQn1. . . AQnm (54); and any values allowable for the typical optional instructions VJn1. . . VJnk (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” into the typical ones of service and/or information entry request forms IE1. . . IEn (38) at the user interfaces I1. . . In (14) of FIGS. 5A , 5B, and 6–10, which the users U1. . . Un (12) enter to complete the typical ones of the completed service and/or information entry request forms IF1. . . IFn (230) at the user interfaces I1. . . In (14). The typical ones of the user responses UR1. . . URn (37), as typical service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14), may then be communicated to the corresponding ones of the users U1. . . Un (12), accordingly. FIGS. 27A–52C , inclusive, show typical ones of the user responses UR1. . . URn (37), as the typical service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14), which may be communicated to the corresponding ones of the users U1. . . Un (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.
D. TYPICAL SERVICE AND/OR INFORMATION RESPONSE FORMS
[0239] FIGS. 27A–52C , inclusive, show typical ones of the user responses UR1. . . URn (37), as typical service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14), which may be communicated to the corresponding ones of the users U1. . . Un (12). A typical particular one of the user responses UR1. . . URn (37), as a particular typical one of the service and/or information response forms IS1. . . ISn (39) at the particular one of the user interfaces I1. . . In (14) may hereinafter be designated as the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14).
[0240] FIGS. 27A–52C , inclusive, also show information in each of the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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 in each of the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interfaces In (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.
[0241] FIGS. 27A–29C , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), with reference to FIG. 11 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into Group I, Group II, and Group III, respectively.
[0242] The user Un (12) may optionally select Group II, and/or Group III from the typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) of FIGS. 27A–27C , and/or Group I and/or Group III at the user interface In (14) of FIGS. 28A–28C , and/or Group I, and/or Group II at the user interface In (14) of FIGS. 29A–29C . The user Un (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 IEn (38) at the user interfaces I1. . . In (14), and completing the typical completed service and/or information entry request form IFn (230), at the user interface In (14) with the appropriate selections to be made.
[0243] The user Un (12) may also make other selections by entering such into the typical one of the service and/or information entry request form IEn (38) at the user interfaces I1. . . In (14), and completing the typical completed service and/or information entry request form IFn (230), at the user interface In (14) with the appropriate selections to be made, and/or by making such selections through the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14). The user Un (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.
[0244] FIGS. 27A–29C , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), having the service and/or information group Gn (35) having the addressable query information groups GIn1. . . GInz (63) therein, the labelled individual information groups LLn11. . . LLnzu (86) in the addressable query information groups GIn1. . . GInz (63), the additional request links SLn1. . . SLnw (71), the optional service and/or information entry request form IEn (38), and other information and/or services therein, resulting from the same and different ones of the typical queries QQn1. . . QQnm (53), different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52).
[0245] FIGS. 27A–29C , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), resulting from the typical ones of the queries QQn1. . . QQnm (53), “Cat”, “Mouse”, and “Dog”, the same ones of the typical queries QQn1. . . QQn3 (53) and QQn9 (53) being “Cat”, other same ones of the typical queries QQn4 (53) and QQn7 (53) being “Mouse”, but different from “Cat”, and other same ones of the typical queries QQn5, QQn6 (53), and QQn8 (53) being “Dog”, but different from “Cat” and/or “Mouse”, the typical ones of the queries QQn1. . . QQnm (53), “Cat”, “Dog”, and “Mouse”, being different one from the other.
[0246] The typical same ones of the typical queries QQn1. . . QQn3 (53) as “Cat” are incorporated into the addressable query information groups GIn1 (63) of Group I.
[0247] The typical one of the queries QQn4 (53) as “Mouse” is incorporated into the addressable query information groups GIn1 (63) of Group II. The other same ones of the typical queries QQn5 and QQn6 (53) as “Dog are incorporated into the addressable query information groups GIn2 (63) of Group II.
[0248] The typical one of the queries QQn7 (53) as “Mouse” is incorporated into the addressable query information groups GIn1 (63) of Group III. The typical one of the queries QQn8 (53) as “Dog” is incorporated into the addressable query information groups GIn2 (63) of Group III. The typical one of the queries QQn9 (53) as “Cat” is incorporated into the addressable query information groups GIn3 (63) of Group III.
[0249] FIGS. 27A–29C , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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.
[0250] The typical optional instructions VJn1. . . VJnk (52) “URL's per Search Engine” as “10” instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having substantially “10” ones of the typical labelled individual information groups LLn11. . . LLnzu (86) per each one of the typical server addresses AQn1. . . AQnm (54) in the typical “Current Group”, retrieved from the responses Rn1. . . Rnm (32). In this case, the typical labelled individual information groups LLn11. . . LLnzu (86) may be “Uniform Resource Locators”, or “URL's” and/or other services and/or information associated therewith.
[0251] The typical optional instructions VJn1. . . VJnk (52) “Searches per Group” as “3” instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having “3 Searches per Group” for the group selected, which is designated in the typical optional instructions VJn1. . . VJnk (52) having “Group” as “1”.
[0252] “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 QQn1. . . QQn3 (53) of “Cat”, “Cat”, “Cat” and the typical server addresses AQn1. . . AQn3 (54) of WebCrawler®, Altavista®, and Lycos®.
[0253] The “Next Group: II” and/or the “Group: III” may be selected from the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14). If the “Next Group: II” is selected, then Search 4, Search 5, and Search 6, having the typical queries QQn4. . .QQn6 (53) of “Mouse”, “Dog”, and “Dog” and the typical server addresses AQn4. . . AQn6 (54) of Infoseek®, Excite®, and Yahoo® are selected and returned as the typical service and/or information response forms ISn (39) at the user interface In (14). If the “Group: III” is selected, then Search 7, Search 8, and Search 9, having the typical queries QQn7. . . QQn9 (53) of “Mouse”, “Dog”, and “Cat” and the typical server addresses AQn7. . . AQn9 (54) of LookSmart®, HotBot®, and Dejanews® are selected and returned as the typical service and/or information response forms ISn (39) at the user interface In (14).
[0254] The typical optional instructions VJn1. . . VJnk (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 in the “Current Group”.
[0255] 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.
[0256] The typical optional instructions VJn1. . . VJnk (52) “Page” as “1” instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (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, in the “Current Group”.
[0257] The “Next Page” and/or other pages may be selected, which in this typical case may be Pages 1–25, from the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (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, in the “Current Group” are selected and returned as the typical service and/or information response form ISn (39) at the user interface In (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, in the “Current Group” are selected and returned as the typical service and/or information response form ISn (39) at the user interface In (14).
[0258] The typical optional instructions VJn1. . . VJnk (52) of “Search Engine Results” as “Interleave” instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having ones of the typical labelled individual information groups LLn11. . . LLnzu (86) and/or other services and/or information associated with the typical queries QQn1. . . QQnm (53) and the typical server addresses AQn1. . . AQnm (54) in the typical “Current Group”, portions of which have been retrieved from the responses Rn1. . . Rnm (32), interleaved one with the other (or alternating one with the other) in the appropriate addressable query information groups GIn1. . . GInz (63). The “Interleaved” information and/or services may typically be incorporated into the appropriate addressable query information groups GIn1. . . GInz (63) in the “Current Group” in substantially the same sequence as the information and/or services are in the responses Rn1. . . Rnm (32) communicated from the servers S1. . . Sz (20). However, other sorting/grouping criteria may optionally be used, as will be discussed later. In this case, the typical labelled individual information groups LLn11. . . LLnzu (86) may be “Uniform Resource Locators”, or “URL's” and/or other services and/or information associated therewith.
[0259] “Separate” may be selected from the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), which instructs the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) in “Separate” groups, i.e., grouped by the typical server addresses AQn1. . . AQnm (54) incorporated into the appropriate addressable query information groups GIn1. . . GInz (63) in the “Current Group”.
[0260] The typical optional instructions VJn1. . . VJnk (52) “URL Details” as “Summary” instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37) showing the typical labelled individual information groups LLn11. . . LLnzu (86) showing descriptions and/or other information and/or services, in addition to links, and/or URL's in the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14).
[0261] “List” may be selected from the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), which instructs the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) typically showing only links to URL's and/or other links in the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14).
[0262] The “Timeout (seconds) per Search Engine” instructs the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) within a period of less than the “Timeout (seconds) per Search Engine” specified in the typical optional instructions VJn1. . . VJnk (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 U1 (12) to specify in the event of slow ones of the responses Rn1. . . Rnm (32) from certain ones of the servers S1. . . Sz (20).
[0263] If the time it takes to retrieve information from certain ones of the servers S1. . . Sz (20) having the typical ones of the queries QQn1. . . QQnm (53) at the typical ones of the server addresses AQn1. . . AQnm (54) is greater than the “Timeout” selected, then the client Cn (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 S1. . . Sz (20), as shown later in FIGS. 44A–44C . Information and/or services only from those ones of the servers S1. . . Sz (20) responding within the “Timeout” period are then incorporated into the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14).
[0264] FIGS. 30A–32B , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), with reference to FIG. 12 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into Group I, Group II, and Group III, respectively.
[0265] FIGS. 30A–32B , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), having the service and/or information group Gn (35) having the addressable query information groups GIn1. . . GInz (63) therein, the labelled individual information groups LLn11. . . LLnzu (86) in the addressable query information groups GIn1. . . GInz (63), the additional request links SLn1. . . SLnw (71), the optional service and/or information entry request form IEn (38), and other information and/or services therein, resulting from the same and different ones of the typical queries QQn1. . . QQnm (53), and the same and different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52), rather than results just from different ones of the typical server addresses AQn1. . . AQnm (54) as in FIGS. 27A–29C , inclusive.
[0266] FIGS. 30A–32B , inclusive, show the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), resulting from the typical ones of the queries QQn1. . . QQnm (53), “Cat”, “Dog”, and “Mouse”, the same ones of the typical queries QQn1. . . QQn3 (53), and QQn9 (53) being “Cat”, other same ones of the typical queries QQn2 (53), QQn5 (53), QQn6 (53), and QQn8 (53) being “Dog”, but different from “Cat”, and other same ones of the typical queries QQn4 and QQn7 (53) being “Mouse”, but different from “Cat” and/or “Dog”, the typical ones of the queries QQn1. . . QQnm (53), “Cat”, “Dog”, and “Mouse”, being different one from the other.
[0267] FIGS. 30A–32B , inclusive, also show the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), resulting from the typical ones of the server addresses AQn1. . . AQnm (54), HotBot®, WebCrawler®, Yahoo®, LookSmart®, and Dejanews®, the same ones of the typical server addresses AQn1 and AQn2 (54) being Hotbot®, other same ones of the typical server addresses AQn3. . . AQn5 (54), being WebCrawler®, but different from HotBot®, another one of the server addresses AQn6 (54), being Yahoo®, but different from HotBot® and/or WebCrawler®, another one of the server addresses AQn7 (54), being LookSmart®, but different from HotBot® and/or WebCrawler® and/or Yahoo®, and other same ones of the typical server addresses AQn8 (54) and QQn9 (54) being Dejanews®, but different from HotBot® and/or WebCrawler® and/or Yahoo® and/or LookSmart®, the typical ones of the server addresses AQn1 . . . AQnm (54), HotBot®, WebCrawler®, Yahoo®, LookSmart®, and Dejanews®, being different one from the other.
[0268] The typical same ones of the typical queries QQn1 and QQn3 (53) as “Cat” are incorporated into the addressable query information groups GIn1 (63) of Group I. The typical one of the queries QQn2 (53) as “Cat” is incorporated into the addressable query information groups GIn2 (63) of Group II.
[0269] The typical one of the queries QQn4 (53) as “Mouse” is incorporated into the addressable query information groups GIn1 (63) of Group II. The other same ones of the typical queries QQn5 and QQn6 (53) as “Dog are incorporated into the addressable query information groups GIn2 (63) of Group II.
[0270] The typical one of the queries QQn7 (53) as “Mouse” is incorporated into the addressable query information groups GIn1 (63) of Group III. The typical one of the queries QQn8 (53) as “Dog” is incorporated into the addressable query information groups GIn2 (63) of Group III. The typical one of the queries QQn9 (53) as “Cat” is incorporated into the addressable query information groups GIn3 (63) of Group III.
[0271] FIGS. 30A–32B , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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.
[0272] Now again, FIGS. 30A–32B , inclusive, show the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), resulting from the same and different ones of the typical queries QQn1. . . QQnm (53), the same and different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52), but which also result from the typical optional instructions VJn1. . . VJnk (52) having 5 “URL's per Search Engine”, which instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having 5 “URL's per Search Engine”, rather than 10 “URL's per Search Engine”, as in FIGS. 27A–29C , inclusive.
[0273] FIGS. 33A–33C show a typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), with reference to FIG. 13 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into Group I, having the typical ones of the queries QQn1. . . QQnm (53) as “Big Elephants”. The user Un (12) may optionally select Group II, and/or Group III from the typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) of FIGS. 33A–33C .
[0274] FIGS. 33A–33C show the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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 from the typical one of the user response URn 1 (37), as the typical service and/or information response forms ISn (39) at the user interface In (14) of FIGS. 33A–33C .
[0275] FIGS. 34A–36C , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), with reference to FIGS. 14A , 14B, and 14C, respectively, having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into 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 in the typical one of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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 Un (12). The user Un (12) may select the items and/or items to order from such information that the user Un (12) considers to be important. The user Un (12) may place the order and/or orders directly through the links and/or URL's in the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14). The user Un (12) may additionally and/or alternatively collect the order and/or orders in a shopping cart and/or shopping carts associated with the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), and place the order and/or orders through the client Cn (16) and/or the server PS (18).
[0276] Now again, FIGS. 34A–36C , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), having the service and/or information group Gn (35) having the addressable query information groups GIn1. . . GInz (63) therein, the labelled individual information groups LLn11. . . LLnzu (86) in the addressable query information groups GIn1. . . GInz (63), the additional request links SLn1. . . SLnw (71), the optional service and/or information entry request form IEn (38), and other information and/or services therein, resulting from the same and different ones of the typical queries QQn1. . . QQnm (53), different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52). Typical same ones of the typical queries QQn1. . . QQnm (53) are “Catcher in the Rye”, “Catcher”, “Rye”, “Sports”, and “Rye Bread”, which are different one from the other. The typical server addresses AQn1. . .AQnm (54) are different one from the other.
[0277] FIGS. 34A–36C , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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.
[0278] Now again, the typical optional instructions VJn1. . . VJnk (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 Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) within a period of less than the “Timeout (seconds) per Search Engine” specified in the typical optional instructions VJn1. . . VJnk (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 U1 (12) to specify in the event of slow ones of the responses Rn1. . . Rnm (32) from certain ones of the servers S1. . . Sz (20).
[0279] FIGS. 37A–39C , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), with reference to FIG. 15 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into 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.
[0280] FIGS. 37A–39C , inclusive, show typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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.
[0281] Now again, the typical optional instructions VJn1. . . VJnk (52) have “Separate”, which instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) in separate groups, i.e., grouped by the typical server addresses AQn1. . . AQnm (54), rather than interleaved one with the other, as in FIGS. 27A–36C , inclusive.
[0282] FIGS. 40A–40M show a typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), with reference to FIG. 16 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into a single Group.
[0283] FIGS. 40A–40M show the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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 from the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14) of FIGS. 40A–40M .
[0284] Now again, the “URL Details” as “Summary” instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37) showing descriptions and/or other information and/or services, in addition to links, in the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), as in FIGS. 27A–39C , inclusive, while “URL Details” as “List” instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37) showing only links and/or URL's in the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), as in FIGS. 40A–40M .
[0285] FIGS. 41A–41F show a typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), with reference to FIG. 17 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into Group II.
[0286] FIGS. 41A–41F show the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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 from the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14) of FIGS. 41A–41F .
[0287] FIGS. 42A–42O show a typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), with reference to FIG. 18 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into a single Group.
[0288] FIGS. 42A–42O show the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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”.
[0289] FIGS. 43A–43O show a typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), with reference to FIG. 19 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into a single Group.
[0290] FIGS. 43A–43O show the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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”.
[0291] FIGS. 44A–44C show a typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), with reference to FIG. 20 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into Group I. FIGS. 44A–44C also show the results of a “Timeout” occurring.
[0292] FIGS. 44A–44C show the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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 from the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14) of FIGS. 44A–44C .
[0293] FIGS. 45A–45C show a typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), with reference to FIG. 21 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into Group I.
[0294] FIGS. 45A–45C show the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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 from the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14) of FIGS. 45A–45C .
[0295] FIGS. 46A–46E show a typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), with reference to FIG. 22 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into Group I. FIGS. 46A–46E also show the links/advertisements/images automatically inserted into the typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), which may be associated with the typical queries QQn1. . . QQnm (53). In the typical case shown in FIGS. 46A–46E , links/advertisements/images associated with the typical queries QQn1. . . QQnm (53) of “sports” and “television” have been automatically inserted into the typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14).
[0296] FIGS. 46A–46E show the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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 from the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14) of FIGS. 46A–46E .
[0297] FIGS. 47A–47C and 48A–48D show a typical ones of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), with reference to FIG. 23 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into 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 with the typical queries QQn1. . . QQnm (53), and which additionally and/or alternatively may function as an internal search engine. The full text search results are incorporated from the additional optional responses RAn1. . . RAnm (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 into the typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), in addition to the typical queries QQn1. . . QQnm (53) at the typical ones of the server addresses AQn1. . . AQnm (54). In the typical case shown in FIGS. 47A–47C and 48A–48D, full text search results associated with the typical query QQn1. . . QQnm (53) of “weather” have been automatically inserted into the typical ones of the user responses URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14), in addition to the typical queries QQn1. . . QQnm (53) at the typical ones of the server addresses AQn1. . . AQnm (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 .
[0298] FIGS. 47A–47C and 48A–48D show the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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 from the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14) of FIGS. 47A–47C and 48A–48D.
[0299] FIGS. 49A–49I show a typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface ISn (14), with reference to FIG. 24 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into Group I. FIGS. 49A–49I also show the typical results of the server PS (18) and/or the client Cn (16) automatically optionally spidering the sites obtained as a result of the typical queries QQn1. . . QQnm (53) at the typical ones of the server addresses AQn1. . . AQnm (54), and incorporating the spidered results into the optional database 41 and/or the optional database 42. The spidered results incorporated into 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 QQn1. . . QQnm (53) at the typical ones of the server addresses AQn1. . . AQnm (54), and the full text search results may be obtained from the additional optional responses RAn1. . . RAnm (40).
[0300] FIGS. 49A–49I also show the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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 from the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14) of FIGS. 49A–49I .
[0301] FIGS. 50A–50K show a typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), with reference to FIG. 25 , having information and/or services from the responses Rn1. . . Rnm (32) incorporated therein, and incorporated into Group I. FIGS. 50A–50K also show the typical results of the server PS (18) and/or the client Cn (16) semi-automatically optionally spidering the sites obtained as a result of the typical queries QQn1. . . QQnm (53) at the typical ones of the server addresses AQn1. . . AQnm (54), and incorporating the spidered results into the optional database 41 and/or the optional database 42. The spidered results incorporated into 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 QQn1. . . QQnm (53) at the typical ones of the server addresses AQn1. . . AQnm (54), and the full text search results may be obtained from the additional optional responses RAn1. . . RAnm (40).
[0302] The user Un (12) may optionally select those sites to be spidered and incorporated into the optional database 41 and/or the optional database 42, as in the typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) in FIGS. 50A–50K . FIGS. 51A–51G show the typical results of the server PS (18) and/or the client Cn (16) optionally spidering the sites obtained as a result of the typical queries QQn1. . . QQnm (53) at the typical ones of the server addresses AQn1. . . AQnm (54), and input resulting from user selection of sites to be spidered from FIGS. 50A–50K , and incorporating the spidered results into the optional database 41 and/or the optional database 42.
[0303] The results of the optional spidering typically obtained from the typical process used with FIGS. 50A–50K and 51A–51G may be substantially the same as the typical process used with 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 and 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 into the database 41 and/or the optional database 42.
[0304] FIGS. 50A–50K also show the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (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 from the typical one of the user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In(14) of FIGS. 50A–50K .
[0305] FIGS. 52A–52C show a typical one of the user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14), with reference to FIG. 26 , having information and/or services from the additional optional responses RAn1. . . RAnm (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 with the typical queries QQn1. . . QQnm (53). The full text search results are incorporated from the additional optional responses RAn1. . . RAnm (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 .
[0306] The typical ones of the user responses UR1. . . URn (37), as typical service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14) shown in FIGS. 27A–52C , inclusive, are typical examples of the user responses UR1. . . URn (37), as typical service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14), a much larger variety of which is possible. FIGS. 27A–52C , inclusive, illustrate typical examples of typical ones of the user responses UR1. . . URn (37), as typical service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14) to the typical queries QQn1. . . QQnm (53), the typical ones of the server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52) having been entered into the typical ones of the completed service and/or information entry request forms IF1. . . IFn (230) at the user interfaces I1. . . In (14) shown in FIGS. 11–26 .
[0307] The typical examples of the typical ones of the user responses UR1. . . URn (37), as typical service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14) are for illustrative purposes, and are not intended to limit the substantially infinite variety of the user responses UR1. . . URn (37), as the service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14), and queries QQn1. . . QQnm (53), the server addresses AQn1. . . AQnm (54), and the optional instructions VJn1. . . VJnk (52) that may be entered into the service and/or information entry request forms IE1. . . IEn (38), to derive the to the completed service and/or information entry request forms IF1. . . IFn (230), and which result in the user responses UR1. . . URn (37), as the service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14). Likewise, names and/or links and/or other information are incorporated into the typical ones of the user responses UR1. . . URn (37), as the service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14), shown in FIGS. 27A–52C , inclusive, for illustrative purposes, and are not intended to limit the large variety of the user responses UR1. . . URn (37), as the service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14), and the names and/or links and/or information that are possible, and that may be incorporated into the user responses UR1. . . URn (37), as the service and/or information response forms IS1. . . ISn (39) at the user interfaces I1. . . In (14).
E. OTHER TYPICAL SERVICE AND/OR INFORMATION ENTRY REQUEST FORMS, OTHER TYPICAL COMPLETED SERVICE AND/OR INFORMATION ENTRY REQUEST FORMS, AND OTHER TYPICAL SERVICE AND/OR INFORMATION RESPONSE FORMS
[0308] FIG. 111 shows another typical completed service and/or information entry request form IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1. . . QQnm (53), different ones of the typical server addresses AQn1. . . AQnm (54), and the typical optional instructions VJn1. . . VJnk (52). Typical same ones of the typical queries QQn1. . . QQnm (53) are “Cat”; “Dog”; and “Mouse”, which are different one from the other. Typical and same ones of the typical server addresses AQn1. . . AQnm (54) are Amazon®, Borders®, and BarnesandNoble®, which are different one from the other, and which are also different from Google®. The typical optional instructions VJn1. . . VJnk (52) having “URL's per Search Engine” as “10” and “Searches per Group” as “9”, the returns substantially “10 URL's per Search Engine” multiplied by “9 Searches per Group”, which is substantially “90 URL's per Group”, and/or other services and/or information associated therewith, returned in the “Current Group”, and Search Engine Results as “Interleaved”. In this case, however, order entry boxes 402 are also returned, which allow the user U1 (12) to order services, merchandise, information, other items and/or objects through the user interface I1 (14), as shown in FIGS. 112A–112H . The user U1(12) can place orders with sites that support such services and also obtain information on queried subjects from sites that support returning information and/or services.
[0309] The typical optional instructions VJn1. . . VJnk (52) “Interleaved” of FIG. 111 instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having information and/or services in the responses Rn1. . . Rnm (32) to be interleaved one with the other (or alternating one with the other) in the appropriate addressable query information groups GIn1. . . GInz (63). The labelled individual information groups LLn11. . . LLnzu (86) in the addressable query information groups GIn1. . . GInz (63) are alternatingly interleaved one with the other and labelled and/or identified and associated correspondingly with the responses Rn1. . . Rnm (32) from the servers S1. . . Sz (20). The “Interleaved” information and/or services may typically be incorporated into the appropriate addressable query information groups GIn1 . . . GInz (63) in substantially the same sequence as the information and/or services in the responses Rn1. . . Rnm (32) communicated from the servers S1. . . Sz (20). However, other sorting/grouping criteria may optionally be used, as will be discussed.
[0310] FIG. 113 shows another typical completed service and/or information entry request form IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1 . . . QQnm (53), different ones of the typical server addresses AQn1 . . . AQnm (54), and the typical optional instructions VJn1 . . . VJnk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Combined $[a–z]”.
[0311] The typical optional instructions VJn1 . . . VJnk (52) “Combined $[a–z]” of FIG. 113 instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having information and/or services in the responses Rn1 . . . Rnm (32) to be sorted in ascending order first numerically, and then alphabetically, in the appropriate addressable query information groups GIn1 . . . GInz (63). Items having prices will be sorted numerically by price, with lowest price first. The labelled individual information groups LLn11 . . . LLnzu (86) in the addressable query information groups GIn1 . . . GInz (63) are grouped and sorted in ascending order one with the other and labelled and/or identified and associated correspondingly with the responses Rn1 . . . Rnm (32) from the servers S1 . . . Sz (20). The “Combined $[a–z]” information and/or services may typically be incorporated into the appropriate addressable query information groups GIn1 . . . GInz (63) in accordance with the “Combined $[a–z]” optional instructions VJn1. . . VJnk (52), and communicated in the other typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, as shown in FIGS. 114A–114H .
[0312] FIGS. 114A–114H also depict typical order boxes 402 of a typical order entry form OFn, which is communicated with the typical user response URn, to enter quantities that the user Un may elect to order, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, which the user Un may use to enter an order.
[0313] FIG. 115 shows another typical completed service and/or information entry request form IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1 . . . QQnm (53), different ones of the typical server addresses AQn1 . . . AQnm (54), and the typical optional instructions VJn1 . . . VJnk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Combined $[z–a]”.
[0314] The typical optional instructions VJn1 . . . VJnk (52) “Combined $[z–a]” of FIG. 115 instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having information and/or services in the responses Rn1 . . . Rnm (32) to be sorted in descending order first alphabetically, and then numerically, in the appropriate addressable query information groups GIn1 . . . GInz (63). Items having prices will be sorted numerically by price, with highest price first. The labelled individual information groups LLn11 . . . LLnm (86) in the addressable query information groups GIn1 . . . GInz (63) are grouped and sorted in descending order one with the other and labelled and/or identified and associated correspondingly with the responses Rn1 . . . Rnm (32) from the servers S1 . . . Sz (20). The “Combined $[z–a]” information and/or services may typically be incorporated into the appropriate addressable query information groups GIn1 . . . GInz (63) in accordance with the “Combined $[z–a]” optional instructions VJn1 . . . VJnk (52), and communicated in the other typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, as shown in FIGS. 116A–116H .
[0315] FIG. 117 shows another typical completed service and/or information entry request form IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1 . . . QQnm (53), different ones of the typical server addresses AQn1 . . . AQnm (54), and the typical optional instructions VJn1 . . . VJnk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Separate”. The typical optional instructions VJn1 . . . VJnk (52) of FIG. 117 have “Separate”, which instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) in separate groups, i.e., grouped by the typical server addresses AQn1 . . . AQnm (54), rather than interleaved one with the other, and communicated in the other typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, as shown in FIGS. 118A–118H .
[0316] FIG. 119 shows another typical completed service and/or information entry request form IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1 . . . QQnm (53), different ones of the typical server addresses AQn1 . . . AQnm (54), and the typical optional instructions VJn1 . . . VJnk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Separate $[a–z]”. The typical optional instructions VJn1 . . . VJnk (52) of FIG. 119 have “Separate $[a–z]”, which instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) in separate groups, sorted in ascending order first numerically, and then alphabetically, in the appropriate addressable query information groups GIn1 . . . GInz (63), i.e., grouped by the typical server addresses AQn1 . . . AQnm (54), and communicated in the other typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, as shown in FIGS. 120A–120H . Items having prices will be sorted numerically by price, with lowest price first within each of the typical server addresses AQn1 . . . AQnm (54) groups.
[0317] FIG. 121 shows another typical completed service and/or information entry request form IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1 . . . QQnm (53), different ones of the typical server addresses AQn1 . . . AQnm (54), and the typical optional instructions VJn1 . . . VJnk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Separate $[z–a]”. The typical optional instructions VJn1 . . . VJnk (52) of FIG. 121 have “Separate $[z–a]”, which instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response forms ISn (39) at the user interface In (14) in separate groups, sorted in descending order alphabetically, and then numerically, in the appropriate addressable query information groups GIn1 . . . GInz (63), i.e., grouped by the typical server addresses AQn1 . . . AQnm (54), and communicated in the other typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, as shown in FIGS. 122A–122H . Items having prices will be sorted numerically by price, with highest price first within each of the typical server addresses AQn1 . . . AQnm (54) groups.
[0318] FIGS. 123A–123H depict the typical combined user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, and the order entry form OFn, which the user Un may use to enter the order, of FIGS. 114A–114H , with typical order information entered therein.
[0319] FIGS. 124A–124B depict a typical preview form of an order OPn, resulting from submission of the quantities to be ordered in order boxes 402 of the order entry form OFn of FIGS. 114A–114H , of the typical user response URn, as the typical service and/or information response form ISn at the user interface In, with the typical order information entered therein, as shown in FIGS. 123A–123H .
[0320] FIGS. 125A–125B depict a typical order placement form OLn, having the typical preview form of the order OPn, resulting from submission of the order entry form OFn, of the typical combined user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, and the order entry form OFn, which the user Un may use to enter the order, of FIGS. 114A–114H , with the typical order information entered therein, as shown in FIGS. 123A–123H , or which the user Un may enter through the typical preview form of the order OPn of FIGS. 124A–124B .
[0321] FIGS. 126A–126B depict a typical completed order placement form OLn, having a preview of the order OPn, resulting from submission of the order entry form OFn, of the typical combined user response URn , as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, and the order entry form OFn, which the user Un may use to enter the order, of FIGS. 114A–114H , with the typical order information entered therein, as shown in FIGS. 123A–123H , or which the user Un may enter through the typical preview form of the order OPn of FIGS. 124A–124B .
[0322] FIGS. 127A–127B depict a typical order confirmation OCn, resulting from submission of the typical completed order placement form OLn of FIGS. 126A–126B .
[0323] The orders are also confirmed automatically by e-mail, with e-mailed confirmations being sent to the user Un (12), i.e., the buyer, seller, order fulfillment organization, with the total order being totaled, portions of the order being segregated and separated one from the other, and subtotaled, each segregated and subtotaled portion being directed to individual suppliers.
[0324] FIGS. 128A–128C depict a typical e-mail order placement EPn, resulting from submission of the typical completed order placement form OLn of FIGS. 126A–126B . FIGS. 129A–129C depict a typical e-mail confirmation of receipt of order ECn, resulting from submission of the typical completed order placement form OLn of FIGS. 126A–126B . FIGS. 130A–130B depict a typical e-mail order placement EPn of a portion of the order, resulting from submission of the typical completed order placement form OLn of FIGS. 126A–126B , and FIGS. 131A–131B and 132A–132B depict a typical e-mail order placements EPn of other portions of the order, resulting from submission of the typical completed order placement form OLn of FIGS. 126A–126B .
[0325] FIG. 136 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn thereinto, which is substantially the same as the typical service and/or information entry request form IEn at the user interface In of FIG. 111 , except the typical service and/or information entry request form IEn at the user interface In of FIG. 136 is adapted to allow 10 different ones of the typical queries QQn1 . . . QQnm (53) and 10 different ones of the typical server addresses AQn1 . . . AQnm (54) to be entered, whereas the typical service and/or information entry request form IEn at the user interface In of FIG. 111 is adapted to allow 9 different ones of the typical queries QQn1 . . . QQnm (53) and 9 different ones of the typical server addresses AQn1 . . . AQnm (54) to be entered.
[0326] FIG. 137 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn thereinto, which is substantially the same as the typical service and/or information entry request form IEn at the user interface In of FIG. 136 , except the typical service and/or information entry request form IEn at the user interface In of FIG. 137 is adapted to allow the 10 different ones of the typical queries QQn1 . . . QQnm (53) and the 10 different ones of the typical server addresses AQn1 . . . AQnm (54) to be entered, aligned vertically one with the other in pairs, in two rows predominantly horizontally adjacent one with the other, whereas the typical service and/or information entry request form IEn at the user interface In of FIG. 136 is adapted to allow the 10 different ones of the typical queries QQn1 . . . QQnm (53) and the 10 different ones of the typical server addresses AQn1 . . . AQnm (54) to be entered, aligned horizontally one with the other in pairs adjacent one with the other in vertical rows.
[0327] FIG. 138 depicts another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn thereinto, which is substantially the same as the typical service and/or information entry request form IEn at the user interface In of FIG. 137 , except the typical service and/or information entry request form IEn at the user interface In of FIG. 138 is adapted to allow 12 different ones of the typical queries QQn1 . . . QQnm (53) and 12 different ones of the typical server addresses AQn1 . . . AQnm (54) to be entered, whereas the typical service and/or information entry request form IEn at the user interface In of FIG. 138 is adapted to allow 10 different ones of the typical queries QQn1 . . . QQnm (53) and 10 different ones of the typical server addresses AQn1 . . . AQnm (54) to be entered.
[0328] FIGS. 139–141 depict yet another typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn thereinto, which are substantially the same as the typical service and/or information entry request forms IEn at the user interface In of FIGS. 6 , 8, and 10.
[0329] Each of the typical service and/or information entry request form IEn at the user interface In, which the user Un may communicate other typical user input UIn thereinto, of FIGS. 136–141 also have “Top Stories”, which are news stories, and are updated intermittently on a substantially routine basis.
[0330] FIG. 142 shows another typical completed service and/or information entry request form IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1 . . . QQnm (53), different ones of the typical server addresses AQn1 . . . AQnm (54), and the typical optional instructions VJn1 . . . VJnk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Separate $[a–z]”. The typical optional instructions VJn1 . . . VJnk (52) of FIG. 142 have “Separate $[a–z]”, which instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) in separate groups, sorted in ascending order first numerically, and then alphabetically, in the appropriate addressable query information groups GIn1 . . . GInz (63), i.e., grouped by the typical server addresses AQn1 . . . AQnm (54), and communicated in the other typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, as shown in FIGS. 143A–143H . Items having prices will be sorted numerically by price, with lowest price first within each of the typical server addresses AQn1 . . . AQnm (54) groups.
[0331] FIG. 144 shows another typical completed service and/or information entry request form IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1 . . . QQnm (53), different ones of the typical server addresses AQn1 . . . AQnm (54), and the typical optional instructions VJn1 . . . VJnk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Combined $[a–z]”.
[0332] The typical optional instructions VJn1 . . . VJnk (52) “Combined $[a–z]” of FIG. 144 instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having information and/or services in the responses Rn1 . . . Rnm (32) to be sorted in ascending order first numerically, and then alphabetically, in the appropriate addressable query information groups GIn1 . . . GInz (63). Items having prices will be sorted numerically by price, with lowest price first. The labelled individual information groups LLn11 . . . LLnzu (86) in the addressable query information groups GIn1 . . . GInz (63) are grouped and sorted in ascending order one with the other and labelled and/or identified and associated correspondingly with the responses Rn1 . . . Rnm (32) from the servers S1 . . . Sz (20). The “Combined $[a–z]” information and/or services may typically be incorporated into the appropriate addressable query information groups GIn1 . . . GInz (63) in accordance with the “Combined $[a–z]” optional instructions VJn1 . . . VJnk (52), and communicated in the other typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, as shown in FIGS. 145A–145G .
[0333] FIG. 146 shows yet another typical completed service and/or information entry request form IFn (230), at the user interface In (14), having same and different ones of the typical queries QQn1 . . . QQnm (53), different ones of the typical server addresses AQn1 . . . AQnm (54), and the typical optional instructions VJn1 . . . VJnk (52), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Combined $[a–z]”.
[0334] The typical optional instructions VJn1 . . . VJnk (52) “Combined $[a–z]” of FIG. 146 instruct the client Cn (16) and/or the server PS (18) to return the typical user response URn (37), as the typical service and/or information response form ISn (39) at the user interface In (14) having information and/or services in the responses Rn1 . . . Rnm (32) to be sorted in ascending order first numerically, and then alphabetically, in the appropriate addressable query information groups GIn1 . . . GInz (63). Items having prices will be sorted numerically by price, with lowest price first. The labelled individual information groups LLn11 . . . LLnm (86) in the addressable query information groups GIn1 . . . GInz (63) are grouped and sorted in ascending order one with the other and labelled and/or identified and associated correspondingly with the responses Rn1 . . . Rnm (32) from the servers S1 . . . Sz (20). The “Combined $[a–z]” information and/or services may typically be incorporated into the appropriate addressable query information groups GIn1 . . . GInz (63) in accordance with the “Combined $[a–z]” optional instructions VJn1 . . . VJnk (52), and communicated in the other typical user response URn, as the typical service and/or information response form ISn at the user interface In, which may be communicated to the user Un, as shown in FIGS. 147A–147G .
[0335] Each of the typical service and/or information entry request forms IEn at the user interface In, which the user Un may communicate other typical user input UIn into, of FIGS. 1–147 may also have news stories, which may be updated intermittently on a substantially routine basis.
[0336] The typical ones of the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14) shown in certain ones of the FIGS. 1–147 are typical examples of the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14), a much larger variety of which is possible. Typical queries QQn1 . . . QQnm (53), typical server addresses AQn1 . . . AQnm (54), and typical optional instructions VJn1 . . . VJnk (52) in the typical ones of the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14) shown in certain ones of the FIGS. 1–147 are typical examples for illustrative purposes, and are not intended to limit the substantially infinite variety of the queries QQn1 . . . QQnm (53), the server addresses AQn1 . . . AQnm (54), and the optional instructions VJn1 . . . VJnk (52) that may be entered into the service and/or information entry request forms IE1 . . . IEn (38), to derive the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14). Likewise, names and/or links and/or other information incorporated in the typical ones of the completed service and/or information entry request forms IF1 . . . IFn (230) shown in certain ones of the FIGS. 1–147 are for illustrative purposes, and are not intended to limit the large variety of the completed service and/or information entry request forms IF1 . . . IFn (230) and the names and/or links and/or information that are possible, and that may be incorporated into the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14).
[0337] Any ones of the typical queries QQn1 . . . QQnm (53), any values within the ranges allowable for the typical server addresses AQn1 . . . AQnm (54), and any values allowable for the typical optional instructions VJn1 . . . VJnk (52) may be incorporated into the typical ones of service and/or information entry request forms IE1 . . . IEn (38) at the user interfaces I1 . . . In (14) shown in certain ones of the FIGS. 1–147 , which the users U1 . . . Un (12) enter to complete the typical ones of the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14) of shown in certain ones of the FIGS. 1–147 .
[0338] 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 into the typical ones of service and/or information entry request forms IE1 . . . IEn (38) at the user interfaces I1 . . . In (14) shown in certain ones of the FIGS. 1–147 , which the users U1 . . . Un (12) enter to complete the typical ones of the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14) shown in certain ones of the FIGS. 1–147 .
[0339] The users U1 . . . Un (12), for example, may enter: the typical queries QQn1 . . . QQnm (53); any values within the ranges allowable for the typical server addresses AQn1 . . . AQnm (54); and any values allowable for the typical optional instructions VJn1 . . . VJnk (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” into the typical ones of service and/or information entry request forms IE1 . . . IEn (38) at the user interfaces I1 . . . In (14 shown in certain ones of the FIGS. 1–147 , which the users U1 . . . Un (12) enter to complete the typical ones of the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14). The typical ones of the user responses UR1 . . . URn (37), as typical service and/or information response forms IS1 . . . ISn (39) at the user interfaces I1 . . . In (14), may then be communicated to the corresponding ones of the users U1 . . . Un (12), accordingly. Certain ones of the FIGS. 1–147 show typical ones of the user responses UR1 . . . URn (37), as the typical service and/or information response forms IS1 . . . ISn (39) at the user interfaces I1 . . . In (14), which may be communicated to the corresponding ones of the users U1 . . . Un (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.
F. OPTIONAL DATABASE
[0340] The server PS (18) and/or the clients C1 . . . Cn (16) may also incorporate corresponding additional optional responses RA11 . . . RAnm (40) into the service and/or information responses IR1 . . . IRn (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 C1 . . . Cn (16), respectively.
[0341] The server PS (188) and/or the clients C1 . . . Cn (16) may optionally store the responses R11 . . . Rnm (32) communicated from the servers S1 . . . Sz (20), in accordance with the designation scheme corresponding to the server designations S11 . . . Snm (30) in the optional databases 41 and/or 42, optionally resident within the server PS (18) and/or the clients C1 . . . Cn (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 IR1 . . . IRn (34), and accessed as the additional optional responses RA11 . . . RAnm (40).
[0342] The server PS (18) and/or the clients C1 . . . Cn (16) may optionally communicate with the optional servers SO1 . . . SOp (22), and obtain information from each of the optional servers SO1 . . . SOp (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 C1 . . . Cn (16), respectively, and which may be optionally incorporated into the service and/or information responses IR1 . . . IRn (34), and accessed as the additional optional responses RA11 . . . RAnm (40).
[0343] Each of the users U1 . . . Un (12) may optionally communicate corresponding additional optional requests q11 . . . qnp (44) through the corresponding user interfaces I1 . . . In (14) and the corresponding clients C1 . . . Cn (16) to the optional servers SO1 . . . SOp (22), based upon information in the service and/or information responses IR1 . . . IRn (34) and/or other information presented to and/or available and/or known to the users U1 . . . Un (12) through the corresponding user interfaces I1 . . . In (14). The optional servers SO1 . . . SOp (22) reply to the clients C1 . . . Cn (16) with corresponding responses r11 . . . rnp (46), which the clients C1 . . . Cn (16) communicate through the corresponding user interfaces I1 . . . In (14) to the corresponding user U1 . . . Un (12), as shown in FIG. 2 for typical ones of the requests q11 . . . qnp (44) and the corresponding responses r11 . . . rnp (46).
G. ADDITIONAL DETAILS
[0344] Now, in more detail, the clients C1 . . . Cn (16) and the servers S1 . . . Sz (20) reside on the network 24. The users U1 . . . Un (12) and the corresponding clients C1 . . . Cn (16) communicate one with the other through the corresponding user interfaces I1 . . . In (14). The user U1 (12), thus, communicates with the client C1 (16), one with the other, through the user interface I1 (14); the user U2 (12), thus, communicates with the client C2 (16), one with the other, through the user interface I2 (14); the user Un (12), thus, communicates with the client Cn (16), one with the other, through the user interface In (14); and so on. Any particular user, designated user Un (12), thus, communicates with corresponding client Cn (16), one with the other, through corresponding user interface In (14), as best shown later in FIGS. 54–56 . The user Un (12) may be used to designate any one of the users U1 . . . Un (12); the user interface In (14) may be used to designate any one of the user interfaces I1 . . . In (14); the client Cn (16) may be used to designate any one of the users clients C1 . . . Cn (16); and so on. The client-server multitasking system 10 may also have the server PS (18) and the optional servers SO1 . . . SOp (22) residing on the network 24.
[0345] There may be n different or same the service and/or information requests IQ1 . . . IQn (28) present on the network 24 at any time. Each of the service and/or information requests IQ1 . . . IQn (28) may have one or more of the same and/or different requests Q11 . . . Qnm (29) to be made of one or more of the same and/or different ones of the servers S1 . . . Sz (20), which are called server designations S11 . . . Snm (30), in accordance with the designation scheme which designates the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30). The service and/or information request IQn (28) may be used to designate any particular one of the service and/or information requests IQ1 . . . IQn (28). Requests Qn1 . . . Qnm (29) may be used to designate the particular requests Q11 . . . Qnm (29) associated with and corresponding to the service and/or information request IQn (28).
[0346] Each of the requests Q11 . . . Q1m from the client C1 (16) may each be different one from the other or the same; each of the requests Q21 . . . Q2m from the client C2 (16) may each be different one from the other or the same; and each of the requests Qn1 . . . Qnm (29) from the client Cn (16) may each be different one from the other or the same, and so on. The requests Q11 . . . Q1m (29), the requests Q21 . . . Q2m (29), and the requests Qn1 . . . Qnm (29), thus, may each be different one from the other, or the same, and so on. The requests Q11 . . . Qnm (29) from the clients C1 . . . Cn (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 S1 . . . Sz (20) at the same time and/or different times, in accordance with the corresponding server designations S11 . . . Snm (30). There may be m different or same ones of the requests Qn1 . . . Qnm (29) from the client Cn (16) at any time, and n×m different and/or same ones of the requests Q11 . . . Qnm (29) of the same and/or different ones of the servers S1 . . . Sz (20) present on the network 24 at any time.
[0347] This designation format, in which the first alphanumeric subscript after the parameter of interest, for example, as in the parameters Qn1 . . . Qnm representing the requests Qn1 . . . Qnm (29), represents the particular parameters corresponding to the user Un (12), and the second alphanumeric subscript after the parameter of interest represents the 1st, 2nd, 3rd, through the mth one of the particular parameters, which 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 Qn1 . . . Qnm (29) associated with the nth user Un, which is designated as the user Un (12). There are then the same and/or different m distinctly the same and/or different server designations Sn1 . . . Snm (30) associated with the nth user Un, which is designated as the user Un (12). The same and/or different requests Qn1 . . . Qnm (29), then, may be made of the same and/or different ones of the servers S1 . . . Sz (20), in accordance with the designation scheme corresponding to the corresponding certain ones of the server designations Sn1 . . . Snm (30), associated with and corresponding to the user Un (12).
[0348] Each of the clients C1 . . . Cn (16) may optionally also function as servers. Certain ones of the clients C1 . . . Cn (16) may, therefore, function only as clients, while alternate ones of the clients C1 . . . Cn (16) may function as clients and as servers. Each of the user interfaces I1 . . . In (14) may be integral with the clients C1 . . . Cn (16) or separate from the clients C1 . . . Cn (16). Therefore, certain ones of the user interfaces I1 . . . In (14) may be integral with the clients C1 . . . Cn (16), while yet other ones of the user interfaces I1 . . . In (14) may be separate from the clients C1 . . . Cn (16).
[0349] 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 C1 . . . Cn (16) are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information from the same and/or different ones of the servers S1 . . . Sz (20), and/or the optional servers SO1 . . . SOp (22), and/or the clients C1 . . . Cn (16), having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information into the user responses UR1 . . . URn (37) for delivery to the user interfaces I1 . . . In (14) and use by the users U1 . . . Un (12).
[0350] Now, the user interfaces I1 . . . In (14) may each be different, one from the other, or the same, and may change characteristics over time. Each of the user interfaces I1 . . . In (14) may change characteristics as a function of time, information, and/or instructions, and/or other means, which may be derived by the users U1 . . . Un (12) and/or the clients C1 . . . Cn (16) and/or the servers S1 . . . Sz (20), and/or the server PS (18), and/or the optional servers SO1 . . . SOp (22), and/or derived within the user interfaces I1 . . . In (14). The user interface I1 . . . In (14) may change state.
[0351] The user interface I1 . . . In (14) may also change as a function of optional timers and/or timed instructions associated with the user interfaces I1 . . . In (14), and/or associated with the clients C1 . . . Cn (16) and/or associated with the servers S1 . . . Sz (20), and/or associated with the server PS (18), and/or associated with the optional servers SO1 . . . SOp (22), and/or instructions from the user U1 . . . Un (12). Changes in the user interface In (14) may appear continuous to the user Un (12), spaced in time, staccato, or static depending upon the optional timers and/or the timed instructions. Other conditions may change the user interface I1 . . . In (14), as well.
[0352] The user interfaces I1 . . . In (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.
[0353] The user interfaces I1 . . . In (14) may be visual, such as graphical user interfaces, aural, and/or tactile, a combination thereof, and/or other suitable means. The user interfaces I1 . . . In (14) may be integral with the clients C1 . . . Cn (16) or separate.
II. A PARTICULAR USER, USER INTERFACE, AND CLIENT ON THE NETWORK
A. Overview
[0354] FIGS. 54–56 show typical particular ones of the users Un (12), the corresponding ones of the user interfaces Un (12), the corresponding ones of the clients Cn (16), the server PS (18), the servers S1 . . . Sz (20) designated by the server designations Sn1 . . . Smm (30) corresponding to the requests Qn1 . . . Qnm (29) associated with the corresponding ones of the users Un (12), and the optional servers SO1 . . . SOp (22) of the client-server multitasking system 10 of the present invention, which reside on the network 24. The user Un (12) communicates with the corresponding client Cn (16) through the corresponding user interface In (14).
[0355] The user Un (12) enters the corresponding user input UIn (25) having one or more same and/or different user requests qun1 . . . qunu (26) into the user interface In (14). The user requests qun1 . . . qunm (26) are communicated from the user interface In (14) to the client Cn (16) within the user service and/or information request iqn (27), having the user requests qun1 . . . qunu (26) and other optional information.
[0356] The user interface In (14) communicates the user service and/or information request iqn (27) to the client Cn (16), which optionally formats the corresponding user service and/or information request iqn (27) into the corresponding service and/or information request IQn (28), as required. The service and/or information request IQn (28) may have one or more the same and/or different requests Qn1 . . . Qnm (29) to be made of the servers S1 . . . Sz (20) designated by the server designations Sn1 . . . Snm (30) at the same time.
[0357] The client Cn (16) may communicate the corresponding service and/or information request IQn (28) to the server PS (18). The server PS (18) parses, processes and/or formats the service and/or information request IQn (28) received from the client Cn (16) into the certain requests Qn1 . . . Qnm (29), and communicates the certain requests Qn1 . . . Qnm (29) to the corresponding certain ones of the servers S1 . . . Sz (20) designated by the server designations Sn1 . . . Snm (30), as shown for typical ones of the certain requests Qn1 . . . Qnm (29) in FIG. 54 .
[0358] The client Cn (16) may alternatively parse, process and/or format the user service and/or information request iqn (27) into the alternate requests Qn1 . . . Qnm (29), and communicate the alternate requests Qn1 . . . Qnm (29) to the corresponding alternate ones of the servers S1 . . . Sz (20) designated by the server designations Sn1 . . . Snm (30), as shown for typical alternate ones of the requests Qn1 . . . Qnm (29) in FIG. 55 .
[0359] The client Cn (16) may alternatively communicate the corresponding other alternate one of the service and/or information request IQn (28) to the server PS (18), which parses, processes and/or formats the other alternate one of the service and/or information request IQn (28) into the other alternate ones of the requests Qn1 . . . Qnm (29), and communicates the other alternate ones of the requests Qn1 . . . Qnm (29) to the corresponding other alternate ones of the servers S11 . . . Snm (30), and additionally the client Cn (16) may also parse, process and/or format the user service and/or information request iqn (27) into yet other alternate ones of the requests Qn1 . . . Qnm (29), and communicate the yet other alternate ones of the requests Qn1 . . . Qnm (29) to the corresponding yet other alternate ones of the servers Sn1 . . . Snm (30), as shown for typical other alternate ones of the requests Qn1 . . . Qnm (29) and typical yet other alternate ones of the requests Qn1 . . . Qnm (29) in FIG. 56 .
[0360] Each of the servers S1 . . . Sz (20) designated by the server designations Sn1 . . . Snm (30) replies to the server PS (18) and/or the client Cn (16), in accordance with the designation scheme corresponding to the corresponding certain ones of the server designations S11 . . . Snm (30), accordingly, and communicates the corresponding responses Rn1 . . . Rnm (32), associated with the requests Qn1 . . . Qnm (29), to the server PS (18) and/or the client Cn (16), accordingly. The server PS (18) and/or the client Cn (16) parse, format, process, group, and organize the responses Rn1 . . . Rnm (32) into the corresponding service and/or information response IRn (34) and/or the user service and/or information response irn (36) having the corresponding parsed, processed, formatted, grouped, and organized service and/or information group Gn (35) acceptable to the client Cn (16) and the user interface In (14). The server PS (18) communicates the service and/or information response IRn (34) to the client Cn (16), as required.
[0361] The client Cn (16) formats the service and/or information responses IR1 . . . IRn (34) into the corresponding user service and/or information response irn (36), as required, and communicates the user service and/or information responses irn (36) to the user interfaces In (14). The user interface In (14) incorporates the user service and/or information response irn (36) into the user response URn (37), which is communicated by the user interfaces In (14) to the user Un (12).
[0362] The server PS (18) and/or the client Cn (16) may optionally also incorporate the optional additional corresponding responses RAn1 . . . RAnm (40) (shown later in FIGS. 59 , 60, 63, and 64) into the service and/or information response IRn (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 Cn (16), respectively.
[0363] The server PS (18) and/or the client Cn (16) communicate the service and/or information response IRn (34) through the user interface In (14) to the user Un (12).
[0364] The server PS (18) and/or the clients Cn (16) may optionally store the responses Rn1 . . . Rnm (32) communicated from the servers S1 . . . Sz (20) designated by the server designations Sn1 . . . Snm (30) in the optional databases 41 and/or 42, optionally resident within the server PS (18) and/or the client Cn (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 IRn (34), and accessed as the additional optional responses RAn1 . . . RAnm (40).
[0365] The server PS (18) and/or the client Cn (16) may optionally communicate with the optional servers SO1 . . . SOp (22), and obtain information from each of the optional servers SO1 . . . SOp (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 Cn (16), respectively, and which may be optionally incorporated into the service and/or information response IRn (34), and accessed as the additional optional responses RAn1 . . . RAnm (40).
[0366] The user Un (12) may optionally communicate the corresponding additional optional requests qn1 . . . qnp (44) through the user interface In (14) and the client Cn (16) to the optional servers SO1 . . . SOp (22), based upon information in the service and/or information response IRn (34) and/or other information presented to and/or available and/or known to the user Un (12) through the user interface In (14). The optional servers SO1 . . . SOp (22) reply to the client Cn (16) with the corresponding responses rn1 . . . rnp (46), which the client Cn (16) communicates through the user interface In (14) to the user Un (12), as shown in FIGS. 54–56 for typical ones of the requests qn1 . . . qnp (44) and the corresponding responses rn1 . . . rnp (46).
B. DIAGRAMMATIC REGROUPING
[0367] Now, in more detail, FIG. 57 shows a schematic representation of ones of the users U1 . . . Un (12), the corresponding user interfaces I1 . . . In (14), the corresponding clients C1. . . Cn (16), the server PS (18), the servers S1 . . . Sz (20), and the optional servers SO1 . . . SOp (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.
[0368] Now, as shown in FIG. 57 , for illustrative purposes only, ones of the clients C1 . . . Cn (16) communicating with the server PS (18), as in FIG. 54 , may optionally be designated clients CA1 . . . CAw (16A), and so on. Ones of the clients C1 . . . Cn (16) communicating with the servers S1 . . . Sz (20), as in FIG. 55 , may optionally be designated clients CB1 . . . CBx (16B), and so on. Ones of the clients C1 . . . Cn (16) communicating with the server PS (18) and with the servers S1 . . . Sz (20), as in FIG. 56 , may optionally be designated clients CC1 . . . CCy (16C), and so on.
[0369] The users U1 . . . Un (12) and the corresponding user interfaces I1 . . . In (14) corresponding to the clients C1 . . . Cn (16) may, likewise, optionally be designated in FIG. 57 only: correspondingly to the clients CA1 . . . CAw (16A), as users UA1 . . . UAw (12A) and user interfaces IA1 . . . IAw (14A), respectively; correspondingly to the clients CB1 . . . CBx (16B), as users UB1 . . . UBx (12B) and user interfaces IB1 . . . IBx (14B), respectively; and correspondingly to the clients CC1 . . . CCy (16C), as users UC1 . . . UCy (12C) and IC1 . . . ICy (14C), respectively.
[0370] The clients C1 . . . Cn (16) being accounted for, the total of the clients CA1 . . . CAw (16A), CB1 . . . CBx (16B), and CC1 . . . CCy (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.
w+x+y=n.
III. A PARTICULAR SERVICE AND/OR INFORMATION REQUEST AND ASSOCIATED SERVICE AND/OR INFORMATION RESPONSE ON THE NETWORK
B. The Server PS (18)
[0371] FIG. 58 shows a typical particular one of the service and/or information requests IQ1 . . . IQn (28), designated as the service and/or information request IQn (28), having queries QQn1 . . . QQnm (53), corresponding server addresses AQn1 . . . AQnm (54), and optional instructions VJn1 . . . VJnk (52). The server addresses AQn1 . . . AQnm (54) and the optional instructions VJn1 . . . VJnk (52) may be optional, and may depend upon the user interface In (14), and/or other information resident within the server PS (18).
[0372] FIG. 59 shows the particular service and/or information request IQn (28) parsed, processed, and/or formatted into current request group QAnc (50), request groups QAn1 . . . QAnz (51), and optional instructions VJn1 . . . VJnk (52), and utilization of information therefrom to make the requests Qn1 . . . Qnm (29), obtain the responses Rn1 . . . Rnm (32), and incorporate information therefrom into the particular service and/or information response IRn (34). The current request group QAnc (50) may be any particular one the request groups QAn1 . . . QAnz (51), which may be selected by the user Un (12).
[0373] Upon receipt of the service and/or information requests IQ1 . . . IQn (28) at the server PS (18), communicated from the corresponding clients C1 . . . Cn (16), the server PS (18) parses, processes, and/or formats each of the service and/or information requests IQ1 . . . IQn (28) into the corresponding current request groups QA1c . . . QAnc (50) having corresponding queries QQ11 . . . QQnm (53) and corresponding server addresses AQ11 . . . AQnm (54) to open connections with and make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), shown for a particular one of the service and/or information requests IQn (28) in FIG. 59 .
[0374] The server PS (18) also parses, processes, and/or formats each of the service and/or information requests IQ1 . . . IQn (28) into the corresponding request groups QA11 . . . QAnz (51) having corresponding other queries QQ1a . . . QQnz (55) and corresponding other server addresses AQ1a . . . AQnz (56), and the corresponding optional instructions VJ111 . . . VJnk (52), also shown for a particular one of the service and/or information requests IQn (28) in FIG. 59 .
[0375] The server PS (18) opens connections with and makes the requests Qn1 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), shown for the particular one of the service and/or information requests IQn (28) corresponding to the corresponding queries QQn1 . . . QQnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) in the current request group QAnc (50).
[0376] The servers S1 . . . Sz (20) corresponding to the server designations S11 . . . Snm (30), designated in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), respond to the requests Qn1 . . . Qnm (29) with the corresponding responses Rn1 . . . Rnm (32).
[0377] The server PS (18) parses, and/or processes, and/or formats, and/or groups, and/or organizes each of the responses Rn1 . . . Rnm (32) received from the servers S1 . . . Sz (20) corresponding to the server designations Sn1 . . . Snm (30) into corresponding addressable response information groups RGn1 . . . RGnm (57).
[0378] The server PS (18) may also make additional optional requests QPn1 . . . QPnm (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 RAn1 . . . RAnm (40). The server PS (18) parses, and/or processes, and/or formats, and/or groups, and/or organizes each of the additional optional responses RAn1 . . . RAnm (40) into corresponding response information groups RCn1 . . . RCnm (59).
[0379] Information from the current request group QAnc (50) having the corresponding queries QQn1 . . . QQnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) is formulated into a corresponding request pointer/address group QZn (60) having pointers/addresses PGn1 . . . PGnz (61) associated therewith.
[0380] Each of the pointers/addresses PGn1 . . . PGnz (61) are directed to point/address corresponding addressable query pointer/address groups QGn1 . . . QGnz (62) associated therewith, which aid in obtaining information and/or services from certain ones of addressable response information groups RGn1 . . . RGnm (57) to be incorporated into addressable query information groups GIn1 . . . GInz (63).
[0381] Grouping and/or sorting criteria may be incorporated into the optional instructions VJn1 . . . VJnk (52), which may be entered into the user interface In (14) through the user input UIn (25) by the user Un (12). Grouping and/or sorting criteria may additionally and/or alternatively be optionally resident within the server PS (18) and/or the client Cn (16).
[0382] The grouping and/or sorting criteria gives the user Un (12) the ability to formulate the query information groups GIn1 . . . GInz (63) and the way in which the information and/or services from the addressable response information groups RGn1 . . . RGnm (57) is presented to the user Un (12) through the user interface In (14).
[0383] Each of the addressable query pointer/address groups QGn1 . . . QGnz (62) are associated with the corresponding ones of the addressable query information groups GIn1 . . . GInz (63). The addressable query pointer/address group QGn1 (62) is, thus, associated with the addressable query information group GIn1 (63); the addressable query pointer/address group QGn2 (62) is, thus, associated with the addressable query information group GIn2 (63); the addressable query pointer/address group QGnz (62) is, thus, associated with the addressable query information group GInz (63), and so on.
[0384] Each of the addressable query pointer/address groups QGn1 . . . QGnz (62) is formulated based upon the grouping and/or sorting criteria, which may be incorporated into the optional instructions VJn1 . . . VJnk (52), and/or which may additionally and/or alternatively optionally be resident within the server PS (18) and/or the client Cn (16), and/or information within the current request group QAnc (50).
[0385] Each of the addressable query pointer/address groups QGn1 . . . QGnz (62) has pointers/addresses PPn11 . . . PPnmr (64) directed to address/point information in the addressable response information groups RGn1 . . . RGnm (57) based upon the grouping and/or sorting criteria, which may be incorporated into the optional instructions VJn1 . . . VJnk (52), and/or which may additionally and/or alternatively optionally be resident within the server PS (18) and/or the client Cn (16), and/or the corresponding queries QQn1 . . . QQnm (53), and/or the corresponding server addresses AQn1 . . . AQnm (54) within the current request group QAnc (50).
[0386] Information and/or services within each of the addressable response information groups RGn1 . . . RGnm (57) is addressed with the pointers/addresses PPn11 . . . PPnmr (64) from the query pointer/address groups QGn1 . . . QGnz (62), and the information and/or services from the addressable response information groups RGn1 . . . RGnm (57) is incorporated into the addressable query information groups GIn1 . . . GInz (63) corresponding to the pointers/addresses PPn11 . . . PPnmr (64), which are formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62), in accordance with the grouping and/or sorting criteria.
[0387] The corresponding other queries QQnm . . . QQnz (55) and the corresponding other server addresses AQnm . . . AQnz (56) in the corresponding request groups QAn1 . . . QAnz (51) may be used for other ones of the requests Qn1 . . . Qnm (29), and may be incorporated into the service and/or information response IRn (34), as part of other information OIn (65), for further use.
[0388] Each of the addressable query information groups GIn1 . . . GInz (63) is incorporated into the service and/or information group Gn (35). The service and/or information group Gn (35) and the other information OIn (65) are incorporated into the service and/or information response IRn (34).
[0389] The optional instructions VJn1 . . . VJnk (52) may be used by the server PS (18) in making the requests Qn1 . . . Qnm (29) and/or the additional optional requests QPn1 . . . QPnm (58) of the optional database 41, and/or in processing, formatting, grouping, and organizing the responses Rn1 . . . Rnm (32) from the ones of the servers S1 . . . Sz (20) corresponding to the server designations Sn1 . . . Snm (30), and/or the additional optional responses RAn1 . . . RAnm (40), into the corresponding service and/or information responses IR1 . . . IRn (34), for grouping and/or sorting criteria instructions, and/or may be used for other purposes.
[0390] FIG. 60 is a schematic representation of the particular service and/or information request IQn (28) parsed, processed, and/or formatted into a current request group QAn (50), request groups QAn1 . . . QAnz (51), and corresponding optional instructions VJn1 . . . VJnk (52), and utilization of information therefrom to make the requests Qn1 . . . Qnm (29), obtain the responses Rn1 . . . Rnm (32), and incorporate information therefrom into the particular service and/or information response IRn (34), having simpler grouping/sorting that may be used additionally and/or alternatively to that of FIG. 59 .
[0391] The user Un (12) is typically given the option through the optional instructions VJn1 . . . VJnk (52) as to the grouping and/or sorting criteria to be entered into the user interface In (14) through the user input UIn (25) by the user Un (12). The user Un (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 .
[0392] Information from the current request group QAnc (50) having the corresponding queries QQn1 . . . QQnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) is formulated into a corresponding request pointer/address group QYn (68) having pointers/addresses PFn11 . . . PFnmr (69) associated therewith, as shown in FIG. 60 .
[0393] Each of the pointers/addresses PFn11 . . . PFnmr (69) are directed to point/address the corresponding addressable response information groups RGn1 . . . RGnm (57), and aid in obtaining information and/or services from the corresponding addressable response information groups RGn1 . . . RGnm (57) to be incorporated into the addressable query information groups GIn1 . . . GInz (63), as shown in FIG. 60 .
[0394] The grouping and/or sorting criteria allow the user Un (12) to direct the server PS (18) and/or the client Cn (16) to sort information and/or services from the responses Rn1 . . . Rnm (32) and/or the additional optional responses RAn1 . . . RAnm (40) from 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 from the responses Rn1 . . . Rnm (32) and/or the additional optional responses RAn1 . . . RAnm (40) one with the other, such as, for example, by order of relevance and/or other parameters.
[0395] FIG. 61 shows the particular service, and/or information response IRn (34) having a service and/or information group Gn (35), additional request links SLn1 . . . SLnw (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 IEn (38).
[0396] The service and/or information group Gn (35) has the query information groups GIn1 . . . GInz (63), optional database response groups 75, and optional additional advertisements and/or links 76.
[0397] The additional request links SLn1 . . . SLnw (71) allow the user Un (12) to make additional optional selections, based upon information and/or services previously requested by the user Un (12). The additional request links SLn1 . . . SLnw (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 SLn1 . . . SLnw (71) and/or combinations thereof may also be incorporated into the service and/or information response IRn (34).
[0398] the optional order form 72 allows direct placement and/or confirmation of orders and/or purchases with the servers S=hd 1 . . . Sz (20) and/or the optional servers SO1 . . . SOp (22), which reside on the network 24. The user Un (12) may enter the order placement into the user interface In (14) through the user input UIn (25), and receive order confirmation through the user interface In (14). The client Cn (16) may communicate the order placement from the user interface In (14) to the server PS (18), which may communicate the order placement to the servers S1 . . . Sz (20) and/or the optional servers SO1 . . . SOp (22). The server PS (18) may alternatively and/or additionally communicate the order confirmation received from the servers S1 . . . Sz (20) and/or the optional servers SO1 . . . SOp (22) to the client Cn (16), which may communicate the order confirmation to the user interface In (14) for presentation to the user Un (12). The order placement and/or the order confirmation may be stored within the server PS (18) and/or the client Cn (16). The order placement and/or the order confirmation is typically secure, and may be encrypted, and is typically communicated using secure communications means.
C. CERTAIN ONES OF THE CLIENTS
[0399] Certain ones of the clients C1 . . . Cn (16) may alternatively and/or additionally make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29), and formulate the corresponding user service and/or information response ir1 . . . irn (36), as previously described.
[0400] FIG. 62 shows a typical particular one of the user service and/or information requests iq1 . . . iqn (27), designated as the user service and/or information request iqn (27), having the queries QQn1 . . . Qnm (53), the corresponding server addresses AQn1 . . . AQnm (54), and the optional instructions VJn1 . . . VJnk (52). The server addresses AQn1 . . . AQnm (54) and the optional instructions VJn1 . . . VJnk (52) may be optional, and may depend upon the user interface In (14), and/or other information resident within the client Cn (16).
[0401] FIG. 63 shows the particular user service and/or information request iqn (27) parsed, processed, and/or formatted into the current request group QAnc (50), the request groups QAn1 . . . QAnz (51), and the corresponding optional instructions VJn1 . . . VJnk (52), and utilization of information therefrom to make the requests Qn1 . . . Qnm (29), obtain the responses Rn1 . . . Rnm (32), and incorporate information therefrom into the particular user service and/or information response irn (36);
[0402] The server PS (18) makes the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), as shown in FIG. 59 , and certain ones of the clients C1 . . . Cn (16) may additionally and/or alternatively make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), as shown in FIG. 63 .
[0403] The clients Cn (16) may parse, process, and/or format the user service and/or information requests iqn (27) and/or organize and/or group information and/or services from the addressable response information groups RGn1 . . . RGnm (57) into the addressable query information groups GIn1 . . . GInz (63) substantially the same as the server PS (18) parses, processes, and/or formats the service and/or information requests IQn (28) from the addressable response information groups RGn1 . . . RGnm (57) into the addressable query information groups GIn1 . . . GInz (63), except that the client Cn (16) may organize the addressable query information groups GIn1 . . . GInz (63) into the user service and/or information response irn (36), as in FIG. 63 , and the server PS (18) organizes the addressable query information groups GIn1 . . . GInz (63) into the corresponding service and/or information response IRn (34), as in FIG. 59 .
[0404] Upon receipt of the user service and/or information requests iq1 . . . iqn (27) at the corresponding clients C1 . . . Cn (16), certain ones of the corresponding clients C1 . . . Cn (16) may parse, process, and/or format the corresponding user service and/or information requests iq1 . . . iqn (27) into the corresponding current request groups QA1c . . . QAnc (50) having the corresponding queries QQ11 . . . QQnm (53) and the corresponding server addresses AQ11 . . . AQnm (54) to open connections with and make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), shown for a particular one of the user service and/or information requests iq1 . . . iqn (27) in FIG. 63 .
[0405] The corresponding clients C1 . . . Cn (16) may also parse, process, and/or format the corresponding user service and/or information response ir1 . . . irn (36) into the corresponding request groups QA11 . . . QAnz (51) having the corresponding other queries QQ1a . . . QQnz (56) and the corresponding optional instructions VJ111 . . . VJnk (52), also shown for a particular one of the user service and/or information request iqn (27) in FIG. 63 .
[0406] A particular one of the corresponding clients C1 . . . Cn (16), designated as the client Cn (16), may open connections with and make the requests Qn1 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), shown for the particular one of the user service and/or information requests iqn (27) corresponding to the corresponding queries QQn1 . . . QQnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) in the current request group QAnc (50).
[0407] The servers S1 . . . Sz (20) corresponding to the server designations S11 . . . Snm (30), designated in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), respond to the requests Qn1 . . . Qnm (29) with the corresponding responses Rn1 . . . Rnm (32).
[0408] The client Cn (16) may parse, and/or process, and/or format, and/or group, and/or organize each of the responses Rn1 . . . Rnm (32) received from the servers S1 . . . Sz (20) corresponding to the server designations Sn1 . . . Snm (30) into the corresponding addressable response information groups RGn1 . . . RGnm (57).
[0409] The client Cn (16) may also make additional optional requests QPn1 . . . QPnm (58) of the optional database 42, which may be optionally resident within the client Cn (16), and which may reply with the corresponding additional optional responses RAn1 . . . RAnm (40). The client Cn (16) may parse, and/or process, and/or format, and/or group, and/or organize each of the additional optional responses RAn1 . . . RAnm (40) into the corresponding response information groups RCn1 . . . RCnm (59).
[0410] Now again, for the client Cn (16), information from the current request group QAnc (50) having the corresponding queries QQn1 . . . QQnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) is formulated into the corresponding request pointer/address group QZn (60) having the pointers/addresses PGn1 . . . PGnz (61) associated therewith.
[0411] Now again, for the client Cn (16), each of the pointers/addresses PGn1 . . . PGnz (61) are directed to point/address the corresponding addressable query pointer/address groups QGn1 . . . QGnz (62) associated therewith, which aid in obtaining information and/or services from certain ones of the addressable response information groups RGn1 . . . RGnm (57) to be incorporated into the addressable query information groups GIn1 . . . GInz (63).
[0412] Yet again, for the client Cn (16), grouping and/or sorting criteria may be incorporated into the optional instructions VJn1 . . . VJnk (52), which may be entered into the user interface In (14) through the user input UIn (25) by the user Un (12). Grouping and/or sorting criteria may additionally and/or alternatively optionally resident within the server PS (18) and/or the client Cn (16).
[0413] Now again, the grouping and/or sorting criteria gives the user Un (12) the ability to formulate the query information groups GIn1 . . . GInz (63) and the way in which information from the addressable response information groups RGn1 . . . RGnm (57) is presented to the user Un (12) through the user interface In (14).
[0414] Now again, for the client Cn (16), each of the addressable query pointer/address groups QGn1 . . . QGnz (62) are associated with the corresponding ones of the addressable query information groups GIn1 . . . GInz (63). Each of the addressable query pointer/address groups QGn1 . . . QGnz (62) is formulated base upon the grouping and/or sorting criteria, which may be incorporated into the optional instructions VJn1 . . . VJnk (52), and/or which may additionally and/or alternatively optionally be resident within the server PS (18) and/or the client Cn (16), and/or information within the current request group QAnc (50).
[0415] Now again, for the client Cn (16), each of the addressable query pointer/address groups QGn1 . . . QGnz (62) has pointers/addresses PPn11 . . . PPnmr (64) directed to address/point services and/or information in the addressable response information groups RGn1 . . . RGnm (57) based upon the grouping and/or sorting criteria, which may be incorporated into the optional instructions VJn1. . . VJnk (52), and/or which may additionally and/or alternatively optionally be resident within the server PS (18) and/or the client Cn (16) and/or the corresponding queries QQn1 . . . QQnm (53), and/or the corresponding server addresses AQn1 . . . AQnm (54) within the current resident group QAnc (50).
[0416] Yet again, for the client Cn (16), the information and/or services in each of the addressable response information groups RGn1 . . . RGnm (57) is addressed with the pointers/addresses PPn11 . . . PPnmr (64) from the query pointer/address groups QGn1 . . . QGnz (62), and information and/or services from the addressable response information groups RGn1 . . . RGnm (57) is incorporated into the addressable query information groups GIn1 . . . GInz (63) corresponding to the pointer/addresses PPn11 . . . PPnmr (64), which are formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62), in accordance with the grouping and/or sorting criteria.
[0417] Yet again, for the client Cn (16), the corresponding other queries QQna . . . QQnz (55) and the corresponding other server addresses AQna . . . AQnz (56) in the corresponding request groups QAn1 . . . QAnz (51) may be used for other ones of the requests Qn1 . . . Qnm (29), and may be incorporated into the user service and/or information response irn (36), as part of other information OIn (65), for future use.
[0418] Now again, for the client Cn (16), each of the addressable query information groups GIn1 . . . GInz (63) is incorporated into the service and/or information group Gn (35). The service and/or information group Gn (35) and the other information OIn (65) are incorporated into the service and/or information response IRn (34).
[0419] The optional instructions VJn1 . . . VJnk (52) may be used by the client Cn (16), in making the requests Qn1 . . . Qnm (29) and/or the additional optional requests QPn1 . . . QPnm (58) of the optional database 42, and/or in processing, formatting, grouping, and organizing the responses Rn1 . . . Rnm (32) from the ones of the servers S1 . . . Sz (20) corresponding to the server designations Sn1 . . . Snm (30), and/or the additional optional responses RAn1 . . . RAnm (40), into user service and/or information response irn (36), for grouping and/or sorting criteria instructions, and/or may be used for other purposes.
[0420] FIG. 64 is a schematic representation of the particular user service and/or information request iqn (27) parsed, processed, and/or formatted into the current request group QAnc (50), the request groups QAn1 . . . QAnz (51), and the corresponding optional instructions VJn1 . . . VJnk (52), and utilization of information therefrom to make the requests Qn1 . . . Qnm (29), obtain the responses Rn1 . . . Rnm (32), and incorporate information therefrom into the particular user service and/or information response irn (36), having simpler grouping/sorting that may be used additionally and/or alternatively to that of FIG. 63 .
[0421] The user Un (12) is typically given the option through the optional instructions VJn1 . . . VJnk (52) as to the grouping and/or sorting criteria to be entered into the user interface In (14) through the user input UIn (25) by the user Un (12). The user Un (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 .
[0422] Now again, the client Cn (16) may parse, process, and/or format the user service and/or information requests iqn (27) and/or organize and/or group information and/or services from the addressable response information groups RGn1 . . . RGnm (57) into the addressable query information groups GIn1 . . . GInz (63) substantially the same as the server PS (18) parses, processes, and/or formats the service and/or information requests IQn (28) from the addressable response information groups RGn1 . . . RGnm (57) into the addressable query information groups GIn1 . . . GInz (63), except that the client Cn (16) may organize the addressable query information groups GIn1 . . . GInz (63) into the user service and/or information response irn (36), as in FIG. 64 , and the server PS (18) organizes the addressable query information groups GIn1 . . . GInz (63) into the corresponding service and/or information response IRn (34), as in FIG. 60 .
[0423] Now again, for the client Cn (16), information from the current request group QAnc (50) having the corresponding queries QQn1 . . . QQnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) is formulated into the corresponding request pointer/address group QYn (68) having the pointers/addresses PFn11 . . . PFnmr (69) associated therewith, as shown in FIG. 64 .
[0424] Now again, for the client Cn (16), each of the pointers/addresses PFn11 . . . PFnmr (69) are directed to point/address the corresponding addressable response information groups RGn1 . . . RGnm (57), and aid in obtaining information and/or services from the corresponding addressable response information groups RGn1 . . . RGnm (57) to be incorporated into the addressable query information groups GIn1 . . . GInz (63), as shown in FIG. 64 .
[0425] Again, the grouping and/or sorting criteria allow the user Un (12) to direct the server PS (18) and/or the client Cn (16) to sort information and/or services from the responses Rn1 . . . Rnm (32) and/or the additional optional responses RAn1 . . . RAnm (40) from 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 from the responses Rn1 . . . Rnm (32) and/or the additional optional responses RAn1 . . . RAnm (40) one with the other, such as, for example, by order of relevance and/or other parameters.
[0426] FIG. 65 shows the particular user service and/or information response irn (36) having the service and/or information group Gn (35), the additional request links SLn1 . . . SLnw (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 IEn (38).
[0427] Now again, the service and/or information group Gn (35) has the query information groups GIn1 . . . GInz (63), the optional database response groups 75, and the optional additional advertisements and/or links 76.
[0428] Yet again, the additional request links SLn1 . . . SLnw (71) allow the user Un (12) to make additional optional selections, based upon information and/or services previously requested by the user Un (12). The additional request links SLn1 . . . SLnw (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 SLn1 . . . SLnw (71) and/or combination thereof may also be incorporated into the user service and/or information response irn (36).
[0429] Now again, for the client Cn (16), the optional order form 72 allows direct placement and/or confirmation of order and/or purchases with the servers S1 . . . Sz (20) and/or the optional servers SO1 . . . SOp (22), which reside on the network 24. The user Un (12) may enter the order placement into the user interface In (14) through the user input UIn (25), and receive order confirmation through the user interface In (14). The client Cn (16) may communicate the order placement from the user interface In (14) to the servers S1 . . . Sz (20) and/or the optional servers SO1 . . . SOp (22), and/or receive the order confirmation therefrom, and communicate the order confirmation from the servers S1 . . . Sz (20) and/or the optional servers SO1 . . . SOp (22) to the user interface In (14) for presentation to the user Un (12). The order placement and/or the order confirmation may be stored within the server PS (18) and/or the client Cn (16). The order placement and/or the order confirmation is typically secure, and may be encrypted, and is typically communicated using secure communication means.
D. FORMULATING QUERY INFORMATION GROUPS
[0430] Each of the particular addressable response information groups RGn1 . . . RGnm (57), designated as the addressable response information group RGnm (57), has optional addressable individual information groups LGnm1 . . . LGnmr (80), which may be addressed with the pointers/addresses PPnm1 . . . PPnmr (64), as shown in FIGS. 59 , 63, 66A, 66B, and 66C.
[0431] Each of the addressable response information groups RGn1 . . . RGnm (57) and each of the optional addressable individual information groups LGn11 . . . LGnmr (80) in each of the addressable response information groups RGn1. . .RGnm (57) may be addressed with the pointers/addresses PPn11 . . . PPnmr (64).
[0432] Now again, the addressable response information group RGnm (57) has the optional addressable individual information groups LGnm1 . . . LGnmr (80), which may be addressed with the pointers/addresses PPnm1 . . . PPnmr (64). Each of the addressable individual information groups LGnm1 . . . LGnmr (80) in the addressable response information group RGnm (57) may be pointed/addressed by the server PS (18) and/or the client Cn (16) to retrieve all and/or a portion and/or combinations of specific ones of the addressable individual information groups LGnm1 . . . LGnmr (80), from the addressable response information group RGnm (57), and incorporate information and/or services from the addressable individual information groups LGnm1 . . . LGnmr (80) into certain ones of the addressable query information groups GIn1 . . . GInz (63), in accordance with the grouping and/or sorting criteria addressing scheme.
[0433] The addressable response information group RGnm (57) having the optional addressable individual information groups LGnm1 . . . LGnmr (80) may have optional addressable pointer/address indices INnm1 . . . INnmr (81) correspondingly associated with the optional addressable individual information groups LGnm1 . . . LGnmr (80), which may be addressed/pointed with the pointers/addresses PPnm1 . . . PPnmr (64), and which may be pointed/addressed by the server PS (18) and/or the client Cn (16) to retrieve all and/or a portion and/or combinations of specific ones of the addressable individual information groups LGnm1 . . . LGnmr (80), and incorporate information and/or services from the addressable individual information groups LGnm1 . . . LGnmr (80) into the certain ones of the addressable query information groups GIn1 . . . GInz (63), in accordance with the grouping and/or sorting criteria addressing scheme.
[0434] FIGS. 66A , 66B, and 66C show the addressable response information group RGnm (57) having the addressable individual information groups LGnm1 . . . LGnmr (80) showing the optional addressable pointer/address indices INnm1 . . . INnmr (81) correspondingly associated with the optional addressable individual information groups LGnm1 . . . LGnmr (80), which may be addressed/pointed with the pointer/addresses PPnm1 (64), PPnm2 (64), and PPnmr (64), respectively.
[0435] The optional addressable pointer/address index INnm1 (81) correspondingly associated with the optional addressable individual information group LGnm1 (80). The optional addressable pointer/address index INnm2 (81) is correspondingly associated with the optional addressable individual information group LGnm2 (80), and so on. The optional addressable pointer/address index INnmr (81), is, thus, correspondingly associated with the optional addressable individual information group LGnm1 (80).
[0436] The pointers/addresses PGn1 . . . PGnz (61) may be formulated as arrays and/or lists. The pointers/addresses PPnm1 . . . PPnmr (64) and/or the pointers/addresses PFnm1 . . . PFnmr (69) may be formulated as arrays and/or lists. The arrays may be multidimensional arrays, and the lists may be lists within lists.
[0437] The optional addressable individual information group LGnmr (80) is associated with and corresponds to a particular one of the addressable individual information groups LGnm1 . . . LGnmr (80) in a particular one of the addressable response information groups RGn1 . . . RGnm (57), designated as the addressable response information group RGnm (57). The first subscript of the optional addressable individual information groups LGnmr (80) is associated with and corresponds to the particular service and/or information request IQn (28) and/or the user service and/or information request iqn (27). The second subscript of the optional addressable individual information groups LGnmr (80) is associated with and corresponds to a particular one of “1” through “m” i.e., 1 . . . m, of the addressable response information group RGn1 . . . RGnm (57). The third subscript of the optional addressable individual information groups LGnmr (80) is associated with and corresponds to a particular one of “1” through “r” i.e., 1 . . . r, of the optional addressable individual information group LGnm1 . . . LGnmr (80) within the addressable response information group RGnm (57).
[0438] The subscripts of the optional addressable pointer/address indices INnm1 . . . INnmr (81), are correspondingly associated with the subscripts of the corresponding addressable individual information groups LGnm1 . . . LGnmr (80).
[0439] 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.
[0440] For example, the pointers/addresses PGn1 . . . PGnz (61) of the request pointer/address group QZn (60) may be pointed/addressed to certain ones of the addressable query pointer/address groups QGn1 . . . QGnz (62), in accordance with certain grouping and/or sorting criteria schemes and/or pointing/addressing schemes. The pointers/addresses PPn11 . . . PPnmr (64) of each of the pointed/addressed addressable query pointer/address groups QGn1 . . . QGnz (62) may be pointed to the pointer/address indices INn11 . . . INnmr (81) of the optional addressable individual information groups LGnm1 . . . LGnmr, i.e., 1 . . . r, and the pointers/addresses PPn11 . . . PPnmr (64), i.e., 1 . . . m, corresponding to the addressable response information groups RGn1 . . . RGnm (57) formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62) may be pointed to certain ones of the addressable response information groups RGn1 . . . RGnm (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 LGnm1 . . . LGnmr from the addressable response information groups RGn1 . . . RGnm (57) is incorporated into the certain ones of the addressable query information groups GIn1 . . . GInz (63), in accordance with the grouping and/or sorting criteria addressing scheme, as formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62) and the request pointer/address group QZn (60).
[0441] Alternatively and/or additionally, the pointers/addresses PGn1 . . . PGnz (61) of the request pointer/address group QZn (60) may be incremented through each of the addressable query pointer/address groups QGn1 . . . QGnz (62). The pointers/addresses PPn11 . . . PPnmr (64) of each of the pointed/addressed addressable query pointer/address groups QGn1 . . . QGnz (62) may be pointed to the pointer/address indices INn11 . . . INnmr (81) of the optional addressable individual information groups LGnm1 . . . LGnmr, i.e., 1 . . . r, and incremented once, and then the pointers/addresses PPn11 . . . PPnmr (64), i.e., 1 . . . m, corresponding to the addressable response information groups RGn1 . . . RGnm (57) formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62) may be incremented through each of the addressable response information groups RGn1 . . . RGnm (57). This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LGnm1 . . . LGnmr from the addressable response information groups RGn1 . . . RGnm (57) is incorporated into the certain ones of the addressable query information groups GIn1 . . . GInz (63), in accordance with the grouping and/or sorting criteria addressing scheme, and as formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62).
[0442] Alternatively and/or additionally, the pointers/addresses PPn11 . . . PPnmr (64), i.e., 1 . . . m, may be incremented, corresponding to the addressable response information groups RGn1 . . . RGnm (57) formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62), and then the pointers/addresses PPn11 . . . PPnmr (64), i.e., 1 . . . r, pointing to the pointer/address indices INn11 . . . INnmr (81) of the optional addressable individual information groups LGnm1 . . . LGnmr may then be incremented. This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LGnm1 . . . LGnmr from the addressable response information groups RGn1 . . . RGnm (57) is incorporated into the certain ones of the addressable query information groups GIn1 . . . GInz (63), in accordance with the grouping and/or sorting criteria addressing scheme, and as formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62).
[0443] Alternatively and/or additionally, the pointers/addresses PFnm1 . . . PFnmr (69), i.e., 1 . . . m, may be incremented, corresponding to the addressable response information groups RGn1 . . . RGnm (57) formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62), and then the pointers/addresses PFnm1 . . . PFnmr (69), i.e., 1 . . . r, pointing to the pointer/address indices INn11 . . . INnmr (81) of the optional addressable individual information groups LGnm1 . . . LGnmr may then be incremented. This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LGnm1 . . . LGnmr from the addressable response information groups RGn1 . . . RGnm (57) is incorporated into the certain ones of the addressable query information groups GIn1 . . . GInz (63), in accordance with the grouping and/or sorting criteria addressing scheme, and as formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62).
[0444] The typical sorting and/or grouping criteria and the addressing/pointing schemes mentioned immediately above, for example, may group certain ones of the queries QQn1 . . . QQnm (53) having the same and/or substantially the same values into a particular one of the query information groups GInz . . . GInz (63), designated as the query information group GInz (63), as shown in certain ones of FIGS. 27A–52C , inclusive.
[0445] 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.
[0446] The addressable individual information groups LGnm1 . . . LGnmr (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 LGnm1 . . . LGnmr (80) are incorporated into the addressable response information groups RGn1 . . . RGnm (57) from the responses Rn1 . . . Rnm (32).
[0447] Alternatively and/or additionally the addressable individual information groups LGnm1 . . . LGnmr (80) may be incorporated into the addressable response information groups RGn1 . . . RGnm (57) from the responses Rn1 . . . Rnm (32) in an as-is condition and/or in raw form.
[0448] The optional addressable individual information groups LGnm1 . . . LGnmr (80) in the addressable response information group RGnm (57) having information and/or services parsed and/or processed, and/or formatted, and/or grouped from the response Rnm (32), may be correspondingly associated with the locations of the information and/or services in the response Rnm (32).
[0449] Each of the addressable individual information groups LGnm1 . . . LGnmr (80) may have and/or be parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into corresponding optional links LDnm1 . . . LDnmr (82), and/or corresponding optical descriptions DDnm1 . . . DDnmr (83), and/or corresponding optional prices/values PDnm1 . . . PDnmr (84), and/or corresponding optical images IDnm1 . . . IDnmr (85), as shown in FIG. 67 .
[0450] The optional links LDnm1 . . . LDnmr (82), the corresponding optional descriptions DDnm1 . . . DDnmr (83), the corresponding optional prices/values PDnm1 . . . PDnmr (84), and the corresponding optional images IDnm1 . . . IDnmr (85), corresponding to the addressable individual information groups LGnm1 . . . LGnmr (80) are typically associated correspondingly one with the other.
[0451] The optional link LDnm1 (82), the corresponding optional description DDnm1 (83), the corresponding optional price/value PDnm1 (84), and the corresponding optional image IDnm1 (85), corresponding to the optional individual information group LGnm1 (80) are typically associated correspondingly one with the other. The optional link LDnm2 (82), the corresponding optional description DDnm2 (83), the corresponding optional price/value PDnm2 (84), and the corresponding optional image IDnm2 (85), corresponding to the addressable individual information group LGnm2 (80) are typically associated correspondingly one with the other, and so on. The optional link LDnmr (82), the corresponding optional description DDnmr (83), the corresponding optional price/value PDnmr (84), and the corresponding optional image IDnmr (85), corresponding to the addressable individual information group LGnmr (80) are, thus, typically associated correspondingly one with the other.
[0452] The addressable individual information groups LGnm1 . . . LGnmr (80), which may have the corresponding optional links LDnm1 . . . LDnmr (82), and/or the corresponding optional descriptions DDnm1 . . . DDnmr (83), and/or the corresponding optional prices/values PDnm1 . . . PDnmr (84), and/or the corresponding optional images IDnm1 . . . IDnmr (85) are appended with labels/identifiers, as shown in FIG. 68 , and incorporated into certain ones of the addressable query information groups GIn1 . . . GInz (63), depending upon the grouping and/or sorting criteria. FIG. 69 shows a particular one of the addressable query information groups GIn1 . . . GInz (63), designated as the query information group GInz (63).
[0453] Now again, the optional addressable individual information group LGnmr (80) is associated with and corresponds to a particular one of the addressable individual information groups LGnm1 . . . LGnmr (80) in a particular one of the addressable response information groups RGn1 . . . RGnm (57), designated as the addressable response information group RGnm (57). The first subscript of the optional addressable individual information groups LGnmr (80) is associated with and corresponds to the particular service and/or information request IQn (28) and/or the user service and/or information request iqn (27). The second subscript of the optional addressable individual information groups LGnmr (80) is associated with and corresponds to a particular one of “1” through “m” i.e., 1 . . . m, of the addressable response information group RGn1 . . . RGnm (57). The third subscript of the optional addressable individual information groups LGnmr (80) is associated with and corresponds to a particular one of “1” through “r”, i.e., 1 . . . r, of the optional addressable individual information group LGnm1 . . . LGnmr (80) within the addressable response information group RGnm (57).
[0454] FIG. 68 shows a labelled individual information group LLnzu (86) associated with a particular one of the addressable query information groups GIn1 . . . GInz (63), designated as the addressable query information group GInz (63), having optional group identifier GLnc (87), optional query link identifier LNncu (88), optional resource location identifier SUnw (89), optional server and/or query identifier SInm (90), and/or optional server link identifier LXnmr (91) appended to the addressable individual information group LGnmr (80).
[0455] The first alphanumeric subscript of the labelled individual information group LLnzu (86) is associated with and corresponds to the service and/or information response IRn (34) and/or the user service and/or information response irn (36). The second alphanumeric subscript of the labelled individual information group LLnzu (86) is associated with and corresponds to a particular one of “1” through “z”, i.e., 1 . . . z, of the addressable query information groups GIn1 . . . GInz (63), designated as the addressable query information group GInz (63), which the labelled individual information group LLnzu (86) is incorporated in. The third alphanumeric subscript of the labelled individual information group LLnzu (86) is associated with and corresponds to a particular one of “1” through “u”, i.e. , 1 . . . u, of labelled individual information groups LLnz1 . . . LLnzu (86) within the addressable query information group GInz (63).
[0456] The optional group identifier GLnc (87) labels and/or identifies the current request group QAnc (50). The optional group identifier GLnc (87) is associated with and corresponds to the current request group QAnc (50), which may be any particular one of the request groups QAn1 . . . QAnz (51) selected by the user Un (12). The first alphanumeric subscript of the optional group identifier GLnc (87) is associated with and corresponds to the service and/or information response IRn (34) and/or the user service and/or information response irn (36). The second subscript of the optional group identifier GLnc (87) is associated with and corresponds to the particular one of the request groups QAn1 . . . QAnz (51) selected by the user Un (12) as the current request group QAnc (50).
[0457] The optional query link identifier LNncu (88) is also associated with and corresponds to the current request group AQnc (50). The optional query link identifier LNncu (88) labels and/or identifies the labelled individual information group LLnm (86). The first alphanumeric subscript of the optional query link identifier LNncu (88) is associated with and corresponds to the service and/or information response IRn (34) and/or the user service and/or information response irn (36). The second subscript of the optional query link identifier LNncu (88) is also associated with and corresponds to the particular one of the request groups QAn1 . . . QAnz (51) selected by the user Un (12) as the current request group QAnc (50). The third alphanumeric subscript of the optional query link identifier LNncu (88) is associated with and corresponds to a particular one of “1” through “u”, i.e., 1 . . . u, of the labelled individual information groups LLnz1 . . . LLnzu (86) in the addressable query information group GInz (63).
[0458] The optional resource location identifier SUnw (89) labels and/or identifies resource locations of information and/or services associated with and corresponding to the optional addressable individual information group LGnmr (80) in the labelled individual information group LLnzu (86). The optional resource location identifier SUnw (89) indicates and is associated with and corresponds to resource locations of information and/or services associated with certain ones of the optional servers SO1 . . . SOp (22) and/or certain ones of the servers S1 . . . Sz (20). The optional resource location identifier SUnw (89) may be obtained from certain information in the optional addressable individual information group LGnmr (80). The first alphanumeric subscript of the optional resource location identifier SUnw (89) is associated with and corresponds to the service and/or information response IRn (34) and/or the user service and/or information response irn (36). The second alphanumeric subscript of the optional resource location identifier SUnw (89) is associated with and corresponds to a particular one of “1” through “w”, i.e., 1 . . . w, of the optional resource location identifiers SUn1 . . . SUnw (89) in the labelled individual information group LLnzu (86).
[0459] The optional server and/or query identifier SInm (90) labels and/or identifies the query QQnm (53) and/or the corresponding server address AQnm (54) associated with and corresponding to the optional addressable individual information group LGnmr (80) in the corresponding labelled individual information group LLnzu (86) of the current request group QAnc (50). The first alphanumeric subscript of the optional server and/or query identifier SInm (90) is associated with and corresponds to the service and/or information response IRn (34) and/or the user service and/or information response irn (36). The second alphanumeric subscript of the optional server and/or query identifier SInm (90) is associated with and corresponds to a particular one of “1” through “m”, i.e., 1 . . . m, of the optional server and/or query identifiers SIn1 . . . SInm (90), which may be correspondingly associated with the corresponding ones of the queries QQn1 . . . QQnm (53) and/or the corresponding ones of the server addresses AQn1 . . . AQnm (54).
[0460] The optional server link identifier LXnmr (91) labels and/or identifies the location of the optional addressable individual information group LGnmr (80) in the corresponding addressable response information groups RGnm (57). The first alphanumeric subscript of the optional server link identifier LXnmr (91) is associated with and corresponds to the service and/or information response IRn (34) and/or the user service and/or information response irn (36). The second alphanumeric subscript of the optional server link identifier LXnmr (91) is associated with and corresponds to the addressable response information group RGnm (57). The third alphanumeric subscript of the optional server link identifier LXnmr (91) is associated with and corresponds to a particular one of “1” through “r”, i.e., 1 . . . r, of the optional server link identifiers LXnm1 . . . LXnmr (91), which may be correspondingly associated with the locations of certain ones of the optional addressable individual information group LGnm1 . . . LGnmr (80) in the addressable response information groups RGnm (57). The certain ones of the optional addressable individual information groups LGnm1 . . . LGnmr (80) in the addressable response information group RGnm (57), having information and/or services parsed and/or processed, and/or formatted, and/or grouped from the response Rnm (32), which are labelled and/or identified with the optional server link identifiers LXnm1 . . . LXnmr (91), are correspondingly associated with the locations of the information and/or services in the response Rnm (32). The optional server link identifiers LXnm1 . . . LXnmr (91), thus, identify and/or label the location of services and/or information in the response Rnm (32).
[0461] FIG. 69 shows the addressable query information group GInz (63) having the labelled individual information groups LLnz1 . . . LLnzu (86), optional database labelled individual information groups RLnz1 . . . RLnzx (92), optional query description QTnz (93), optional server descriptions and/or links STnz1 . . . STnzf (94), and optional advertisements and/or links LTnz1 . . . LTnzt (95). The first and second subscripts of the optional database labelled individual information groups RLnz1 . . . RLnzx (92), the optional query description QTnz (93), the optional server descriptions and/or links STnz1 . . . STnzf (94), and the optional advertisement and/or links LTnz1 . . . LTnzt (95) are associated with and correspond to the addressable query information group GInz (63). The third subscripts of the optional database labelled individual information groups RLnz1 . . . RLnzx (92), the optional server descriptions and/or links STnz1 . . . STnzf (94), and the optional advertisements and/or links LTnz1 . . . LTnzt (95) are associated with and correspond to ones of the optional database labelled individual information groups RLnz1 . . . RLnzx (92), the optional server descriptions and/or links STnz1 . . . STnzf (94), and the optional advertisements and/or links LTnz1 . . . LTnzt (95), respectively.
IV PROCESS
[0462] FIG. 70 shows steps of a client-server multitasking process 99 of the present invention. The client-server multitasking process 99 is shown for the client-server multitasking system 10 for a particular one of the users U . . . Un (12), designated as the user Un (12), the corresponding particular one of the user interfaces I . . . In (14), designated as the user interface In (14), the corresponding particular one of the clients C . . . Cn (16), designated as the client Cn (16), the server PS (18), the servers S1 . . . Sz (20), and the optional servers SO1 . . . SOp (22), which reside on the network 24.
[0463] The client-server multitasking process 99 starts at step 101. The user Un (12) enters the user input UIn (25) into the user interface In (14) (step 102). The user input UIn (25) is formulated into the user service and/or information request iqn (27) at the user interface In (14) and communicated to the client Cn (16) (step 103). The user service and/or information request iqn (27) may be formulated into the service and/or information request IQn (28) at the client Cn (16) and communicated to the server PS (18) (also step 103).
[0464] The service and/or information response IRn (34) and/or the user service and/or information response irn (36) are derived at the server PS (18) and/or the client Cn (16), respectively, at step 104, which in itself is a process, and may hereinafter be referred to as the multitasking process 104. The multitasking process 104 will be discussed in more detail later with reference to FIGS. 71 and 72 .
[0465] Now, continuing with FIG. 70 , the user service and/or information response irn (36) may be derived at the client Cn (16) (step 104) from the service and/or information response IRn (34), which may be communicated to the client Cn (16) from the server PS (18) (also step 104), and/or alternatively and/or additionally from the responses Rn1 . . . Rnm (32), which may be communicated to the client Cn 1 (16) (step 104).
[0466] Now, the client Cn (16) may communicate the service and/or information request IQn (28) to the server PS (18) (step 103). The service and/or information response IRn (34) is then derived at the server PS (18) (step 104) and communicated to the client Cn (16) (also step 104). The user service and/or information response irn (36) may be derived from the service and/or information response IRn (34) (also step 104).
[0467] Now, in more detail, if the service and/or information request IQn (28) is communicated to the server PS (18) (step 103), then the server PS (18) makes the requests Qn1 . . . Qnm (29) and/or certain ones of the requests Qn1 . . . Qnm (29) of the servers S1 . . . S2 (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations Sn1 . . . Snm (30), utilizing information from the service and/or information request IQn (28). The service and/or information response IRn (34) is then derived at the server PS (18) (step 104) from the responses Rn1 . . . Rnm (32) received from the servers S1 . . . Sz (20) corresponding to the server designations Sn1 . . . Snm (30), and communicated to the client Cn (16). Now, again, the user service and/or information response irn (36) may be derived from the service and/or information response IRn (34) (also step 104).
[0468] Now, also in more detail, alternatively and/or additionally, the client Cn (16) may make the requests Qn1 . . . Qnm (29) and/or certain other ones of the requests Qn1 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations Sn1 . . . Snm (30), utilizing information from the user service and/or information request iqn (27). Now, again, the user service and/or information response irn (36) may also be derived at the client Cn (16) (step 104) from the responses Rn1 . . . Rnm (32) communicated to the client Cn (16) (step 104) and/or alternatively and/or additionally from the service and/or information response IRn (34) communicated to the client Cn (16) from the server PS (18) (also step 104).
[0469] The user service and/or information response irn (36), thus, may be derived from the service and/or information response IRn (34) communicated from the server PS (18) to the client Cn (16) and/or alternatively and/or additionally from the responses Rn1 . . . Rnm (32) communicated to the client Cn (16) (step 104).
[0470] The user service and/or information response irn (36) is communicated to the user interface In (14) (step 105) and incorporated into the user response URn (37).
[0471] The user Un (12) reviews the user response URn (37) and/or selects additional services and/or information (step 106). Step 106 will be discussed in more detail later with reference to FIG. 76 . The process 99 ends at step 107. The process 99 will be described in more detail with reference to FIGS. 1–147 of the drawings.
[0472] The service and/or information response IRn (34) and/or the user service and/or information response irn (36) are derived at the server PS (18) and/or the client Cn (16), respectively, at step 104 in FIG. 70 , and shown in more detail in FIGS. 71 and 72 .
[0473] FIG. 71 shows the multitasking process 104 of deriving the service and/or information response IRn (34) and/or the user service and/or information response irn (36), with reference to FIGS. 59 and 63 . FIG. 72 shows the multitasking process 104 of deriving the service and/or information response IRn (34) and/or the user service and/or information response irn (36) having 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 . The multitasking process 104 will also be described in more detail with reference to FIGS. 1–147 of the drawings.
[0474] The server PS (18) and/or the client Cn (16) parse, process, and/or format the service and/or information request IQn (28) and/or the user service and/or information request iqn (27) into the current request group QAnc (50), the request groups QAn1. . .QAnc (51), and the optional instructions VJn1 . . . VJnk (52) (step 104-1), as shown in FIGS. 71 and 72 .
[0475] Information from the current group QAnc (50) and the optional instructions VJn1 . . . VJnk (52) may be used to make the requests Qn1 . . . Qnm (29), obtain the responses Rn1 . . . Rnm (32), and incorporate information therefrom into the service and/or information response IRn (34) and/or the user service and/or information response irn (36), as shown in FIGS. 71 and 72 with reference to FIGS. 59 , 60, 63, and 64. The current request group QAnc (50) may be any particular one the request groups QAn1 . . . QAnz (51), which may be selected by the user Un (12).
[0476] The current request group QAnc (50) has the corresponding queries QQn1 . . . QQnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) to open connections with and make the requests Qn1 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations Sn1 . . . Snm (30), shown for the particular service and/or information request IQn (28) and/or the particular user service and/or information request iqn (27).
[0477] The server PS (18) and/or the client Cn (16) open connections with and make the requests Qn1 . . . Qnm (29) having the corresponding queries QQn1 . . . Qnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) in the current request group QAnc (50) of the servers S1 . . . Sz (20) (step 104-2) as shown in FIGS. 71 and 72 , in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations Sn1 . . . Snm (30).
[0478] The servers S1 . . . Sz (20) corresponding to the server designations Sn1 . . . Snm (30), designated in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), respond to the requests Qn1 . . . Qnm (29) with the corresponding responses Rn1 . . . Rnm (32).
[0479] The server PS (18) and/or the client Cn (16) parse, and/or process, and/or format, and/or group, and/or organize each of the responses Rn1 . . . Rnm (32) received from the servers S1 . . . Sz (20) (step 104-3), as shown in FIGS. 71 and 72 with reference to FIGS. 105–107 , corresponding to the server designations Sn1 . . . Snm (30) into the corresponding addressable response information groups RGn1 . . . RGnm (57).
[0480] The server PS (18) and/or the client Cn (16) may also make additional optional requests QPn1 . . . QPnm (58) of the optional databases 41 and/or 42 (also step 104-2 of FIGS. 71 and 72 ), which may be optionally resident within the server PS (18) and/or the client Cn (16), and which may reply with the corresponding additional optional responses RAn1 . . . RAnm (40). The server PS (18) and/or the client Cn (16) parse, and/or process, and/or format, and/or group, and/or organize each of the additional optional responses RAn1 . . . RAnm (40) into the corresponding response information groups RCn1 . . . RCnm (59) (also step 104-3 of FIGS. 71 and 72 ).
[0481] Now, step 104-3 of FIGS. 71 and 72 is shown in more detail in FIG. 73 .
[0482] As discussed later, and shown in FIGS. 105–107 , entity body RHnm (353) of the response Rnm (32) has optional response individual information groups LSnm1 . . . LSnmr (360).
[0483] Each of the optional response individual information groups LSn11 . . . LSnmr (360) and/or portions thereof from the entity bodies RHn1 . . . RHnm (353) of the responses Rn1 . . . Rnm (32) may be optionally compared one with the other, and duplicate ones of the optional response individual information groups LSn11 . . . LSnmr (360) may be optionally discarded (step 104-3-1), as shown in FIG. 73 .
[0484] The remaining optional response individual information groups LSn11 . . . LSnmr (360) are parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into corresponding ones of the addressable individual information groups LGn11 . . . LGnmr (80) as the addressable individual information groups LGn11 . . . LGnmr (80) are incorporated into the addressable response information groups RGn1 . . . RGnm (57) from the responses Rn1 . . . Rnm (32) (step 104-3-2), as shown in FIG. 73 .
[0485] The addressable individual information groups LGn11 . . . LGnmr (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 LGn11 . . . LGnmr (80) are incorporated into the addressable response information groups RGn1 . . . RGnm (57) from the responses Rn1 . . . Rnm (32).
[0486] The server PS (18) and/or the client Cn (16) may formulate information from the current request group QAnc (50) having the corresponding queries QQn1 . . . QQnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) into the corresponding request pointer/address group QZn (60) having the pointers/addresses PGn1 . . . PGnz (61) associated therewith (step 104-4 of FIG. 71 with reference to FIGS. 59 , 63, and 97). Alternatively and/or additionally, the server PS (18) and/or the client Cn (16) may formulate information from the current request group QAnc (50) having the corresponding queries QQn1 . . . QQnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) into a corresponding request pointer/address group QYn (68) having the pointers/addresses PFn11 . . . PFnmr (69) associated therewith (step 104-4 of FIG. 72 with reference to FIGS. 60 and 64 ).
[0487] The server PS (18) and/or the client Cn (16) may formulate the addressable query pointer/address groups QGn1 . . . QGnz (62) (step 104-5 of FIG. 71 with reference to FIGS. 59 , 63, 97, 102, and typical ones of the addressable query pointer/address groups QGn1 . . . QGnz (62) in FIGS. 98 and 99 ), depending upon the grouping and/or sorting criteria used. Each of the pointers/addresses PGn1 . . . PGnz (61) may be directed to point/address the corresponding addressable query pointer/address groups QGn1 . . . QGnz (62) associated therewith, which aid in obtaining information and/or services from certain ones of addressable response information groups RGn1 . . . RGnm (57) to be incorporated into addressable query information groups GIn1 . . . GInz (63).
[0488] Each of the addressable query pointer/address groups QGn1 . . . QGnz (62) has the pointers/addresses PPn11 . . . PPnmr (64) directed to address/point information in the addressable response information groups RGn1 . . . RGnm (57) based upon the grouping and/or sorting criteria.
[0489] The grouping and/or sorting criteria may be incorporated into the optional instructions VJn1 . . . VJnk (52), which may be entered into the user interface In (14) through the user input UIn (25) by the user Un (12). Grouping and/or sorting criteria may additionally and/or alternatively optionally resident within the server PS (18) and/or the client Cn (16).
[0490] The grouping and/or sorting criteria gives the user Un (12) the ability to formulate the query information groups GIn1 . . . GInz (63) and the way in which information and/or services from the addressable response information groups RGn1 . . . RGnm (57) is presented to the user Un (12) through the user interface In (14).
[0491] Information and/or services within each of the addressable response information groups RGn1 . . . RGnm (57) is addressed with the pointers/addresses PPn11 . . . PPnmr (64) from the query pointer/address groups QGn1 . . . QGnz (62), and information and/or services from the addressable response information groups RGn1 . . . RGnm (57) is incorporated into the addressable query information groups GIn1 . . . GInz (63) corresponding to the pointers/addresses PPn11 . . . PPnmr (64) (step 104-6 of FIG. 71 ), which are formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62), in accordance with the grouping and/or sorting criteria, as shown in FIG. 71 with reference to FIGS. 59 , 63, 66A, 66B, 66C, 67–69, 97, 102, typical ones of the addressable query pointer/address groups QGn1 . . . QGnz (62) in FIGS. 98 and 99 , and a typical one of the addressable query information groups GIn1 . . . GInz (63), designated as the addressable query information group GInz (63), in FIG. 109 .
[0492] Alternatively and/or additionally, each of the pointers/addresses PFn11 . . . PFnmr (69) may directed to point/address the corresponding addressable response information groups RGn1 . . . RGnm (57), and aid in obtaining information and/or services from the corresponding addressable response information groups RGn1 . . . RGnm (57) to be incorporated into the addressable query information groups GIn1 . . . GInz (63) (step 104-6) as shown in FIG. 72 with reference to FIGS. 60 , 64, 66A, 66B, 66C, 67–69, and another typical one of the addressable query information groups GIn1 . . . GInz (63), designated as the addressable query information group GInz (63), in FIG. 110 .
[0493] Now, step 104-6 of FIG. 71 is shown in more detail in FIG. 74 with reference to FIGS. 59 , 63, 66A, 66B, 66C, 67–69, 97, 102, typical ones of the addressable query pointer/address groups QGn1 . . . QGnz (62) in FIGS. 98 and 99 , and a typical one of the addressable query information groups GIn1 . . . GInz (63), designated as the addressable query information group GInz (63), in FIG. 109 . Step 104-6 of FIG. 72 is shown in more detail in FIG. 75 with reference to FIGS. 60 , 64, 66A, 66B, 66C, 67–69, and another typical one of the addressable query information groups GIn1 . . . GInz (63), designated as the addressable query information group GInz (63), in FIG. 110 .
[0494] The optional addressable individual information groups LGn11 . . . LGnmr (80) in each of the addressable response information groups RGn1 . . . RGnm (57) may be addressed with the pointers/addresses PPn11 . . . PPnmr (64) (step 104-6-1) as shown in FIG. 74 with reference to FIGS. 59 and 63 and FIG. 71 .
[0495] The optional addressable individual information groups LGn11 . . . LGnmr (80) in each of the addressable response information groups RGn1 . . . RGnm (57) may be addressed with the pointers/addresses PPn11 . . . PPnmr (64) (step 104-6-1) as shown in FIG. 74 with reference to FIGS. 59 and 63 and FIG. 71 .
[0496] The optional addressable individual information groups LGn11 . . . LGnmr (80) in each of the addressable response information groups RGn1 . . . RGnm (57) may alternatively and/or additionally be addressed with the pointers/addresses PFn11 . . . PFnmr (69) (step 104-6-1) as shown in FIG. 75 with reference to FIGS. 60 and 64 and FIG. 72 .
[0497] The addressed optional addressable individual information groups LGn11 . . . LGnmr (80) in each of the addressable response information groups RGn1 . . . RGnm (57) may alternatively and/or additionally be addressed with the pointers/addresses PFn11 . . . PFnmr (69) (step 104-6-1) as shown in FIG. 75 with reference to FIGS. 60 and 64 and FIG. 72 .
[0498] The addressed optional addressable individual information groups LGn11 . . . LGnmr (80) and/or portions thereof may be optionally labelled with labels and/or identifiers and incorporated into the labelled individual information groups LLnz1 . . . LLnzu (86) (step 104-6-2), as shown in FIGS. 74 and 75 .
[0499] The labelled individual information groups LLnz1 . . . LLnzu (86) may be incorporated into certain ones of the addressable query information groups GIn1 . . . GInz (63), depending upon the grouping and/or sorting criteria (step 104-6-3), as shown in FIGS. 74 and 75 .
[0500] The addressed optional addressable individual information groups LGn11 . . . LGnmr (80) and/or portions thereof are typically appended with the labels and/or identifiers, thus creating the labelled individual information groups LLnz1 . . . LLnzu (86), as each of the labelled individual information groups LLnz1 . . . LLnzu (86) are incorporated into the certain ones of the addressable query information groups GIn1 . . . GInz (63). The steps 104-6-2 and 104-6-3 are thus typically consolidated into a single step.
[0501] The addressable query information groups GIn1 . . . GInz (63) may then be incorporated into the service and/or information response IRn (34) (step 104-7), as shown in FIGS. 71 and 72 with reference to FIG. 61 , and/or the user service and/or information response irn (36) (also step 104-7), as also shown in FIGS. 71 and 72 but with reference to FIG. 65 .
[0502] The user Un (12) reviews the user response URn (37) the user interface In (14) and/or selects additional services and/or information at step 106 in FIG. 70 , and shown in more detail in FIG. 76 . The step 106 will also be described in more detail with reference to FIGS. 1–147 of the drawings.
[0503] The user Un (12) selects additional services and/or information through the user interface In (14) (step 106-1) or exits to the end of the process 99 at step 107. If the user Un (12) selects additional services and/or information through the user interface In (14) (step 106-1), the user Un (12) may optionally enter one or more orders into an order form and/or order forms at and through the user interface In (14) (step 106-2). The order and/or orders may be, for example, for purchases, and/or instructions, and/or payment, and/or other information and/or services to be directed to and/or requested of third parties, and/or combinations thereof, of the optional servers SO1 . . . SOp (22), and/or the servers S1 . . . Sz (20), and/or other ones of the clients C1 . . . Cn (16) through the server PS (18) and/or the client Cn (16). The order and/or orders may, thus, be placed through and by the server PS (18) and/or the client Cn (16), eliminating the need for the user Un (12) to place separate ones of the order with the third parties, the optional servers SO1 . . . SOp (22), and/or the servers S1 . . . Sz (20) separately and/or individually.
[0504] The server PS (18) and/or the client Cn (16) process the orders and/or communicate the orders to the third parties, the optional servers SO1 . . . SOp (22), and/or the servers S1 . . . Sz (20), and/or other ones of the clients C1 . . . Cn (16) (step 106-3). The server PS (18) and/or the client Cn (16) confirm the order (step 106-4). The user Un (12) may select additional services and/or information through the user interface In (14) (step 106-1) or exit to the end of the process 99 at step 107.
[0505] If the user Un (12) selects additional services and/or information through the user interface In (14) (step 106-1), the user Un (12) may alternatively and/or additionally optionally enter information and/or service requests of the optional servers SO1 . . . SOp (22), and/or the servers S1 . . . Sz (20) through the suer interface In (14) (step 106-5) and/or exit to the end of the process 99 at step 107.
[0506] If the user Un (12) selects additional services and/or information through the user interface In (14) (step 106-1), the user Un (12) may alternatively and/or additionally optionally enter additional requests as the user input UIn (25) at and through the user interface In (14) (step 106-6) and enter the process 99 at step 102.
V. ADDITIONAL DETAILS
A. User Input
[0507] The user input UIn (25), which the user Un (12) makes through the user interface In (14), may have one or a plurality of the same and/or different ones of the queries QQn1 . . . QQnm (53) to be made by the server PS (18) and/or the client Cn (16) of the same and/or different ones of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations Sn1 . . . Snm (30) at the corresponding server addresses AQn1 . . . AQnm (54).
[0508] The server PS (18) and/or the client Cn (16) parse, process, format, sort, group, and/or organize each of the responses Rn1 . . . Rnm (32) to the corresponding requests Qn1 . . . Qnm (29), received from the servers S1 . . . Sz (20) designated by the server designations Sn1 . . . Snm (30), and/or each of the additional optional responses RAn1 . . . RAnm (40) from the server PS (18) and/or the client Cn (16). The parsed, processed, formatted, sorted, grouped, and/or organized results from the server PS (18) and/or the client Cn (16) are communicated to the user Un (12) through the user interface In (14) as the user response URn (37), which the user Un (12) may review, interact with, and/or select additional services and/or information therefrom.
[0509] The user Un (12) enters the user input UIn (25) having one or more of the same and/or different user requests qun1 . . . qunu (26) into the user interface In (14), as shown in FIG. 3 . The user requests qun1 . . . qunu (26) are communicated from the user interface In (14) to the client Cn (16) within the suer service and/or information request iqn (27), having the user requests qun1 . . . qunu (26) and other optional information.
[0510] The user Un (12) may enter the user input UIn (25) having one or more of the same and/or different user request qun1 . . . qunu (26) into the service and/or information entry request form IEn (38) at the user interface In (14), or into the user interface In (14) through other suitable means.
[0511] The user interfaces I1 . . . In (14) have suitable input means and/or suitable presentation and/or display means, which allow the corresponding users U1 . . . Un (12) to communicate with the corresponding clients C1 . . . Cn (16). FIGS. 5A , 5B, and 6–10 show typical ones of the service and/or information entry request forms IE1 . . . IEn (38) at the user interfaces I1 . . . In (14), as graphical user interfaces (GUI's), which the users U1 . . . Un (12) may enter the corresponding user inputs UI1 . . . UIn (25) thereinto. FIGS. 77 and 78 are schematic representations of the service and/or information entry request form IEn (38) showing fields, links, and elements of the service and/or information entry request form IEn (38).
[0512] The user Un (12) may enter the user input UIn (25) into the service and/or information entry request form IEn (38) at the user interface In (14), as shown schematically in FIG. 77 . The user input UIn (25) may be entered as user input values into fields or alternate request links of the service and/or information entry request form IEn (38).
[0513] The user Un (12) may enter the user input UIn (25) as one or more of the same and/or different user requests qun1 . . . qunu (26), which may have the query values QVn1 . . . QVnu (200), server name values AVn1 . . . AVnu (201), optional instruction values VVn1 . . . VVnv (202), and/or alternate request links QLn1 . . . QLnm (203), and/or server request links ULn1 . . . ULns (204), and/or the additional request links SLn1 . . . SLnw (71) into the service and/or information entry request form IEn (38).
[0514] The user input UIn (25), thus, has one or more of the same and/or different user requests qun1 . . . qunm (26), which may be entered as the query values QVn1 . . . QVnu (200) of the same and/or different servers S1 . . . Sz (20), designated in accordance with the designation scheme corresponding to the corresponding certain ones of the server designations S11 . . . Snm (30) having the corresponding server name values AVn1 . . . AVnm (201), the optional instruction values VVn1 . . . VVnv (202), and/or the alternate request links QLn1 . . . QLnm (203), and/or the server request links ULn1 . . . ULns (204), and/or the additional request links SLn1 . . . SLnw (71) into the service and/or information entry request form IEn (38).
[0515] Each of the different user requests qun1 . . . qunu (26) may be the same and/or different one from the other. Each of the query values QVn1 . . . QVnu (200) may be the same and/or different one from the other. The query values QVn1 . . . QVnu (200) may be entered for the same and/or different ones of the servers S1 . . . Sz (20). The optional instruction values VVn1 . . . VVnv (202) may be the same and/or different one from the other.
[0516] The user Un (12) may also enter the user input UIn (25) and request services and/or information through one of the alternate request links QLn1 . . . QLna (203), or one of the server request links ULn1 . . . ULns (204), or one of the additional request links SLn1 . . . SLnw (71) at the user interface In (14).
B. USER INTERFACE DETAILS
[0517] The client-server multitasking system 10 of the present invention may have any suitable user interface In (14) acceptable to and/or preferred by the user Un (12), and acceptable to the client Cn (16). The user interface In (14) may be, for example, a graphical user interface, visual, aural, and/or tactile user interface, and/or combination thereof, or other suitable interface. The user interface In (14) may be integral with the client Cn (16) or separate therefrom.
[0518] The user interface In (14) may be hardware based, and/or computer based, and/or process based, and/or a combination thereof, and may be a graphical user interface, such as, for example, a browser and/or combination thereof, varieties of which are commonly used on the internet.
[0519] The service and/or information entry request form IEn (38) may be optionally available to the user Un (12) at the suer interface In (14), or the user Un (12) may optionally request the service and/or information entry request form IEn (38) through the user interface In (14).
[0520] Now, as shown in FIGS. 5A , 5B, and 6–10 and schematically in FIGS. 77 and 78 , the service and/or information entry request form IEn (38) at the user interface In (14) has user client request fields QDn1 . . . QDnu (206) accessible to the user Un (12) and hidden client request elements HUn1 . . . HUnh (207) hidden from the user Un (12). The user client request fields QDn1 . . . QDnu (206) accessible to the user Un (12) has server requests portion 208, optional instructions portion 209, an optional execute request element 210, and alternate requests portion 212. The hidden client request elements HUn1 . . . HUnh (207) hidden from the user Un (12) have optional server requests portion 214, optional instructions portion 216, and optional information element HEn (218).
[0521] The server requests portion 208 of the user client request fields QDn1 . . . QDnu (206) accessible to the user Un (12) has server query fields QFn1 . . . QFnu (220), which the user Un (12) may enter corresponding server query values QVn1 . . . QVnu (200) thereinto, as a portion of the user input UIn (25).
[0522] The user Un (12) may also optionally enter the server name values AVn1 . . . AVnu (201) into server name fields AFn1 . . . AFnu (224). The user Un (12) may enter the server name values AVn1 . . . AVnu (201) as another portion of the user input UIn (25).
[0523] The user Un (12) may also optionally enter the optional instructions values VVn1 . . . VVnv (202) into optional instruction fields VFn1 . . . VFnv (228) of the optional instructions portion 209 of the user client request fields QDn1 . . . QDnu (206) accessible to the user Un (12). The user Un (12) may enter the optional instruction values VVn1 . . . VVnv (202) as yet another portion of the user input UIn (25).
[0524] Upon the user Un (12) entering the user input UIn (25) of the server query values QVn1 . . . QVnu (200) and/or the server name values AVn1 . . . AVnu (201) and/or the optional instruction values VVn1 . . . VVnv (202) into the service and/or information entry request form IEn (38) at the user interface In (14), the completed service and/or information request form IFn (230) results, shown schematically in FIGS. 79 and 80 .
[0525] The user Un (12) may instruct the user interface In (14) to communicate the user service and/or information requests iqn (27), shown in FIG. 80 , having the server query values QVn1 . . . QVnu (200) and/or the server name values AVn1 . . . AVnu (201) and/or the optional instruction values VVn1 . . . VVnv (202), from the already completed service and/or information request form IFn (230) at the user interface In (14) to the client Cn (16) by entering the optional execute request element 210, using a point and click device, such as a mouse, light pen, tactile monitor, by entering a carriage return, through other user interface controls, or through other suitable means. FIG. 81 shows a schematic representation of the user service and/or information request iqn (27).
[0526] The user U=hd n (12) may alternatively enter the alternate request links QLn1 . . . QLna (203) or the server request links ULn1 . . . ULns (204) or the additional request links SLn1 . . . SLnw (71) into the service and/or information entry request form IEn (38) with a point and click device, such as a mouse, a light pen, tactile monitor, or with alternative and/or other user interface controls or other suitable means, and instruct the user interface In (14) to communicate the user service and/or information request iqn (27), having information associated with the alternate request links QLn1 . . . QLna (203) or the server request links ULn1 . . . ULns (204) or the additional request links SLn1 . . . SLnw (71), to the client Cn (16).
[0527] The server name fields AFn1 . . . AFnu (224) and the optional instruction fields VFn1 . . . VFnv (228) of the service and/or information entry request form IEn (38) may optionally have the server name values AVn1 . . . AVnu (201) and/or the optional instruction values VVn1 . . . VVnv (202) entered thereinto, respectively, as changeable and/or fixed pre-set or preselected values, drop down menu selections, and/or as blank fields, or a combination thereof. The preselected values may be replaced with values of the user's Un (12) choice or may remain fixed, depending upon choices offered in the service and/or information entry request form IEn (38). The drop down menu selections may be changed to ones of a number of preselected choices offered in the drop down menu selections, which the user Un (12) may optionally scroll through to determine which choice to make. Blank ones of the server name fields AFn1 . . . AFnu (224) and/or blank ones of the optional instruction fields VFn1 . . . VFnv (228) allow the user Un (12) to optionally enter the server name values AVn1 . . . AVnu (201) and/or the optional instruction values VVn1 . . . VVnv (202), respectively, therein, accordingly.
[0528] The server query fields QFn1 . . . QFnu (220), which the user Un (12) enters the corresponding server query values QVn1 . . . QVnu (200) thereinto, through the user input UIn (25), may also have changeable and/or fixed preselected values, drop down menu selections, and/or blank fields, or a combination thereof. However, the server query fields QFn1 . . . QFnu (220) may generally be presented to the user Un (12) as blank fields, at least for the first user input UIn (25).
[0529] The alternate requests portion 212 of the user client request fields QDn1 . . . QDnu (206) accessible to the user Un (12) had the alternate request links QLn1 . . . QLna (203), the server request links ULn1 . . . ULns (204), and the additional request links SLn1 . . . SLnw (71). The user Un (12) may alternatively request services and/or information through one of the alternate request links QLn1 . . . QLna (203), or one of the server request links ULn1 . . . ULns (204), or one of the additional request links SLn1 . . . SLnw (71).
[0530] The alternate request links QLn1 . . . QLna (203) allow the user Un (12) to make the service and/or information request IQ1 . . . IQa (28) with preconfigured optional default selections already placed in the service and/or information request IQ1 . . . IQn (28) for the user Un (12). The server request links ULn1 . . . ULnw (204) may be advertisements, advertising links, and/or links to ones of the optional servers SO1 . . . SOp (22). The user Un (12) may, for example, make requests for additional services and/or information from ones of the optional servers SO1 . . . SOp (22), using the server request links ULn1 . . . ULnw (204). The additional request links SLn1 . . . SLnw (71) allow the user Un n(12) to make additional optional selections, based upon information and/or services previously requested by the user Un (12).
[0531] The optional server requests portion 214 of the hidden client request elements HUn1 . . . HUnh (207) hidden from the user Un (12) has hidden query elements Qhn1 . . . Qhnh (236) and corresponding associated hidden server name elements Ahn1 . . . Ahnh (238). The optional instructions portion 216 of the hidden client request elements HUn1 . . . HUnh (207) hidden from the user Un (12) may have optional hidden instruction elements Vhn1 . . . VHni (240). The hidden client request elements HUn1 . . . HUnh (207) hidden from the user Un (12) may also have the hidden optional information element HEn (218), which may have optional information and/or statistics.
[0532] The user Un (12) may, thus, request the service and/or information by completing entry of the server requests portion 208 and the optional instructions portion 209 with the optional execute request element 210, after entering the server query values QVn1 . . . QVnu (200) and/or the server name values AVn1 . . . AVnu (201) and/or the optional instruction values VVn1 . . . VVnv (202), or by alternatively requesting the services and/or information through one of the alternate requests links QLn1 . . . QLna (203), or one of the server request links ULn1 . . . ULns (204), or one of the additional request links SLn1 . . . SLnw (71).
[0533] Upon completion of the user input UIn (25), the completed service and/or information request form IFn (230), as shown in FIGS. 79 and 80 , has user client request elements QMn1 . . . QMnu (246) accessible to the user Un (12) having server request elements 242 and optional instruction elements VEn1 . . . VEnv (244); and/or alternate request elements 248 of the user client request elements QMn1 . . . QMnu (246) accessible to the user Un (12); and/or optional server request elements 250, optional instruction elements 252, and/or hidden client request elements HPn1 . . . HPnh (256) hidden from the user Un (12).
[0534] The user Un (12) may instruct the user interface In (14) to communicate the user service and/or information request iqn (27) derived from the service and/or information request form IFn (230) to the client Cn (16), as shown in FIG. 81 , with the optional execute request element 210 or with the other suitable means; or the user Un (12) may alternatively communicate the user service and/or information request iqn (27) by entering the alternate request links QLn1 . . . QLna (203) or the server request links ULn1 . . . ULns (204) or the additional request links SLn1 . . . SLnw (71) into the service and/or information entry request form IEn (38) or into the completed service and/or information request form IFn (230) with a point and click device, such as a mouse, a light pen, tactile monitor, or with alternative and/or other user interface controls or other suitable means, and instruct the user interface In (14) to communicate the user service and/or information request iqn (27), having information associated with the alternate request links QLn1 . . . QLna (203) or the server request links ULn1 . . . ULns (204) or the additional request links SLn1 . . . SLnw (71), to the client Cn (16).
[0535] FIGS. 79 and 80 are schematic representations of the completed service and/or information entry request form IFn (230) showing typical elements, values, field names, name-value pairs, optional instructions, and alternate requests, resulting from the user Un (12) entering the user input UIn (25) of the server query values QVn1 . . . QVnu (200) and/or the server name values AVn1 . . . AVnu (201) and/or the optional instruction values VVn1 . . . VVnv (202) into the service and/or information entry request form IEn (38) at the user interface In (14).
[0536] Now, the completed service and/or information entry request form IFn (230) has the user client request elements QMn1 . . . QMnu (246) accessible to the user Un (12) having the server request elements 242, which has query elements QEn1 . . . QEnu (258) and corresponding associated server name elements AEn1 . . . AEnu (260).
[0537] Each of the query elements QEn1 . . . QEnu (258) have query field names QNn1 . . . QNnu (262) of the associated corresponding server query fields QFn1 . . . QFnu (220) and the corresponding server query values QVn1 . . . QVnu (200) associated therewith, which the requests Q11 . . . Qnm (29) may be derived therefrom.
[0538] Each of the server name elements AEn1 . . . AEnu (260) have server field names ANn1 . . . ANnm (264) of the associated corresponding server name fields AFn1 . . . AFnu (224) and the corresponding server name values AVn1 . . . AVnu (201) associated therewith, which server addresses An1 . . . Anu (265) may be derived therefrom.
[0539] The user client request elements QMn1 . . . QMnu (246) accessible to the user Un (12) also have the optional instruction elements VEn1 . . . VEnv (244) having optional instruction field names VNn1 . . . VNnv (266) of the associated corresponding optional instruction fields VFn1 . . . VFnv (228) and the corresponding optional instruction values VVn1 . . . VVnv (202) associated therewith.
[0540] The user client request elements QMn1 . . . QMnu (246) accessible to the user Un (12) also have the alternate request elements 246 having the alternate request links QLn1 . . . QLnu (203), or the server request links ULn1 . . . ULns (204), or the additional request links SLn1 . . . SLnw (71).
[0541] The hidden client request elements HPn1 . . . HPnh (256) hidden from the user Un (12) have the hidden query elements Qhn1 . . . Qhnh (236), which may have hidden query field names Qnn1 . . . Qnnh (268) and corresponding hidden query values Qvn1 . . . Qvnh (270) associated therewith. The hidden server name elements Ahn1 . . . Ahnh (238) may have hidden server field names Ann1 . . . Annh (272) and corresponding server hidden request name values Avn1 . . . Avnh (274) associated therewith.
[0542] The hidden client request elements HPn1 . . . HPnh (256) hidden from the user Un (12) may also have the optional hidden instruction elements Vhn1 . . . Vhni (240), which may have optional hidden instruction field names Vnn1 . . . Vnni (275) and corresponding optional hidden instruction values Vvn1 . . . Vni (276) associated therewith. The hidden client request elements HPn1 . . . HPnh (256) hidden from the user Un (12) may also have the hidden optional information element HEn (218), which may have optional hidden information element field name Jnn (277) and optional hidden information element value Jvn (278) associated therewith.
[0543] Now again, the user interfaces I1 . . . In (14) may each be different, one from the other, or the same, and may change characteristics over time. Each of the user interfaces I1 . . . In (14) may change characteristics as a function of time, information, and/or instructions, and/or other means, which may be derived by the users U1 . . . Un (12) and/or the clients Cn1 . . . Cn (16) and/or the servers S1 . . . Sz (20), and/or the server PS (18), and/or the optional servers SO1 . . . SOp (22), and/or derived within the user interfaces I1 . . . In (14). The user interface I1 . . . In (14) may change state.
[0544] The user interface I1 . . . In (14) may also change as a function of optional times and/or timed instructions associated with the user interfaces I1 . . . In (14), and/or associated with the clients C1 . . . Cn (16) and/or associated with the servers S1 . . . Sz (20), and/or associated with the server PS (18), and/or associated with the optional servers SO1 . . . SOp (22), and/or instructions from the user U1 . . . Un (12). Changes in the user interface In (14) may appear continuous to the user Un (12), spaced in time, staccato, or static depending upon the optional timers and/or the timed instructions. Other conditions may change the user interface I1 . . . In (14), as well.
[0545] The user interfaces I1 . . . In (14) may be visual, such as graphical user interfaces, aural, and/or tactile, a combination thereof, and/or other suitable means. The user interfaces I1 . . . In (14) may be integral with the clients C1 . . . Cn (16) or separate therefrom.
[0546] The user interfaces I1 . . . In (14) may change in response to the user inputs UI1 . . . UIn (25), the service and/or information entry request forms IE1 . . . IEn (38) at the user interfaces I1 . . . In (14), the completed service and/or information request forms IFn (230), the user service and/or information requests iq1 . . . iqn (27), the optional execute request elements 210, accessing the alternate request links QL11 . . . QL1a (203), accessing the server request links UL11 . . . UL1s (204), accessing the additional request links SL11 . . . SL1w (71), the service and/or information responses IR1 . . . IRn (34), the service and/or information response forms IS1 . . . ISn (39). Other conditions may change the user interface I1 . . . In (14), as well.
[0547] Portions of the user responses UR1 . . . URn (37) may be mapped into and/or onto different portions of the user interfaces I1 . . . In (14) to facilitate interaction with and the needs of each of the users U1 . . . Un (12). Such mappings may be optionally customized by the users U1 . . . Un (12).
C. SERVICE AND/OR INFORMATION REQUEST DETAILS
[0548] Each of the users U1 . . . Un (12) communicate the corresponding user service and/or information requests iq1 . . . iqn (27) through the corresponding user interfaces I1 . . . In (14) to the corresponding clients C1 . . . Cn (16), which optionally format the corresponding user service and/or information requests iq1 . . . iqn (27) into the corresponding service and/or information requests IQ1 . . . IQn (28), as required.
[0549] Now, again, the user Un (12) may instruct the user interface In (14) to communicate the user service and/or information requests iqn (27) having the server query values QVn1 . . . QVnu (200) and/or the server name values AVn1 . . . AVnu (201) and/or the optional instruction values VVn1 . . . VVnv (202), from the already completed service and/or information request form IFn (230) at the user interface In (14) to the client Cn (16) by entering the optional execute request element 210, using a point and click device, such as a mouse, light pen, tactile monitor, by entering a carriage return, through other user interface controls, or through other suitable means. FIG. 81 shows a schematic representation of the user service and/or information request iqn (27).
[0550] The user U=hd n (12) may alternatively enter the alternate request links QLn1 . . . QLna (203) or the server request links ULn1 . . . ULns (204) or the additional request links SLn1 . . . SLnw (71) into the service and/or information entry request form IEn (38) with a point and click device, such as a mouse, a light pen, tactile monitor, or with alternative and/or other user interface controls or other suitable means, and instruct the user interface In (14) to communicate the user service and/or information request iqn (27), having information associated with the alternate request links QLn1 . . . QLna (203) or the server request links ULn1 . . . ULns (204) or the additional request links SLn1 . . . SLnw (71), to the client Cn (16).
[0551] The user service and/or information request iqn (27) is communicated from the user interface In (14) to the client Cn (16), which acts upon the user service and/or information request iqn (27) to derive the service and/or information request IQn (28) therefrom. FIGS. 81–86 are schematic representations of the service and/or information request IQn (28) and/or the user service and/or information request iqn (27).
[0552] The service and/or information request IQn (28) has information and/or elements, which may be used by the server PS (18) to make the requests Qn1 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme with designates the ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30). The client Cn (16) may additionally and/or alternatively make the requests Qn1 . . . Qnm (29) of the servers S1 . . . Sz (20), using information and/or elements within the user service and/or information request iqn (27).
[0553] The service and/or information request IQn (28) has user client requests QCn1 . . . QCnu (280) accessible to the user Un (12) and hidden client requests HCn1 . . . HCnh (281) hidden from the user Un (12).
[0554] The user client requests QCn1 . . . QCnu (280) accessible to the user Un (12) and/or the hidden client requests HCn1 . . . HCnh (281) hidden from the user Un (12) have address and/or location information and/or instructions, and/or other information corresponding to information and/or services to be requested of the servers S1 . . . Sz (20), and/or information and/or instructions to be utilized by the server PS (18) and/or ones of the clients C1 . . . Cn (16).
[0555] The user client requests QCn1 . . . QCnu (280) accessible to the user Un (12) have server requests portion SQn (282), optional instructions portion Vn (283), and alternate request portion ALn (284).
[0556] The hidden client requests HCn1 . . . HCnh (281) hidden from the user Un (12) has optional hidden server requests portion HQn (285), optional hidden instructions portion HOn (286), and optional hidden information portion Jn (287).
[0557] The server requests portion SQn (282) of the service and/or information request IQn (28) has queries QSn1 . . . QSnu (288), which may be derived from the query field names QNn1 . . . QNnu (262) and the corresponding server query values QVn1 . . . QVnu (200) of the query elements QEn1 . . . QEnu (258).
[0558] The server requests portion SQn (282) of the service and/or information request IQn (28) may also have the server addresses An1 . . . Anu (265), which may be derived from the server field names ANn1 . . . ANnm (264) and the corresponding server name values AVn1 . . . AVnu (201) of the server name elements AEn1 . . . AEnu (260).
[0559] The optional instructions portion VOn (283) of the user client request QCn1 . . . QCnu (280) accessible to the user Un (12) of the service and/or information request IQn (28) may have optional instructions Vn1 . . . Vnv (289), which may be derived from the optional instructions field names VNn1 . . . VNnv (266) and the corresponding optional instruction values VVn1 . . . VVnv (202). The optional instructions Vn1 . . . Vnv (289) may optionally be used by the client Cn (16) and/or the server PS (18), and/or incorporated into the requests Qn1 . . . Qnm (29) to be made of the servers S1 . . . Sz (20) designated by the server designations Sn1 . . . Snm (30), corresponding to the requests Qn1 . . . Qnm (29) associated with the user Un (12).
[0560] The alternate request portion ALn (284) of the user client requests QCn1 . . . QCnu (280) accessible to the user Un 912) of the service and/or information request IQn (28) may be derived from one of the alternate request links QLn1 . . . QLna (203), or one of the server request links ULn1 . . . ULns (204), or one of the additional request links SLn1 . . . SLnw (71).
[0561] The optional hidden server requests portion HQn1 . . . HQnh (281) of the hidden client requests HCn1 . . . HCnh (281) hidden from the user Un (12) may have hidden queries QHn1 . . . QHnh (290) and corresponding hidden server addresses AHn1 . . . AHnh (291).
[0562] The hidden queries QHn1 . . . QHnh (290) of the optional hidden server requests portion HQn1 . . . HQnh (281) of the service and/or information request IQn (28) may be derived from the hidden query field names Qnn1 . . . Qnnh (268) and the corresponding hidden query values Qvn1 . . . Qvnh (270).
[0563] The hidden server addresses AHn1 . . . AHnh (291) of the optional hidden server requests portion HQn1 . . . HQnh (281) of the service and/or information request IQn (28) may be derived from the hidden server field names Ann1 . . . Annh (272) and the corresponding server hidden server name values Avn1 . . . Avnh (274).
[0564] The hidden queries QHn1 . . . QHnh (290) may optionally be appended to the queries QSn1 . . . QSnu (288) to be made of the servers S1 . . . Sz (20). The hidden server addresses AHn1 . . . AHnh (291) may optionally be appended to the server addresses An1 . . . Anu (265). The appended queries QSn1 . . . QSnu (288) may then be made of the servers S1 . . . Sz (20) designated by the server designations Sn1 . . . Snm (30), corresponding to the resulting appended requests Qn1 . . . Qnm (29) associated with the user Un (12), in accordance with the appended server addresses An1 . . . Anu (265).
[0565] The appended requests Qn1 . . . Qnm (29) will hereinafter be used synonymously with the requests Qn1 . . . Qnm (29), the appended queries QSn1 . . . QSnu (288) will hereinafter be used synonymously with the queries QSn1 . . . QSnu (288), and the appended server addresses An1 . . . Anu (265) will hereinafter be used synonymously with the server addresses An1 . . . Anu (265).
[0566] The optional hidden instructions portion HOn (286) of the hidden client requests HCn1 . . . HCnh (281) hidden from the user Un (12) of the service and/or information request IQn (28) have optional hidden instructions Hn1 . . . Hni (292), which may be derived form the hidden instruction field names Vnn1 . . . Vnni (275) and the corresponding optional hidden instruction values Vvn1 . . . Vvni (276). The optional hidden instructions Hn1 . . . Hni (292) may optionally be appended to the optional instructions Vn1 . . . Vnv (289) and/or may optionally be used by the client Cn (16) and/or the server PS (18), and/or incorporated into the requests Qn1 . . . Qnm (29) to be made of the servers S1 . . . Sz (29) associated with the user Un (12). The appended instructions Vn1 . . . Vnv (289) will hereinafter be used synonymously with the instructions Vn1 . . . Vnv (289).
[0567] The optional hidden information portion Jn (287) of the hidden client requests HCn1 . . . HCnh (281) hidden from the user Un (12) of the service and/or information request IQn (28) may be derived from the optional hidden information element field name Jnn (277) and the optional hidden information element value Jvn (278), and may optionally be used by the client Cn (16) and/or the server PS (18), and/or incorporated into the requests Qn1 . . . Qnm (29) to be made of the servers S1 . . . Sz 920) designated by the server designations Sn1 . . . Snm (30), corresponding to the requests Qn1 . . . Qnm (29) associated with the user Un (12).
[0568] Now, again, each of the users U1 . . . Un (12) communicate the corresponding user service and/or information request iq1 . . . iqn (27) through the corresponding user interfaces I1 . . . In (14) to the corresponding clients C1 . . . Cn 916), which optionally format the corresponding user service and/or information requests iq1 . . . iqn (27) into the corresponding service and/or information requests IQ1 . . . IQn (28), as required.
[0569] The user service and/or information requests iq1 . . . iqn (27) may be communicated from the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In 914) to the clients C1 . . . Cn (16) or alternatively from the service and/or information entry request forms IE1 . . . IEn (38) at the corresponding user interfaces I1 . . . In (14) through the alternate request links QL11 . . . QLnm (203) or the server request links UL11 . . . ULns (204) or the additional request links SL11 . . . SLnw (71).
[0570] The user service and/or information requests iq1 . . . iqn (27) may be communicated as the elements, values, field names, optional instructions, and/or alternate requests entered into the completed service and/or information entry request form IFn (230) from the corresponding user interfaces I1 . . . In 914) to the corresponding clients C1 . . . Cn (16).
[0571] The users U1 . . . Un (12) may, thus, communicate the corresponding user service and/or information requests iq1 . . . iqn (27) to the clients C1 . . . Cn (16) through the user interfaces I1 . . . In (14), upon entering the corresponding user inputs UI1 . . . UIn (25) into the corresponding service and/or information entry request forms IE1 . . . IEn (38) at the corresponding user interfaces I1 . . . In (14). The completed service and/or information entry request forms IF1 . . . IFn (230) are derived from the user inputs UI1 . . . UIn (25) having the corresponding user service and/or information requests iq1 . . . iqn (27), which may be entered as values or alternate requests thereinto the corresponding service and/or information entry request forms IE1 . . . IEn (38).
[0572] The user U1 . . . Un (12) may alternatively communicate the user service and/or information requests iq1 . . . iqn (27) by entering the alternate request links QL11 . . . QLna (203) or the server request links UL11 . . . ULns (204) or the additional request links SL11 . . . SLnw (71) into the service and/or information entry request form IE1 . . . IEn (38) or into the completed service and/or information request form IF1 . . . IFn (230).
[0573] The server PS (18) and/or the Cn 916) may alternatively and/or additionally use information resident within the server PS (18) and/or the client Cn 916), such as default information, and/or information communicated from the user Un 912) through the user interface In 914) to the client Cn (16) to make the requests Qn1 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30).
[0574] FIG. 87 is a schematic representation showing queries QQn1 . . . QQnm (53) and corresponding server addresses AQn1 . . . AQnm (54). FIGS. 88–91 show the schematic representation of FIG. 87 having typical values.
D. OPTIONAL INSTRUCTIONS
[0575] Typically, information within the optional instructions V11 . . . Vnv (289), and/or the optional hidden instructions H11 . . . Hni (292), and/or the optional hidden information portion Jn (287) are used by the server PS (18) and/or specific ones of the clients C1 . . . Cn (16), but may also be used by the servers S1 . . . Sz (20).
[0576] Now, in yet more detail, the user inputs UI1 . . . UIn (25) may have one or more of the same and/or different optional instruction values VV11 . . . VVnv (202). The optional instruction values VV11 . . . VVnv (202) may typically have instructions, which may be used by the server PS (18) and/or the clients C1 . . . Cn (16), such as, for example, as instructions on how to request, organize, present and/or display, and/or retrieve services and/or information from the servers S1 . . . Sz (20) and/or other suitable instructions.
[0577] Typical information that may be incorporated into the optional instruction values VVn1 . . . VVnv (202) may include, for example, Searches per Group 311 and Group 312, shown in FIGS. 5A , 5B, and 6–10 for a particular one of the service and/or information entry request forms IEn (38) at the user interface In (14) shown in FIGS. 81–86 .
[0578] The Searches per Group 311 is considered to be the number of the server query values QVn1 . . . QVnu (200), associated with corresponding ones of the server name values AVn1 . . . AVnu (201), corresponding to the requests Qn1 . . . Qnm (29) to make of the servers S1 . . . Sz (20). The Group 312 is considered to be the group of the server query values QVn1 . . . QVnu (200) to communicate to the ones of the servers S1 . . . Sz (20) associated with the corresponding ones of the server name values AVn1 . . . AVnu (201), in accordance with the designation scheme corresponding to the corresponding ones of the server designations Sn1 . . . Snm (30), corresponding to the request Qn1 . . . Qnm (29).
[0579] Page 313, which includes certain service and/or information location information, which may be incorporated into the requests Qn1 . . . Qnm (29) to be made of the associated corresponding ones of the servers S1 . . . Sz (20), in accordance with the designation scheme corresponding to the corresponding ones of the server designations Sn1 . . . Snm (30), may also be typically incorporated into the optional instruction values VVn1 . . . VVnv (202).
[0580] Timeout per Search Engine 314, which is substantially the maximum time for the server PS (18) and/or the particular client Cn (16) making the requests Qn1 . . . Qnm (29) to wait for each of the responses Rn1 . . . Rnm (32) from certain ones of the servers S1 . . . Sz 920), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations Sn1 . . . Snm 930), may also be typically incorporated into the optional instruction values VVn1 . . . VVnv (202).
[0581] URL's per Search Engine 315, which is the number of links and/or descriptions to be returned to the user interface In (14) from each of the responses Rn1 . . . Rnm (32), may also be typically incorporated into the optional instruction values VVn1 . . . VVnv (202). Search Engine Results 316 and URL Details 317, each of which designate different presentation and/or display schemes to be presented at the user interface In (14), may also be typically incorporated into the optional instruction values VVn1 . . . VVnv (202).
[0582] In those instance in which, for example, the service and/or information entry request form IEn (38) at the user interface In (14) has only one entry field for one of the requests Qn1 (29), as in FIGS. 6 , 8, and 10, and the optional instruction values VV11 . . . VVnv (202) are not visible, the server PS (18) and/or the particular client Cn (16) may then have default values resident therein for the Searches per Group 311, and/or the Group 312, and/or the Page 313, and/or the Timeout per Search Engine 314, and/or the URL's per Search Engine 315, and/or the Search Engine Results 316, and/or the URL Details 317, and/or other suitable ones of the optional instruction values VV11 . . . VVnv (202), and/or the server PS (18) and/or the particular client Cn (16) may establish the default values, and/or the default values may be incorporated into the optional hidden instruction values Vvn1 . . . Vvni (276).
[0583] The server PS (18) and/or the particular client Cn (16) may make the requests Qn1 . . . Qnm (29) of the servers S1 . . . Sz 920), according to the designation scheme corresponding to the corresponding ones of the server designations Sn1 . . . Snm (30), and the optional instruction values VVn1 . . . VVnv (202), typically having the Searches per Group 311, and/or the Group 312, and/or the Page 313, and/or the Timeout per Search Engine 314, and/or the URL's per Search Engine 315, and/or the Search Engine Results 316, and/or the URL Details 317, and/or the default values which may be established or to be resident within the server PS (18) and/or the particular client Cn (16), and/or the optional hidden instruction values Vvn1 . . . Vvni (276), and/or other information incorporated into the hidden client request elements HPn1 . . . HPnh (256) hidden from the user Un (12).
E. COMMUNICATING THE SERVICE AND/OR INFORMATION REQUESTS
[0584] Now, each of the users U1 . . . Un (12) communicate the corresponding user service and/or information requests iq1 . . . iqn (27) through the corresponding user interfaces I1 . . . In (14) to the corresponding clients C1 . . . Cn (16), which optionally format the corresponding user service and/or information requests iq1 . . . iqn (27) into the corresponding service and/or information requests IQ1 . . . IQn (28). The clients C1 . . . Cn (16) communicate the corresponding service and/or information requests IQ1 . . . IQn 928) to the server PS (18) and/or use the corresponding user service and/or information requests iq1 . . . iqn (27) internally to formulate the requests Q11 . . . Qnm (29).
F. PARING, PROCESSING, AND/OR FORMATTING THE SERVICE AND/OR INFORMATION REQUESTS
[0585] The server PS (18) and/or the clients C1 . . . Cn 916) parse, process, and/or format the service and/or information requests IQ1 . . . IQn (28) into the requests Q11 . . . Qnm (29), the optional instructions VJ11 . . . VJnk (52), and information to open connections OC11 . . . OCnm (323). FIG. 92 shows a particular one of the requests Qnm (29), the optional instructions VJn1 . . . VJnk (52), and the information to open connections OC11 . . . OCnm (323), which may be parsed, processed, and/or formatted from a particular one of the service and/or information requests IQn (28). The clients C1 . . . Cn (16) may alternatively and/or additionally parse, process, and/or format the user service and/or information requests iq1 . . . iqn (27) directly into the requests Q11 . . . Qnm (29), and/or the optional instructions VJ11 . . . VJnk (52) and the information required to open the connections OC11 . . . OCnm (323), as required.
[0586] Upon receipt of the service and/or information requests IQ1 . . . IQn (28) at the server PS (18), communicated form the clients C1 . . . Cn (16), the server PS (18) parses, processes, and/or formats each of the corresponding service and/or information requests IQ1 . . . IQn (28) into the corresponding queries QQ11 . . . QQnm (53) and the corresponding server addresses AQ11 . . . AQnm (54) to open connections OC11 . . . OCnm (323) with and make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz 920) to be communicated with corresponding to the requests Q11 . . . Qnm (29), and/or the optional instructions VJ11 . . . VJnk (52) to be used by the server PS (18) in making the request Q11 . . . Qnm (29) and/or in processing, formatting, grouping, and organizing the responses R11 . . . Rnm (32) from the ones of the servers S1 . . . Sz 920) corresponding to the server designations S11 . . . Snm (30), and/or the additional optional responses RA11 . . . RAnm (40), into the corresponding service and/or information responses IR1 . . . IRn (34), as shown in FIG. 92 .
[0587] Alternatively and/or additionally, upon receipt of the user service and/or information requests iq1 . . . iqn (27) at the corresponding clients C1 . . . Cn (16), the corresponding clients C1 . . . Cn (16) may parse, process, and/or format each of the user service and/or information requests iq1 . . . iqn (27) into corresponding queries QQ11 . . . QQnm (53) and corresponding server addresses AQ11 . . . AQnm (54) to open connections OC11 . . . OCnm (323) with and make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29), and/or the optional instructions VJ11 . . . VJnk (52) to be used by the corresponding clients C1 . . . Cn (16) in making the requests Q11 . . . Qnm (29) and/or in processing, formatting, grouping, and organizing the responses R11 . . . Rnm (32) from the ones of the servers S1 . . . Sz (20) corresponding to the server designations S11 . . . Snm (30), and/or the additional optional responses RA11 . . . RAnm (40), into the corresponding user service and/or information responses ir1 . . . irn (36).
[0588] The server PS (18) parses, processes, and/or formats each of the service and/or information requests IQ1 . . . IQn (28) into queries, server addresses to make the queries of, query groups and/or server groups, and instructions to be used by the server PS (18), typically when the server PS (18) makes the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20) corresponding to the server designations S11 . . . Snm 930) and/or the server PS (18) processes, formats, groups, and organizes the responses R11 . . . Rnm (32) from the ones of the servers S1 . . . Sz (20) corresponding to the server designations S11 . . . Snm (30) at the server PS (18). Otherwise, the clients C1 . . . Cn 916) may parse, process, and/or format each of the user service and/or information requests iq1 . . . iqn (27) into queries, server addresses to make the queries of, query groups and/or server groups, and instructions, typically when the clients C1 . . . Cn (16) make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz 920) corresponding to the server designations S11 . . . Snm (30) and/or the clients C1 . . . Cn (16) process, format, group, and organize the responses R11 . . . Rnm (32) from the ones of the servers S1 . . . Sz (20) corresponding to the server designations S11 . . . (30) at the corresponding clients C1 . . . Cn (16). Choice as to whether the server PS (18) and/or the clients C1 . . . Cn 916) makes the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20) corresponding to the server designations S11 . . . Snm 930) and/or process, format, group, and organize the responses R11 . . . Rnm (32) are dependent on processing capabilities of the server PS (18) and/or the clients C1 . . . Cn (16) and other factors.
[0589] Ones of the requests Q11 . . . Qnm (29) may require further formatting and/or processing by the server PS (18) and/or the corresponding clients C1 . . . Cn 916) and/or other ones of the requests Q11 . . . Qnm (29) may already be formatted in accordance with requirements with respect to communications protocols, the service and/or information requests IQ1 . . . IQn (28), the servers S1 . . . Sz (20), and/or the optional servers SO1 . . . SOp (22), and/or the server PS (18), and/or other requirements of the network 24 of the client-server multitasking system 10. The server PS (18) and/or the clients C1 . . . Cn (16) parse, process, and/or format the requests Q11 . . . Qnm (29), as required.
G. FORMULATING THE REQUESTS
[0590] Each of the optional instructions VJ11 . . . VJnk (52) is typically parsed, and/or processed, and/or formatted, and/or grouped, and/or organized into particular ones of the optional instructions VJn1 . . . VJnk (52) for use by the server PS (18) and/or particular ones of the clients C1 . . . Cn (16), a particular one of the clients C1 . . . Cn 916) being designated as the client Cn (16).
[0591] Each of the alternate request links QLn1 . . . QLna (203) and the additional request links SL11 . . . SLnw (71) are also typically parsed, and/or processed, and/or formatted, and/or grouped, and/or organized for use by the server PS (18) and/or particular ones of the clients C1 . . . Cn 916), a particular one of the clients C1 . . . Cn (16) being designated as the client Cn (16).
[0592] The alternate request links QLn1 . . . QLna (203) allow the user Un (12) to make the service and/or information request IQ1 . . . IQn (28) with preconfigured optional default selections already placed in the service and/or information request IQ1 . . . IQn (28) for the user Un (12). The additional request links SLn1 . . . SLnw (71) allow the user Un (12) to make additional optional selections, based upon information and/or services previously requested by the user Un (12).
[0593] Typical ones of the optional instructions VJn1 . . . VJnk (52) and the additional request links SLn1 . . . SLnw (71) that may be parsed, processed, and/or formatted from the service and/or information request IQn (28) and/or the user service and/or information request iqn (27) are shown in FIG. 96 .
[0594] The requests Q11 . . . Qnm (29) may be made by the server PS (18) and/or the corresponding clients C1 . . . Cn (16) of the associated corresponding ones of the servers S1 . . . Sz (20), according to the designation scheme corresponding to the corresponding ones of the server designations S11 . . . Snm (30), in accordance with the optional instructions VJ11 . . . VJnk (52) and/or default values for the optional instructions VJ11 . . . VJnk (52) resident within the server PS (18) and/or the corresponding clients C1 . . . Cn 916).
[0595] The service and/or information responses IR1 . . . IRn (34) and/or the corresponding user service and/or information responses ir1 . . . irn (36) may be formulated by the server PS (18) and/or the corresponding clients C1 . . . Cn (16), in accordance with the optional instructions VJ11 . . . VJnk (52) and/or default values for the optional instructions VJ11 . . . VJnk (52) resident within the server PS (18) and/or the corresponding clients C1 . . . Cn (16).
[0596] The optional instructions VJn1 . . . VJnk (52) and the additional request links SL11 . . . SLnw (71) for a particular one of the service and/or information requests IQn (28) may typically have Searches per Group 326, and/or Group 327, and/or Page 328A, and/or Page 328B, and/or Timeout per Search Engine 329, and/or URL's per Search Engine 330, and/or Search Engine Results 331A and/or Search Display 331B, and/or URL Details 332A and/or Description and/or List 332B, as shown in FIG. 96 . Default values may additionally and/or alternatively be established or be resident for any and/or all of the optional instructions VJ11 . . . VJnk 952) within the server PS (18) and/or the clients C1 . . . Cn (16).
[0597] The Searches per Group 326 are typically considered to be the number of the queries QQn1 . . . QQnm (53) to make of the servers S1 . . . Sz 920) at the corresponding server addresses AQn1 . . . AQnm (54), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz 920) to make the requests Qn1 . . . Qnm (29) of as the corresponding ones of the server designations Sn1 . . . Snm (30).
[0598] The group 327 is considered to be the group of the queries QQn1 . . . QQnm (53) to make of the servers S1 . . . Sz 920) at the corresponding server addresses AQn1 . . . AQnm (54), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to make the requests Qn1 . . . Qnm (29) of as the corresponding ones of the server designations Sn1 . . . Snm (30).
[0599] The Page 328A and the Page 328B have certain service and/or information location information, which may be incorporated into the requests Qn1 . . . Qnm (29) to be made of the associated corresponding ones of the servers S1 . . . Sz (20), at the corresponding server addresses AQn1 . . . AQnm (54), in accordance with the designation scheme corresponding to the corresponding ones of the server designations Sn1 . . . Snm (30).
[0600] The Timeout per Search Engine 329 is considered to be substantially the maximum time for the server PS (18) and/or the particular client Cn 916) making the requests Qn1 . . . Qnm (29) to wait for each of the responses Rn1 . . . Rnm (32) from certain ones of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) as the corresponding server designations Sn1 . . . Snm (30).
[0601] The URL's per Search Engine 330, is considered to be the number of links, and/or descriptions, and/or prices/values, and/or images to be returned to the user interface In (14) from each of the responses Rn1 . . . Rnm (32).
[0602] The Search Engine Results 331A and the Search Display 331B each designate presentation and/or display schemes to be presented at the user interface In 914). The URL Details 332A and the Description and/or List 332B each also designate presentation and/or display schemes to be presented at the user interface In (14).
[0603] FIG. 133 is a schematic representation of certain typical optional instructions VJnm1 . . . VJnk 952) and/or certain additional request links SLn1 . . . SLnw (71), referred to as the Search Engine Results 331A, which are shown to Interleave 331A-1, Separate 331A-2, Combine $[a–z] 331A-3, Combine $[z–a] 331A-4, Separate $[a–z] 331A-5, Separate $[z–a] 331A-6, which are instructions for parsing, processing, sorting, and/or formatting the service and/or information response IRn (34).
[0604] FIG. 134 is a schematic representation of other certain typical optional instructions VJnm1 . . . VJnk (52) and/or other certain additional request links SLn1 . . . SLnw (71), referred to as the URL Details 332A, which are other instructions for parsing, processing, sorting, and/or formatting the service and/or information response IRn (34) in Summary 332A-1 or List 332A-2 formats.
[0605] FIG. 135 depicts certain typical additional request links SLn1 . . . SLnw (71), and also shows the Search Display 331B, which are shown to be Interleave 331B-1, Separate 331B-2, Combine $[a–z] 331B-3, Combine $[z–a] 331B-4, Separate $[a–z] 331B-5, Separate $[z–a] 331B-6, which are instructions for parsing, processing, sorting, and/or formatting the service and/or information response IRn (34) and the Description and/or List 332B, which are other instructions for parsing, processing, sorting, and/or formatting the service and/or information response IRn (34) in Summary of List formats.
[0606] The optional instructions VJn1 . . . VJnk (52) may also typically have Next Group 333 and Previous Group 334, which are considered to be the next group and the previous group, respectively, to make the queries QQn1 . . . Qnm (53) thereof at the next and previous ones of the corresponding groups of the queries QQn1 . . . QQnm (53) to make of the servers S1 . . . Sz (20) thereof at the corresponding server addresses AQn1 . . . AQnm (54), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to make the requests Qn1 . . . Qnm (29) thereof as the corresponding ones of the server designations Sn1 . . . Snm (30). Information about Current Group 337 having the queries QQn1 . . . QQnm (53) and the server addresses AQn1 . . . AQnm (54) is also shown. Current Page Number 338 is also indicated.
[0607] The optional instructions VJn1 . . . VJnk (52) for a particular one of the service and/or information requests IQn (28) may also typically have Next Page 335 and Previous Page 336, each of which has certain different service and/or information location information, which may be incorporated into the requests Qn1 . . . Qnm (29) to be made of the associated corresponding ones of the servers S1 . . . Sz (20), in accordance with the designation scheme corresponding to the corresponding ones of the server designations Sn1 . . . Snm (30).
H. DETERMINING QUERIES AND SERVERS TO MAKE THE REQUESTS THEREOF
[0608] The server PS (18) and/or the clients C1 . . . Cn (16) evaluate the optional instructions VJ11 . . . VJnk (52), determine the queries QQ11 . . . QQnm (53) and the servers S1 . . . Sz (20) to make the requests Q11 . . . Qnm (29) thereof at the corresponding server addresses AQ11 . . . AQnm (54), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with as the server designations S11 . . . Snm (30), corresponding to the requests Q11 . . . Qnm (29), and group the queries QQ11 . . . QQnm (53) and the corresponding server addresses AQ11 . . . AQnm (54) associated therewith.
[0609] FIG. 96 shows typical ones of the queries QQn1 . . . QQnm (53), the corresponding server addresses AQn1 . . . AQnm (54), and the optional instructions VJn1 . . . VJnk (52) that may be parsed, processed, and/or formatted from the service and/or information request IQn (28) and/or the user service and/or information request iqn (27).
[0610] The queries QQ11 . . . QQnm (53) and the servers S1 . . . Sz (20) to make the requests Q11 . . . Qnm (29) thereof are typically based upon the values designated in and parsed from the queries QQ11 . . . QQnm (53) and the values designated in and parsed from the corresponding server addresses AQ11 . . . AQnm (54), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with as the server designations S11 . . . Snm (30), corresponding to the requests Q11 . . . Qnm (29), and the Searches per Group 326, the Group 327, the Page 328A and/or the Page 328B within the optional instructions VJ11 . . . VJnk (52).
[0611] The server PS (18) and/or the clients C1 . . . Cn (16) evaluate the values in the Group 327, the Searches per Group 326, the queries QQ11 . . . QQnm (53), and the corresponding server addresses AQ11 . . . AQnm (54), and determine the servers S1 . . . Sz (20) corresponding to the corresponding server addresses AQ11 . . . AQnm (54) within the Group 327, in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with as the server designations S11 . . . Snm (30) to make the requests Q11 . . . Qnm (29) thereof, and the Page 328A, and/or the Page 328B.
[0612] The Group 327 and the Searches per Group 326 are used to determine which of the servers S1 . . . Sz (20) to make the requests Q11 . . . Qnm (29) thereof.
[0613] The server PS (18) and/or the clients C1 . . . Cn (16) determine the size of the Group 327 from the Searches per Group 326 and the Group 327, and the servers S1 . . . Sz (20) associated with the corresponding server addresses AQ11 . . . AQnm (54) within the Group 327, in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with as the server designations S11 . . . Snm (30).
[0614] The Searches per Group 326 and the Group 327 are used to formulate the current request groups QA1c . . . QAnc (50) having the corresponding queries QQ11 . . . QQnm (53) and the corresponding server addresses AQ11 . . . AQnm (54) to open connections with and make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) thereof as the server designations S11 . . . Snm (30), corresponding to the requests Q11 . . . Qnm (29), for corresponding ones of the service and/or information requests IQ1 . . . IQn (28) and/or the user service and/or information requests iq1 . . . iqn (27).
[0615] The queries QQ11 . . . QQnm (53), the server addresses AQ11 . . . AQnm (54), and the Page 328A and/or the Page 328B provide the location of information and/or services to the server PS (18) and/or the clients C1 . . . Cn (16) within the Group 327, in accordance with the Searches per Group 326, to make the requests Q11 . . . Qnm (29) thereof, in accordance with the designation scheme which designates the ones of the servers S1 . . . Sz (20) to make the requests Q11 . . . Qnm (29) thereof as the server designations S11 . . . Snm (30), corresponding to the requests Q11 . . . Qnm (29).
[0616] The URL's per Search Engine 330 determine whether the server PS (18) and/or the clients C1 . . . Cn (16) communicate additional ones of the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), depending upon the number of the links, and/or descriptions, and/or prices/values, and/or images requested by ones of the user U1 . . . Un (12) to be returned to the user interfaces I1 . . . In (14), and the number of links, and/or descriptions, and/or prices/values, and/or images available within each of the corresponding ones of the responses R11 . . . Rnm (32). If insufficient ones of the links, and/or descriptions, and/or prices/values, and/or images are not available within the responses R11 . . . Rnm (32) to satisfy deliver of the number of the URL's per Search Engine 330 requested by certain ones the users U1 . . . Un (12), the server PS (18) and/or the clients C1 . . . Cn (16) may yet make additional ones of the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in order deliver the number of links, and/or descriptions, and/or prices/values, and/or images requested in the number of the URL's per Search Engine 330 to the user interfaces I1 . . . In (14) requested by certain ones of the user U1 . . . Un (12).
[0617] If the optional instructions do not indicate which ones of the servers S1 . . . Sz (20) to make the requests Q11 . . . Qnm (29) thereof, in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with as the server designations S11 . . . Snm (30), corresponding to the requests Q11 . . . Qnm (29), default values may be used. The default values may be resident within the server PS (18) and/or the client C1 . . . Cn (16).
[0618] If all and/or a portion of the optional instructions VJ11 . . . VJnk (52) are absent and/or are not communicated to the server PS (18) and/or the clients C1 . . . Cn (16), default values may be used. The default values may be resident within the server PS (18) and/or the clients C1 . . . Cn (16).
I. GROUPING THE QUERIES AND SORTING/GROUPING CRITERIA
[0619] Upon receipt of the service and/or information requests IQ1 . . . IQn (28) at the server PS (18), communicated from the corresponding clients C1 . . . Cn (16), the server PS (18) parses, processes, and/or formats each of the service and/or information requests IQ1 . . . IQn (28) into the corresponding current request groups QA1c . . . QAnc (50) having the corresponding queries QQ11 . . . QQnm (53) and the corresponding server addresses AQ11 . . . AQnm (54) to open connection with and make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), shown for a particular one of the service and/or information requests IQn (28) in FIG. 59 . The process 104 of deriving the service and/or information response IRn (34) for the grouping and/or sorting criteria of FIG. 59 is shown in FIG. 71 .
[0620] The server PS (18) also parses, processes, and/or formats each of the service and/or information requests IQ1 . . . IQn (28) into the corresponding request groups QA11 . . . QAnz (51) having the corresponding other queries QQ1n . . . QQnz (55) and the corresponding other server addresses AQ1a . . . AQnz (56), and the corresponding optional instructions VJ11 . . . VJnk (52), also shown for a particular one of the service and/or information requests IQn (28) in FIG. 59 .
[0621] Certain ones of the clients C1 . . . Cn (16) may alternatively and/or additionally make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), and formulate the corresponding user service and/or information response ir1 . . . irn (36), as previously described, as shown in FIG. 63 . The process 104 of deriving the user service and/or information response irn (36) for the grouping and/or sorting criteria of FIG. 59 is shown in FIG. 71 .
[0622] Upon receipt of the user service and/or information requests iq1 . . . iqn (27) at the corresponding clients C1 . . . Cn (16), certain ones of the corresponding clients C1 . . . Cn (16) may parse, process, and/or format the corresponding user service and/or information requests iq1 . . . iqn (27) into the corresponding current request groups QA1c . . . QAnc (50) having the corresponding queries QQ11 . . . QQnm (53) and the corresponding server addresses AQ11 . . . AQnm (54) to open connections with and make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29), shown for a particular one of the user service and/or information requests iqn (27) in FIG. 63 . The corresponding clients C1 . . . Cn 916) may also parse, process, and/or format the corresponding user service and/or information response ir1 . . . irn (36) into the corresponding request groups QA11 . . . QAnz (51) having the corresponding other queries QQ1a . . . QQnz (55) and the corresponding other server addresses AQ1a . . . AQnz (56), and the corresponding optional instructions VJ11 . . . VJnk (52), also shown for a particular one of the user service and/or information requests iqn (27) in FIG. 63 .
[0623] The server PS (18) makes the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz 920) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), as shown in FIG. 59 , and certain ones of the client C1 . . . Cn (16) may additionally and/or alternatively make the requests Q11 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30), as shown in FIG. 63 .
[0624] The Searches per Group 326 and the Group 327 are used to formulate the current request group QAnc (50) having the corresponding queries QQn1 . . . QQnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) to open connections with and make the requests Qn1 . . . Qnm (29) of the servers S1 . . . Sz (20), in accordance with the designation scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Qn1 . . . Qnm (29) thereof as the server designations S11 . . . Snm (30), corresponding to the requests Q11 . . . Qnm (29), for the service and/or information request IQn (28) and/or the user service and/or information request iqn (27).
[0625] Information from the current request group QAnc (50) having the corresponding queries QQn1 . . . QQnm (53) and the corresponding server addresses AQn1 . . . AQnm (54) is formulated into the corresponding request pointer/address group QZn (60) having the pointers/addresses PGn1 . . . PGnz (61) associated therewith, as shown in FIGS. 59 and 63 .
[0626] Each of the pointer/addresses PGn1 . . . PGnz (61) are directed to point/address the corresponding addressable query pointer/address groups QGn1 . . . QGnz (62) associated therewith, which aid in obtaining service and/or information from the certain ones of the addressable response information groups RGn1 . . . RGnm (57) to be incorporated into the query information groups GIn1 . . . GInz (63).
[0627] Ones of the addressable query information groups GIn1 . . . GInz (63) may be associated with corresponding ones of the addressable query pointer/address groups QGn1 . . . QGnz (62).
[0628] Each of the addressable query pointer/address groups QGn1 . . . QGnz (62) associated with the service and/or information request IQn has the pointers/addresses PPn11 . . . PPnmr (64) directed to address/point services and/or information in the addressable response information groups RGn1 . . . RGnm (57), based upon the grouping and/or sorting criteria.
[0629] Information and/or services in the addressable response information groups RGn1 . . . RGnm (57) is addressed with the pointers/addresses PPn11 . . . PPnmr (64) from the query pointer/address groups QGn1 . . . QGnz (62), and information and/or services from the addressable response information groups RGn1 . . . RGnm (57) is incorporated into the addressable query information groups GIn1 . . . GInz (63) corresponding to the pointer/addresses PPn11 . . . PPnmr (64), which are formulated by the addressable query pointer/address groups QGn1 . . . QGnz (62), in accordance with the grouping and/or sorting criteria.
[0630] FIGS. 59 and 63 show the request pointer/address group QZn (60), the addressable query pointer/address groups QGn1 . . . QGnz (62), the pointers/addresses PPn11 . . . PPnmr (64), associated ones of the addressable response information groups RGn1 . . . RGnm (57), and the query information group GInz (63) associated with the query pointer/address group QGnz (62). FIGS. 59 and 63 show the rth pointers/addresses PPn1r . . . PPnmr (64), which point to the rth optional addressable pointer/address indices INnmr . . . INnmr (81) of the corresponding rth individual information groups LGn1r . . . LGnmr (80) of the addressable response information groups RGn1 . . . RGnm (57) associated with the query pointer/address group QGnz (62) and the associated query information group GInz (63).
[0631] FIG. 97 shows the request pointer/address group QZn (60), a particular one of the addressable query pointer/address groups QGn1 . . . QGnz (62), designated as the query pointer/address group QGnz (62), the pointers/addresses PPn11 . . . PPnmr (64), associated ones of the addressable response information groups RGn1 . . . RGnm (57), and the query information group GInz (63) associated with the query pointer/address group QGnz (62).
[0632] The addressable query pointer/address groups QGn1 . . . QGnz (62) each have corresponding ones of query information groups GIn1 . . . GInz (63) associated therewith. Each of the query information groups GIn1 . . . GInz (63) have information and/or services therein, which are derived from information and/or services obtained from the certain ones of the addressable response information groups RGn1 . . . RGnm (57), which are addressed to provide such information with the aid of the corresponding pointers/addresses PPn11 . . . PPnmr (64). Each of the pointers/addresses PPn11 . . . PPnmr (64) are directed to point/address information and/or services in the corresponding response information groups RGn1 . . . RGnm (57) associated therewith, which the information and/or services incorporated into the ones of the query information groups GIn1 . . . GInz (63) associated with the corresponding addressable query pointer/address groups QGn1 . . . QGnz (62) is obtained therefrom.
[0633] The addressable query pointer/address groups QGn1 . . . QGnz (62) may be used to aid in formulating the query information groups GIn1 . . . GInz (63), having information obtained from the addressable response information groups RGnm (57), resulting from certain ones of the queries QQn1 . . . QQnm (53) grouped one with the other and/or the associated ones of the corresponding server addresses AQn1 . . . AQnm (54). The query information groups GIn1 . . . GInz (63) may be presented to the user Un (12) through the user interface In (14). The addressable query pointer/address groups QGn1 . . . QGnz (62) may be derived from query criteria in the optional instructions VJ11 . . . VJnk (52) and/or using default criteria resident within the server PS (18) and/or the client Cn (16).
[0634] Query grouping criteria giving the user Un (12) the ability to formulate the addressable query pointer/address groups QGn1 . . . QGnz (62) may be incorporated into the optional instructions VJ11 . . . VJnk (52), which may be entered into the user interface In (14) through the user input UIn (25) by the user Un 912). Typically, however, the queries QQn1 . . . QQnm (53) having the same and/or substantially the same values are grouped one with the other in individual ones of the addressable query pointer/address groups QGn1 . . . QGnz (62). Default criteria may be resident within the server PS (18) and/or the client Cn (16).
[0635] The size of the request pointer/address group QZn (60) and which particular ones of the queries QQn1 . . . QQnm (53) and the corresponding ones of the server addresses AQn1 . . . QGnm (54) to use in the requests Qn1 . . . Qnm (29), and thus construction and/or formulation of the addressable query pointer/address groups QGn1 . . . QGnz (62) to incorporate into the particular request pointer/address group QZn (60), and, thus, delivery of information in the query information groups GIn1 . . . GInz (63) is determined by the current request groups QA1c . . . QAnc (50), which may be determined from the Group 327 and the Searches per Group 326, the queries QQn1 . . . QQnm (53) and the corresponding ones of the server addresses AQn1 . . . AQnm (54) therein.
[0636] Certain ones of the queries QQn1 . . . QQnm (53) may be grouped one with the other in the addressable query pointer/address groups QGn1 . . . QGnz (62), which have the certain ones of the queries QQn1 . . . QQnm (53) and the corresponding ones of the server addresses AQn1 . . . AQnm (54) associated therewith, and the corresponding pointers/addresses PPn11 . . . PPnmr (64) associated with the certain ones of the queries QQn1 . . . QQnm (53), the corresponding ones of the server addresses AQn1 . . . AQnm (54), and certain ones of response information groups RGn1 . . . RGnm (57).
[0637] Typical sorting and/or grouping criteria, for example, may group certain ones of the queries QQn1 . . . QQnm (53) having the same and/or substantially the same values grouped in a particular one of the query information groups GInz . . . GInz (63), designated as the query information group GInz (63), as shown in FIG. 98 and in certain ones of FIGS. 27A–52C , inclusive.
[0638] Alternatively and/or additionally, other typical sorting and/or grouping criteria, for example, may group certain ones of the server addresses AQn1 . . . AQnm (54), having the same and/or substantially the same values grouped in a particular one of the query information groups GInz . . . GInz (63), designated as the query information group GInz (63), as shown in FIG. 99 .
[0639] FIGS. 97–99 show the rth pointers/addresses PPner (64), PPnrr (64), and PPnwr (64), which point to the rth optional addressable pointer/address indices INner (81), INnrr (81), and INnwr (81) of the corresponding rth individual information groups LGner (80), LGnrr (80), and LGnwr (80) of the addressable response information groups RGne (57), RGnr (57), and RGnw (57) associated with the query pointer/address group QGnz (62) and the associated query information group GInz (63).
[0640] Alternatively and/or additionally, the user Un 912) may select query grouping criteria, which simply provides information to the user interface In (14), separately with respect to the individual server addresses AQn1 . . . AQnm (54), as shown in FIGS. 60 and 64 and in certain ones of FIGS. 27A–52C , inclusive. For example, the query information groups GIn1 . . . GInz (63), may alternatively and/or additionally be correspondingly associated with the server address AQn1 . . . AQnm (54), and, thus, may be correspondingly associated with the addressable response information groups RGn1 . . . RGnm (57). The query information group GIn1 (63) may, thus, be associated with the server address AQn1 (54), the addressable response information group RGn1 (57), and the query information group GIn1 (63); the query information group GIn2 (63) may, thus, be associated with the server address AQn2 (54), the addressable response information group RGn2 (57), and the query information group GIn2 (63), and so on; and the query information group GInz (63) may, thus, be associated with the server address AQnz (54), the addressable response information group RGn2 (57), and the query information group GInz (63), as shown in FIGS. 60 and 64 . The process 104 of deriving the service and/or information response IRn (34) and/or the user service and/or information response irn (36) for the grouping and/or sorting criteria of FIGS. 60 and 64 is shown in FIG. 72 .
[0641] The pointing/addressing scheme of FIGS. 60 and 64 is, of course, a much simpler pointing/addressing scheme than the pointing/addressing scheme of FIGS. 59 and 63 , and does not require incorporating the addressable query pointer/address groups QGn1 . . . QGnz (62) into the request pointer/address group QZn (60). Each of the pointers/addresses PFn11 . . . PFnmr (69), of FIGS. 60 and 64 , may then be directed to point/address the corresponding response information groups RGn1 . . . RGnm (57) directly from the request pointer/address group QYns (68), to obtain information from the corresponding response information groups RGn1 . . . RGnm (57) and incorporating into corresponding ones of the corresponding query information groups GIn1 . . . GInz (63), as shown in FIGS. 60 and 64 . In this case, the addressable query pointer/address groups QGn1 . . . QGnz (62) may be bypassed and/or eliminated completely, thus simplifying the process. OF course, then, in this case, the resulting sorting and grouping is not as sophisticated, and allows for such simplification.
[0642] The above sorting criteria addressing schemes are meant only as typical examples of sorting criteria addressing schemes that may be used. Yet other sorting criteria addressing schemes and/or combinations thereof may be used.
[0643] FIG. 100 shows typical ones of the addressable query pointer/address groups QGn1 . . . QGnz (62) having the typical ones of the queries QQn1 . . . QQnm (53), the typical ones of the server addresses AQn1 . . . AQnm (54), and the corresponding ones of typical ones of the pointers/addresses PPn11 . . . PPnmr (64) having the same ones of the queries QQn1 . . . QQnm (53) grouped one with the other in individual ones of the addressable query pointer/address groups QGn1 . . . QGnz (62).
[0644] More particularly, FIG. 100 shows the query pointer/address group QGn1 (62), the query pointer/address group QGn2 (62), and the query pointer/address group QGn3 (62). The query pointer/address group QGn1 (62) of FIG. 100 has the same ones of the queries QQn1 (53), QQn2 (53), QQn3 (53), and QQn9 (53), the ones of the server addresses AQn1 (54), AQn2 (54), AQn3 (54), and AQn9 (54), and the ones of the pointers/addresses PPn1r (64), PPn2r (64), PPn3r (64), nd PPn9r (64) associated therewith. The query pointer/address group QGn2 (62) of FIG. 100 has the same ones of the queries QQn4 (53) and QQn7 (53), the ones of the server addresses AQn4 (54) and AQn7 (54) the ones of the pointer/addresses PPn4r (64) and PPn7r (64) associated therewith. The query pointer/address group QGn3 (62) of FIG. 100 has the same ones of the query values QQn5 (53), QQn6 (53), and QQn8 (53), the ones of the server addresses AQn5 (54), AQn6 (54), and AQn8 (54) and the ones of the pointers/addresses PPn5r (64), PPn6r (64), and PPn8r (64) associated therewith.
[0645] The addressable query pointer/address groups QGn1 . . . QGnz (62), however, may alternatively and/or additionally be grouped, for example, by the server addresses AQn1 . . . AQnm (54) and have the corresponding query values QQn1 . . . QQnm (53) associated therewith. Ones of the same and/or substantially the same ones of the server addresses AQn1 . . . AQnm (54), for example, having the corresponding queries QQn1 . . . QQnm (53) associated therewith may be used as the grouping criteria.
[0646] FIG. 101 shows another schematic representation of the typical ones of the addressable query pointer/address groups QGn1 . . . QGnz (62) having the typical ones of the queries QQn1 . . . QQnm (53), the typical ones of the server addresses AQn1 . . . AQnm (54), and the typical the ones of the pointer/addresses PPn11 . . . PPnmr (64) of FIG. 100 associated therewith.
[0647] FIG. 102 is a generic schematic representation of the addressable query pointer/address groups QGn1 . . . QGnz (62) having the queries QQn1 . . . QQnm (53), the server addresses AQn1 . . . AQnm (54), and the pointers/addresses PPn11 . . . PPnmr (64) associated therewith.
[0648] Certain information in the addressable response information groups RGn1 . . . RGnm (57) may be associated with the corresponding queries QQn1 . . . QQnm (53) and/or the corresponding server addresses AQn1 . . . AQnm (54) within the current request group QAnc (50), and may optionally be used by the server PS (18) and/or the client Cn (16).
[0649] Certain information in the addressable response information groups RGn1 . . . RGnm (57) may also be incorporated into the optional instructions VJn1 . . . VJnk (52). Such information may be incorporated into the optional instructions VJn1 . . . VJnk 952) and/or may also be additionally and/or alternatively optionally resident within the server PS (18) and/or the client Cn (16).
J. COMMUNICATING THE REQUESTS TO THE SERVERS
[0650] The server PS (18) and/or the clients C1 . . . Cn (16) contact and open the connections OC11 . . . OCnm (323) with ones of the servers S1 . . . Sz (20), according to the server designations S11 . . . Snm (30) at the corresponding server addresses A11 . . . Anu (265) at corresponding ports W11 . . . Wnm (343). The server PS (18) and/or the clients C1 . . . Cn (16) communicate the requests Q11 . . . Qnm (29) of one or more of the same and/or different ones of the servers S1 . . . Sz (20), designated within the Group 327 and the Searches per Group 326 to make the requests Q11 . . . Qnc (29) thereof, in accordance with the designation scheme corresponding to the corresponding ones of the server designations S11 . . . Snmm (30), corresponding to the requests Q11 . . . Qnm (29). If the Group 327 is not specified and/or the Searches per Group 326 are not specified by the users U1 . . . Un (12), default values may additionally and/or alternatively values be used.
[0651] A particular one of the requests Q11 . . . Qnm 929), hereinafter designated as the request Qnm (29), corresponding to one request within the requests Qn1 . . . Qnm (29) corresponding to the user Un (12), is shown schematically in FIG. 103 .
[0652] Information 344 that may be used for formulating a typical particular one of the requests Qnm (29) from the service and/or information request IQn (28), and parsing, processing, and/or formatting the optional instructions VJn1 . . . VJnk (52), and opening the connection OCnm (323) is shown in FIGS. 92–95 .
[0653] Now, in more detail, the request Qnm (29) may have a corresponding request line Lnm (345), corresponding optional request header fields JHn1 . . . JHns (346), and a corresponding optional entity body EHnm (347). The request line Lnm (345) may have a corresponding method Mnm (348), a corresponding target resource Pnm (349), which may have information associated with the corresponding query QQnm (53), and corresponding protocol Bnm (350).
[0654] The user Un 912), the server PS (18) and/or the client Cn (16) may optionally specify the port Wnm (343) to communicate the request Qnm (29) therethrough, and/or the method Mnm (348), and/or the protocol Bnm (350). The port Wnm (343), and/or the method Mnm (348), and/or the protocol Bnm (350) may optionally be resident within the server PS (18) and/or the client Cn (16). Default values may also be used for the port Wnm (343) and/or the protocol Bnm (350).
[0655] Typically, information within or from any and/or all or a portion of the queries QQnm (53) may be incorporated into the corresponding ones of the target resources P11 . . . Pnm (349) and/or the corresponding ones of the optional entity bodies EH11 . . . EHnm (347), and may in certain instances depend upon the method M11 . . . Mnm (348).
[0656] However, information that may be used for opening the connections OC11 . . . OCnm (323) and formulating the requests Q11 . . . Qnm (29) from the service and/or information requests IQ1 . . . IQn (28) may be derived from any and/or all or a portion of the user client requests QC11 . . . QCnu (280) accessible to the users U1 . . . Un (12) and/or the hidden client requests HCn1 . . . HCnh (281) hidden from the users U1 . . . Un (12), and/or a combination thereof, and/or may also have information and/or instructions to be utilized by the server PS (18) and/or ones of the clients C1 . . . Cn 916).
[0657] Alternatively information from the alternate request links QL11 . . . QLna (203), and/or the server request links UL11 . . . ULns (204), and/or the additional request links SL11 . . . SLnw (71), and/or a combination thereof, may be used by the server PS (18) and/or ones of the clients C1 . . . Cn (16) to formulate the requests Q11 . . . Qnm (29).
[0658] There may be m different or same ones of the requests Qn1 . . . Qnm (29) from the client Cn (16) at any time, and n×m different and/or same ones of the requests Q11 . . . Qnm (29) of the same and/or different ones of the servers S1 . . . Sz 920) present on the network 24 at any time.
[0659] The queries QQn1 . . . QQnm (53) may each be different, one from the other, or the same. The queries QSn1 . . . QSnu (288) accessible to the user Un (12) may each be different, one from the other, or the same. The hidden queries QHn1 . . . QHnh (290) may each be different, one from the other, or the same. The number of the queries QQn1 . . . QQnm (53) “m” may be substantially the sum of the queries QSn1 . . . QSnu (288) accessible to the user Un 912) and the hidden queries QHn1 . . . QHnh (290), i.e., m=u+h.
[0660] There may be m different or same ones of the queries QQn1 . . . QQnm (53) corresponding to the requests Qn1 . . . Qnm (29) from the client Cn (16) at any time, and n×m different and/or same ones of the queries QQ11 . . . QQnm (53) corresponding to the requests Q11 . . . Qnm (29) of the same and/or different ones of the servers S1 . . . Sz (20) present on the network 24 at any time.
[0661] The server addresses AQn1 . . . AQnm (54) may each be different, one from the other, or the same. The server addresses An1 . . . Anu (265) accessible to the user Un (12) may each be different, one from the other, or the same. The hidden server addresses AHn1 . . . AHnh (291) may each be different, one from the other, or the same. The number of the server addresses AQn1 . . . AQnm (54) “m” may be substantially the sum of the server addresses An1 . . . Anu (265) accessible to the user Un 912) and the hidden server addresses AHn1 . . . AHnh (291), i.e., m=u+h.
[0662] There may be m different or same ones of the server addresses AQn1 . . . AQnm (54) corresponding to the request Qn1 . . . Qnm 929) from the client Cn 916) at any time, and n×m different and/or same ones of the server addresses AQ11 . . . AQnm (54) corresponding to the requests Q11 . . . Qnm (29) of the same and/or different ones of the servers S1 . . . Sz (20) present on the network 24 at any time.
[0663] The optional instructions VJn1 . . . VJnk (52) may each be different, one from the other, or the same. The optional instructions Vn1 . . . Vnv (289) accessible to the user Un (12) may each be different, one from the other, or the same. The optional hidden instructions Hn1 . . . Hni (292) may each be different, one form the other, or the same. The number of the optional instructions VJn1 . . . VJnk (52) “k” may be substantially the sum of the optional instructions Vn1 . . . Vnv (289) accessible to the user Un 912) and The optional hidden instructions Hn1 . . . Hni (292), i.e., k=v+i.
[0664] There may be m×k different or same ones of the optional instructions VJn1 . . . VJnk (52) corresponding to the requests Qn1 . . . Qnm (29) from the client Cn (16) at any time, and n×m×k different and/or same ones of the optional instructions VJ11 . . . VJnk (52) corresponding to the requests Q11 . . . Qnm 929) of the same and/or different ones of the servers S1 . . . Sz (20) present on the network 24 at any time.
[0665] The requests Q11 . . . Qnm (29) of the servers S1 . . . Sz 920) may be made at the same and/or different times. One or more of the requests Q11 . . . Qnm (29) may be made of each of the servers S1 . . . Sz (20) by the same/and or different ones of the clients C1 . . . Cn 916) and/or the server PS (18) at the same and/or different times.
[0666] The server PS (18) and/or the client Cn (16) may make one or more of the requests Qn1 . . . Qnm (29) of the same and/or different ones of the servers S1 . . . Sz 920), in accordance with the designation scheme corresponding to the corresponding ones of the server designations Sn1 . . . Snm (30), in order to fulfill the services and/or information requirements of the user Un (12).
K. REPLIES FROM THE SERVERS
[0667] Each of the servers S1 . . . Sz 920) communicated therewith replies to the server PS (18) and/or the clients C1 . . . Cn (16), in accordance with the designation scheme which designates the servers S1 . . . Sz 920) being communicated with corresponding to the requests Q11.. . Qnm (29) as the corresponding server designations S11 . . . Snm 930), and communicates the corresponding responses R11 . . . Rnm (32), associated with the requests Q11 . . . Qnm (29), to the server PS (18) and/or the clients C1 . . . Cn (16) making the requests Q11 . . . Qnm (29).
[0668] Now, ones of the servers S1 . . . Sz 920) having been contacted by the server PS (18) and/or the clients C1 . . . Cn 916) and the connections OC11 . . . OCnm (323) opened therewith, corresponding to the requests Q11 . . . Qnm 929), according to the server designations S11 . . . Snm (30) at the corresponding server addresses A11 . . . Anu (265) at the corresponding ports W11 . . . Wnm (343) reply to the server PS (18) and/or the contacting clients C1 . . . Cn 916) with the corresponding responses R11 . . . Rnm (32).
[0669] A particular one of the responses Rn1 . . . Rnm (32), hereinafter designated as the response Rnm (32), corresponding to one response within the responses Rn1 . . . Rnm (32), the response Rnm (32) corresponding to the request Qnm 929), and the responses Rn1 . . . Rnm (32) corresponding to the requests Qn1 . . . Qnm (29), is shown schematically in FIG. 104 .
[0670] Now, the response Rnm (32) may have a corresponding response header line LRnm (351), corresponding optional response header fields JRn1 . . . JRnt (352), and a corresponding optional entity body RHnm (353). The optional entity body RHnm (353) typically has links, and/or descriptions, and/or the information. The request header line LRnm (351) may have a corresponding protocol BRnm (354), a corresponding status SRnm (355), and a corresponding status explanation SEnm (356).
[0671] Ones of the connection may be closed after ones of the responses R11 . . . Rnm (32) are communicated to the PS (18) and/or to the requesting corresponding ones of the clients C1 . . . Cn (16). Again, the Timeout per Search Engine 329 is considered to be substantially the maximum time for the server PS (18) and/or the particular client Cn (16) making the requests Qn1 . . . Qnm (29) to wait for each of the responses Rn1 . . . Rnm (32) from certain ones of the servers S1 . . . Sz (20), in accordance with the designated scheme which designates the certain ones of the servers S1 . . . Sz (20) to be communicated with corresponding to the requests Q11 . . . Qnm (29) as the corresponding server designations S11 . . . Snm (30).
[0672] If certain ones of the servers S1 . . . Sz (20) do not open connections OC11 . . . OCnm (323) with and/or communicate the responses R11 . . . Rnm (32) to the server PS (18) and/or the clients C1 . . . Cn (16), and/or if certain ones of the servers S1 . . . Sz (20) do not communicate the responses R11 . . . Rnm (32) to the server PS (18) and/or the client C1 . . . Cn (16) once connections OC11 . . . OCnm (323) therewith may have opened, corresponding to the requests Q11 . . . Qnm (29), according to the server designations S11 . . . Snm 930), within the timeout set by the Timeout per Search Engine 329, the certain ones of requests Qn1 . . . Qnm (29) of such nonresponding ones of the servers S1 . . . Sz (20) may then be cancelled by the server PS (18) and/or the clients C1 . . . Cn (16). Information about such ones of the nonresponding ones of the servers S1 . . . Sz (20) may then be communicated from the server PS (18) and/or the clients C1 . . . Cn (16) through the corresponding ones of the user interfaces I1 . . . In (14) to the corresponding ones of the users U1 . . . Un (12), according to the server designations S11 . . . Snm (30) corresponding to the certain ones of requests Qn1 . . . Qnm (29) of such nonresponding ones of the servers S1 . . . Sz (20).
[0673] In certain instances, the server PS (18) and/or certain ones of the clients C1 . . . Cn (16) may contact certain ones of the servers S1 . . . Sz (20) and open the connections OC11 . . . OCnm (323) therewith, corresponding to the requests Q11 . . . Qnm (29), according to the server designations S11 . . . Snm (30), one or more additional times, in order to satisfy the needs of the users U1 . . . Un (12), and/or certain requirements within the optional instructions VJn1 . . . VJnk (52), such as, for example, the URL's per Search Engine 330, and/or as a result of certain information communicated to the PS (18) and/or certain ones of the clients C1 . . . Cn 916) within the responses R11 . . . Rnm (32).
[0674] If, for example, less links, and/or descriptions, and/or prices/values, and/or images are returned within certain ones of the responses R11 . . . Rnm (32), which may be considered to be first ones of the responses R11 . . . Rnm (32), than are requested by certain ones of the users U1 . . . Un (12) within certain ones of the URL's per Search Engine 330, the server PS (18) and/or certain ones of the clients C1 . . . Cn (16) may contact certain ones of the servers S1 . . . Sz (20), open the connections OC11 . . . OCnm (323) therewith, and make additional ones of the requests Q11 . . . Qnm (29), according to the server designations S11 . . . Snm (30), one or more additional times, in order to satisfy the needs of the users U1 . . . Un (12). The links, and/or the descriptions, and/or the images returned within and/or parsed from additional ones of the responses R11 . . . Rnm (32) to the additional ones of the requests Q11 . . . Qnm 929) may then be appended to the corresponding ones of the links, and/or the corresponding ones of the descriptions, and/or the corresponding ones of the images returned within and parsed form the first ones of the responses R11 . . . Rnm (32)
[0675] The servers S1 . . . Sz (20) communicate the responses R11 . . . Rnm (32) to the requests Q11 . . . Qnm (29) to the server PS (18) and/or specified ones of the clients C1 . . . Cn (16), in accordance with the designation scheme corresponding to the corresponding ones of the server designations S11 . . . Snm (30). Alternatively, and/or additionally, in certain instances, certain ones of the servers S1 . . . Sz (20), corresponding to certain ones of the server designations S11 . . . Snm (30), may request additional information of the server PS (18) and/or specific ones of the clients C1 . . . Cn (16), prior to communicating the responses R11 . . . Rnm (32) to the requests Q11 . . . Qnm (29). Upon receiving such additional information from the server PS (18) and/or the specific ones of the clients C1 . . . Cn (16), the certain ones of the servers S1 . . . Sz (20), corresponding to the certain ones of the server designations S11 . . . Snm (30), may then communicate the responses R11 . . . Rnm (32) to the requests Q11 . . . Qnm (29) to the server PS (18) and/or the specific ones of the clients C1 . . . Cn (16).
[0676] In certain such instances, in more detail, the server PS (18) and/or certain ones of the clients C1 . . . Cn (16) may contact certain ones of the servers S1 . . . Sz (20) and open the connections OC11 . . . OCnm (323) therewith, corresponding to the requests Q11 . . . Qnm (29), according to the server designations S11 . . . Snm (30), one or more additional times, as a result of certain information communicated to the PS (18) and/or certain ones of the clients C1 . . . Cn (16) within the responses R11 . . . Rnm (32), such as, for example, information obtained from and/or parsed from the responses R11 . . . Rnm (32). This information is typically within certain ones of the response header fields JR11 . . . JRnt (352), but may also be within the corresponding optional entity bodies RH11 . . . RHnm (353) and/or the corresponding response header lines LR11 . . . LRnm (351).
[0677] Now, in such certain instances, the certain ones of the servers S1 . . . Sz 920) request the information from the server PS (18) and/or certain ones of the clients C1 . . . Cn (16), prior to communicating the responses R11 . . . Rnm (32) to the server PS (18) and/or the certain ones of the clients C1 . . . Cn (16). The server PS (18) and/or the certain ones of the clients C1 . . . Cn (16) being requested such information may then respond to the requests for such information, by communicating the requested information to the ones of the requesting servers S1 . . . Sz (20). Upon receipt of the requested information at the ones of the requesting servers S1 . . . Sz (20), the requesting ones of the servers S1 . . . Sz (20) reply to the server PS (18) and/or the certain ones of the clients C1 . . . Cn (16) with the responses R11 . . . Rnm (32). Such requests for information from the servers S1 . . . Sz (20) may occur not at all, and/or one or more times.
L. PARSING, PROCESSING, FORMATTING, SORTING, GROUPING, AND ORGANIZING RESPONSES INTO SERVICE AND/OR INFORMATION RESPONSES
[0678] A particular one of the optional entity bodies RH11 . . . RHnm (353), designated as the entity body RHnm (353), of a particular one of the responses R11 . . . Rnm (32), designated as the response Rnm (32), may have optional response individual information groups LSnm1 . . . LSnmr (360) and optional information LLnm (361), as shown in FIG. 105 .
[0679] Each of the optional response individual information groups LSnm1 . . . LSnmr (360) may have and/or be parsed into corresponding optional response links LKnm1 . . . LKnmr (363), and/or corresponding optional response descriptions DKnm1 . . . DKnmr (363), and/or corresponding optional response prices/values PKnm1 . . . PKnmr (364), and/or corresponding optional response images IKnm1 . . . IKnmr (365), as shown in FIG. 105 .
[0680] The optional response links LKnm1 . . . LKnmr (362), the corresponding optional response descriptions DKnm1 . . . DKnmr (363), the corresponding optional response prices/values PKnm1 . . . PKnmr (364), and the corresponding optional response image IKnm1 . . . IKnmr (365), corresponding to the optional response individual information groups LSnm1 . . . LSnmr (360) are typically associated correspondingly one with the other.
[0681] The optional response link LKnm1 (362), the corresponding optional response description DKnm1 (363), the corresponding optional response price/value PKnm1 (364), and the corresponding optional response image IKnm1 (365), corresponding to the optional response individual information group LSnm1 (360) are typically associated correspondingly one with the other. The optional response link LKnm2 (362), the corresponding optional response description DKnm2 (363), the corresponding optional response price/value PKnm2 (364), and the corresponding optional response image IKnm2 (365), corresponding to the optional response individual information group LSnm2 (360) are typically associated correspondingly one with the other, and so on. The optional response link LKnmr (362), the corresponding optional response description DKnmr (363), the corresponding optional response price/value PKnmr (364), and the corresponding optional response image IKnmr (365), corresponding to the optional response individual information group LSnmr (360) are, thus, typically associated correspondingly one with the other.
[0682] The optional information LInm (361) may have additional links, and/or additional descriptions, and/or additional images, and/or prices/values, and/or other information, and/or services, and/or media, all and/or a portion of which may be used and/or discarded by the server PS (18) and/or the clients C1 . . . Cn (16). The optional information LInm (361) is typically filtered from the optional entity body RHnm (353) and discarded, and/or other unwanted information and/or media is also typically filtered from the response Rnm (32), and/or the optional entity body RHnm (353), and discarded.
[0683] The optional response individual information groups LSnm1 . . . LSnmr (360) are typically parsed and/or processed and/or formatted from the entity body RHnm (353) of the response Rnm (32), and/or parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into the addressable individual information groups LGnm1 . . . LGnmr (80) of the addressable response information group RGnm (57), corresponding associated with the response Rnm (32), as shown in FIGS. 106 and 107 .
[0684] FIG. 106 shows the addressable response information group RGnm (57) having the addressable individual information groups LGnm1 . . . LGnmr (80) parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into the addressable response information group RGnm (57) from the optional entity body RHnm (353) of FIG. 105 .
[0685] FIG. 107 shows a particular one of the optional response individual information groups LSnm1 . . . LSnmr (360), designated as the optional response individual information group LSnmr (360), parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into a particular one of the addressable individual information groups LGnm1 . . . LGnmr (80), designated as the addressable individual information group LGnmr (80).
[0686] The addressable individual information groups LGnm1 . . . LGnmr (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 LGnm1 . . . lGnmr (80) are incorporated into the addressable response information groups RGn1 . . . RGnm (57) from the responses Rn1 . . . Rnm (32).
[0687] Alternatively and/or additionally the addressable individual information groups LGnm1 . . . LGnmr (80) may be incorporated into the addressable response information groups RGn1 . . . RGnm (57) from the responses Rn1 . . . Rnm (32) in an as-is condition and/or in raw form.
[0688] The optional response links LKnm1 . . . LKnmr (362) are typically parsed, and/or processed, and/or formatted into the corresponding optional links LDnm1 . . . LDnmr (82). The optional response description DKnm1 . . . DKnmr (363) are typically parsed, and/or processed, and/or formatted into the optional descriptions DDnm1 . . . DDnmr (83). The optional response prices/values PKnm1 . . . PKnmr (364) are typically parsed, and/or processed, and/or formatted into the corresponding optional prices/values PDnm1 . . . PDnmr (84). The optional response images IKnm1 . . . IKnmr (365) are typically parsed, and/or processed, and/or formatted into the corresponding optional images IDnm1 . . . IDnmr (85).
[0689] Each of the optional links LDn1 . . . LDnr (82) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other. Alternatively and/or additionally the optional links LDnm1 . . . LDnmr (82) may be retained in an as-is condition and/or in raw form.
[0690] Each of the optional descriptions DDnm1 . . . DDnmr (83) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other. Alternatively and/or additionally the optional links optional descriptions DDnm1 . . . DDnmr (83) may be retained in an as-is condition and/or in raw form.
[0691] Each of the optional prices/values PDnm1 . . . PDnmr (84) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other. Alternatively and/or additionally the optional prices/values PDnm1 . . . PDnmr (84) may be retained in an as-is condition and/or in raw form.
[0692] Each of the optional images IDnm1 . . . IDnmr (85) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other. Alternatively and/or additionally the optional images IDnm1 . . . IDnmr (85) may be retained in an as-is condition and/or in raw form.
[0693] The optional links LDnm1 . . . LDnmr (82), and/or the optional descriptions DDnm1 . . . DDnmr (83), and/or the optional prices/values PDnm1 . . . PDnmr (84), and/or the optional images IDnm1 . . . IDnmr (85), correspondingly associated with the response Rnm (32), may additionally and/or alternatively be parsed individually and/or separately, and incorporated into the addressable response information group RGnm (57) from the optional entity body RHnm (353), as shown in FIG. 108 .
[0694] The response header line LRnm (351) and/or the optional response header fields JRn1 . . . JRnt (352) may also have information, which the serve PS (18) and/or the clients C1 . . . Cn (16) may use.
[0695] The optional information LLnm (361) and/or certain information and/or media within the response Rnm (32), particularly within the optional entity body RHnm (353), may be optionally used by the server PS (18) and/or the clients C1 . . . Cn (16), and/or optionally incorporated into the addressable response information group RGnm (57).
[0696] Each of the optional response individual information groups LSnm1 . . . LSnmr (360) from each of the responses Rn1 . . . Rnm (32) may be compared one with the other, and duplicate ones of the of the optional response individual information groups LSnm1 . . . LSnmr (360) may be discarded.
[0697] Alternatively and/or additionally, each of the optional addressable individual information groups LGn11 . . . LGnmr (80) from each of the addressable response information groups RGn1 . . . RGnm (57) may be compared one with the other, and duplicate ones of the optional addressable individual information groups LGn11 . . . LGnmr (80) may be discarded.
[0698] Each of the optional response individual information groups LS111 . . . LSnmr (360) and/or portions thereof from the entity bodies RH11 . . . RHnm (353) of the responses R11 . . . Rnm (32) may also be optionally compared one with the other, and duplicate ones of the of the optional response individual information groups LS111 . . . LSnmr (360) may be optionally discarded.
[0699] Alternatively and/or additionally, each of the optional links LKn11 . . . LKnmr (362), and/or the optional descriptions DKn11 . . . DKnmr (363), and/or the optional prices/values PKnm1 . . . PKnmr (364), and/or the optional images IKn11 . . . IKnmr (365), from each of the responses Rn1 . . . Rnm (32) may be compared one with the other of like kind, and duplicate ones of the optional links LKn11 . . . LKnmr (362), and/or the optional descriptions DKn11 . . . DKnmr (363), and/or the optional prices/values PKnm1 . . . PKnmr (365), and/or the optional images IKn11 . . . IKnmr (365), and/or a combination thereof may be discarded.
[0700] Alternatively and/or additionally, each of the optional links LDn11 . . . LDnmr (82), and/or the optional descriptions DDn11 . . . DDnmr (83), and/or the optional prices/values PDnm1 . . . PDnmr (84), and/or the optional images IDn11 . . . IDnmr (85) from each of the addressable response information groups RGn1 . . . RGnm (57) may be compared one with the other of like kind, and duplicate ones of the optional links LDn11 . . . LDnmr (82), and/or the optional descriptions DDn11 . . . DDnmr (83), and/or the optional prices/values PDnm1 . . . PDnmr (84), and/or the optional images IDn11 . . . IDnmr (85), and/or a combination thereof may be discarded.
[0701] The optional links LKn11 . . . LKnmr (362) are typically compared one with the other, and duplicate ones of the corresponding optional links LKn11 . . . LKnmr (362), and/or the corresponding optional descriptions DKn11 . . . DKnmr (363), and/or the corresponding optional images IKn11 . . . IKnmr (365), and/or the corresponding optional prices/values PKnm1 . . . PKnmr (364) are discarded, leaving only one of any ones of the duplicate optional links LKn11 . . . LKnmr (362) and/or the corresponding optional descriptions DKn11 . . . DKnmr (363), and/or the corresponding optional images IKn11 . . . IKnmr (365), and/or the optional prices/values PKnm1 . . . PKnmr (364) remaining.
[0702] The optional prices/values PDnm1 . . . PDnmr (84) and/or the corresponding optional links LDn11 . . . LDnmr (82) and/or the corresponding optional description DDn11 . . . DDnmr (83), and/or the corresponding optional images IDn11 . . . IDnmr (85) may be sorted with respect to the optional prices/values PDnm1 . . . PDnmr (84), in accordance with sorting criteria in the optional instructions VJn1 . . . VJnk (52) and/or in accordance with default criteria resident within the server PS (18) and/or the client Cn (16).
[0703] The optional links LDn11 . . . LDnmr (82), and/or the corresponding optional descriptions DDn11 . . . DDnmr (83), and/or the corresponding optional prices/values PDnm1 . . . PDnmr (84), and/or the corresponding optional images IDn11 . . . IDnmr (85) may be sorted, for example, in ascending order with respect to the optional prices/values PDnm1 . . . PDnmr (84) having the lowest price therein being presented to the user Un (12) at the user interface In (14) first and the highest price therein last.
[0704] Alternatively and/or additionally, the optional links LDn11 . . . LDnmr (82), and/or the corresponding optional descriptions DDn11 . . . DDnmr (83), and/or the corresponding optional prices/values PDnm1 . . . PDnmr (84), and/or the corresponding optional images IDn11 . . . IDnmr (85) may be sorted, for example, in ascending or descending alphabetical order with respect to the optional links LDn11 . . . LDnmr (82) and/or the corresponding optional descriptions DDn11 . . . DDnmr (83) being presented to the user Un (12) at the user interface In (14).
[0705] Other sorting criteria may be used for the optional links LDn11 . . . LDnmr (82), and/or the optional descriptions DDn11 . . . DDnmr (83), and/or the optional prices/values PDnm1 . . . PDnmr (84), and/or the optional images IDn11 . . . IDnmr (85), and may depend upon needs of the user Un (12). The sorting criteria may be determined by the user Un (12).
[0706] Sorting criteria gives the user Un 912) the ability to formulate how information is presented to the user Un (12) at the user interface In (14), and may be incorporated into the optional instructions VJn1 . . . VJnk (52), which may be entered into the user interface In (14) through the user input UIn (25) by the user Un (12). The sorting criteria may additionally and/or alternatively be resident within the server PS (18) and/or the client Cn (16).
[0707] Now again, the labelled individual information group LLnzu (86) associated with the addressable query information group GInz (63) has the optional group identifier GLnc (87), the optional query link identifier LNncu (88), the optional resource location identifier SUnw (89), the optional server and/or query identifier SInm (90), and/or the optional server link identifier LXnmr (91) appended to the addressable individual information group LGnmr (80), as shown in FIG. 68 .
[0708] FIGS. 109 and 110 show typical ones of the addressable query information group GInz (63), based upon certain sorting and/or grouping criteria, having the labelled individual information groups LLnz1 . . . LLnzu (86), the optional database labelled individual information groups RLnz1 . . . RLnzx (92), the optional query description QTnz (93), the optional server descriptions and/or links STnz1 . . . STnzf (94), and the optional advertisements and/or links LTnz1 . . . LTnzt (95) incorporated into certain typical ones of the typical service and/or information response forms ISn (39) of FIGS. 27A–52C , inclusive.
[0709] 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 C1 . . . Cn (16), then, are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information from the same and/or different ones of the servers S1 . . . Sz (20), and/or the optional servers SO1 . . . SOp (22), and/or the clients C1 . . . Cn 916), 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 service and/or information into the user responses UR1 . . . URn (37) for delivery to the user interfaces I1 . . . In (14) and use by the users U1 . . . Un (12).
[0710] 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 C1 . . . Cn (16), then, are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating service and/or information from the same and/or different ones of each of the optional response individual information groups LS111 . . . LSnmr ((360), and/or the optional response links LK111 . . . LKnmr (362), and/or the optional response descriptions DK111 . . . DKnmr (363), and/or the optional response prices/values PK111 . . . PKnmr (364), and/or the optional response images IKnm1 . . . IKnmr (365) from the entity bodies RH11 . . . RHnm (353) of the responses R11 . . . Rnm (32), having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information into the user responses UR1 . . . URn (37) for delivery to the user interfaces I1 . . . In (14) and use by the users U1 . . . Un (12).
M. ADDITIONAL FEATURES AND/OR OTHER CONSIDERATIONS
[0711] 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 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 be capable of searching search engines and/or other sites substantially simultaneously and on-the-fly.
[0712] The client-server multitasking system and process are 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 form the servers and/or the clients into information and/or services responses, and communicating the service and/or information responses to the requestors and/or users substantially simultaneously. The requestors and/or the users may make substantially simultaneous service and/or information requests of servers and clients, using the same and/or different queries, and/or the same and/or different instructions. The same and/or different uniform resource locators, target resource, and/or paths may be used.
[0713] The client-server multitasking system and process are capable of making multiple substantially simultaneous same and/or different requests of the 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.
[0714] The client-server multitasking system and process are also capable of sorting, grouping, and/or organizing results form 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 are also capable of building a client-server multitasking system search engine and/or database from responses returned form the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof, are capable of being searched and/or queried, querying sites referenced in the client-server multitasking system search engine and/or database, and updating information and/or services stored therein.
[0715] 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.
[0716] A requestor and/or user is capable of making substantially multiple simultaneous same and/or different requests of the same and/or different servers. The client server-multitasking system and process are capable of organizing responses from the servers into service and/or information responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously, and on-the-fly.
[0717] The requestors and/or users are capable of making substantially simultaneously 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 are capable of retrieving substantially multiple simultaneous services and/or information having the same and/or different criteria form 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.
[0718] 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. 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 marked value.
[0719] The client-server multitasking system and process are 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.
[0720] The client-server multitasking system and process are 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 location 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 are capable of storing the information and/or services retrieved from 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 is also capable of being queried either directly and/or in combination with the substantially simultaneous searching, using the same and/or different queries of the same and/of different search engines, sites, servers, and/or databases. The client-server multitasking search engine and/or database are 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 the client-server multitasking search engine and/or database.
[0721] The client-server multitasking system and process are 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.
[0722] 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.
[0723] The client-server multitasking system and process are also capable of sorting, grouping, and/or organizing results from the servers, search engines, and/or sites, in accordance with instructions from the requestors and/or the users, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system and process are also capable of drilling down and/or up to different levels within the search engines, sites, and/or servers being queried.
[0724] 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.
[0725] The client-server multitasking system and process are capable of incorporating information and/or services into a variety of user interfaces at different location sin the user interfaces, grouping, and/or organizing the information and/or services, and optionally eliminating duplicate information and/or services.
[0726] 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 into the information and/or services to be delivered to the user interfaces. The requestor and/or the user may place order, such as purchases, and/or other types of orders, payments, confirmations thereof, and/or combinations thereof, either directly and/or through servers and/or sites on the network.
[0727] 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 sits, 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.
[0728] 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 from 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 with the substantially simultaneous multiple same and/or different searches and/or queries of the same and/or different servers on the network. Information in the client-server multitasking system search engine and/or database are also searchable and/or retrievable, and are capable of being incorporated into the service and/or information responses delivered to 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 in the client-server multitasking system search engine and/or database, and updating the service and/or information to be stored and/or stored in the client-server multitasking system search engine and/or database.
[0729] 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 from 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 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 are capable of building a client-server multitasking system search engine and/or database from responses returned from the servers, search engines, and/or sites being queries and/or searched, and/or having requests made thereof, is capable of being searched and/or queried, querying sites referenced in the client-server multitasking system search engine and/or database, and updating information and/or services stored therein.
[0730] The client-server multitasking system and process are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating service and/or information from 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 into user responses for delivery to and use by the requestors and/or users.
[0731] 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 C1 . . . Cn 916), then, are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information from the same and/or different ones of the servers S1 . . . Sz (20), and/or the optional servers SO1 . . . SOp (22), and/or the client C1 . . . Cn 916), 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 into the user responses UR1 . . . URn (37), for delivery to the user interfaces I1 . . . In 914) and use by the users U1 . . . Un (12).
[0732] The client-server multitasking system 10 of the preset invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process, the user interfaces I1 . . . In 914), and/or the clients C1 . . . Cn (16), and/or the server PS (18), and/or the servers S1 . . . Sz (20), and/or the optional servers SO1 . . . SOp (22) may be constructed of hardware, firmware, software, machines, and/or operating systems, and/or combinations thereof, and/or other suitable means, and/or other components and/or systems, and/or combinations thereof. Such hardware, firmware, software, machines, and/or operating systems, and/or combinations thereof, other components and/or systems, and/or other suitable means, and/or combinations thereof may have therein and/or be resident therein, but are not limited to computer components and/or systems, television and/or telecommunications components and/or systems, merger of television and computer systems, and/or merger of television and/or computer and/or telecommunications systems, networks, simulators, interactive technologies and/or systems, cybernetics and/or cybernetic systems, and/or combinations thereof.
[0733] The clients C1 . . . Cn 916), the server PS (18), the servers S1 . . . Sz (20), and/or the optional servers SO1 . . . SOp (22) may be search engines, and/or sites, and/or servers, and/or clients, and/or URL's, and/or databases, and/or locations on the network, and/or other suitable components and/or systems, and/or other suitable means, and/or combinations thereof, which may be capable of communicating on the network 24. The scope 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 search engines, and/or sites, and/or servers, and/or clients, and/or URL's, and/or databases, and/or locations on the network, and/or other suitable components and/or systems, and/or other suitable means, and/or combinations thereof, which may be capable of communicating on the network 24, as it is recognized that other components, systems, technologies, and/or operating systems exist and/or emerge that may make use of the benefits of the present invention, and are either on the horizon and/or are recognized to be forthcoming.
[0734] The client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process, the user interfaces I1 . . . In 914), and/or the clients C1 . . . Cn (16), and/or the server PS (18), and/or the servers S1 . . . Sz (20), and/or the optional servers SO1 . . . SOp (22), may then be hardware, firmware, software, and/or machines, and or operating systems, and/or other suitable means, and/or combinations thereof, and may have and/or be resident within general purpose computers, special purpose computers, televisions, computer-television combinations, telecommunications systems, networks, mergers of computer and/or television technology and/or telecommunications technology and/or network technology, media, film, entertainment, interactive technologies and/or systems, cybernetics and/or cybernetic systems and/or technology, components, and/or systems, and/or other suitable means, and/or combinations thereof, and may be integrated one with the other and/or with other components and/or systems of one another, and may each be substantially the same and/or different one from the other.
[0735] The client-server multitasking system 10 of the present invention, the client server multitasking process 99, and the multitasking process 104, which in itself is a process, the user interfaces I1 . . . In 914), and/or the clients C1 . . . Cn (16), and/or the server PS (18), and/or the servers S1 . . . Sz (20), and/or the optional servers SO1 . . . SOp (22) may each have the same and/or different hardware, firmware, software, and/or ones of operating systems, and/or other suitable means, and/or combinations thereof. The optional databases 41 and/or 42 may also be hardware, firmware, software, and/or machine based, and/or other suitable means, and/or combinations thereof, have the same and/or different ones of operating systems and/or combinations thereof, and may have memory components associated therewith.
[0736] 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 are networks, and local area networks. Such networks may be Earth based, satellite based, and/or space based, and/or other suitable means, and/or combinations thereof.
[0737] 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 components, systems, technologies, operating system and/or networks, as other components, systems, technologies, and/or operating systems exist and/or emerge that may make use of the benefits of the present invention, and are either on the horizon and/or are recognized to be forthcoming.
[0738] Determination as to whether the server PS (18) performs the multitasking process 104, and/or whether particular ones of the clients C1 . . . Cn (16) perform the multitasking process 104, may optionally be made at the particular ones of the clients C1 . . . Cn (16) and/or the server PS (18). Such determination may optionally be made by the users U1 . . . Un (12), and/or be based upon processing power, capabilities, and/or configurations of the particular ones of the clients C1 . . . Cn (16), the server PS (18), and the network 24 considerations (traffic, load, and/or other considerations).
[0739] The client-server multitasking search engine and/or database are 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 the client-server multitasking search engine and/or database.
[0740] 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 is capable of searching search engines and/or other sites substantially simultaneously and on-the-fly.
[0741] 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.
[0742] The client-server multitasking system and process are also capable of sorting, grouping, and/or organizing results from 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 of drilling down and/or up to different levels within the search engines, sites, and/or servers being queried.
[0743] Now again, the typical ones of the service and/or information entry request forms IE1 . . . IEn (38) at the user interfaces I1 . . . In (14) shown in FIGS. 5A , 5B, and 6–10 are typical examples of the service and/or information entry request forms IE1 . . . IEn (38) at the user interfaces I1 . . . In (14), a much larger variety of which is possible. Names and/or links and/or other information are incorporated in the typical ones of the service and/or information entry request forms IE1 . . . IEn (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 IE1 . . . IEn (38) and the names and/or links and/or information that are possible, and that may be incorporated into the service and/or information entry request forms IE1 . . . IEn (38) at the user interfaces I1 . . . In (14).
[0744] Now again, The typical ones of the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14) shown in FIGS. 11–26 are typical examples of the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14), a much larger variety of which is possible. Typical queries QQn1 . . . QQnm (53), typical server addresses AQn1 . . . AQnm (54), and typical optional instructions VJn1 . . . VJnk (52) in the typical ones of the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14) shown in FIGS. 11–26 are typical examples for illustrative purposes, and are not intended to limit the substantially infinite variety of the queries QQn1 . . . QQnm (53), the server addresses AQn1 . . . AQnm (54), and the optional instructions VJn1 . . . VJnk (52) that may be entered into the service and/or information entry request forms IE1 . . . IEn (38), to derive the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14). Likewise, names and/or links and/or other information are incorporated in the typical ones of the completed service and/or information entry request forms IF1 . . . IFn (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 IF1 . . . IFn (230) and the names and/or links and/or information that are possible, and that may be incorporated into the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14).
[0745] Now again, the typical ones of the user responses UR1 . . . URn (37), as typical service and/or information response forms IS1 . . . ISn (39) at the user interfaces I1 . . . In (14) shown in FIG. 27A–52C , inclusive, are typical examples of the user responses UR1 . . . URn (37), as typical service and/or information response forms IS1 . . . ISn (39) at the user interfaces I1 . . . In (14), a much larger variety of which is possible. FIGS. 27A–52C , inclusive, illustrate typical examples of typical ones of the user responses UR1 . . . URn (37), as typical service and/or information response forms IS1 . . . ISn (39) at the user interfaces I1 . . . In (14) to the typical queries typical queries QQn1 . . . QQnm (53), the typical ones of the server addresses AQn1 . . . AQnm (54), and the typical optional instructions VJn1 . . . VJnk (52) having been entered into the typical ones of the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In (14) shown in FIGS. 11–26 .
[0746] The typical examples of the typical ones of the user responses UR1 . . . URn (37), as typical service and/or information response forms IS1 . . . ISn (39) at the user interfaces I1 . . . In 914) are for illustrative purposes, and are not intended to limit the substantially infinite variety of the user responses UR1 . . . URn (37), as the service and/or information response forms IS1 . . . ISn (39) at the user interfaces I1 . . . In (14), the queries QQn1 . . . QQnm (53), the server addresses AQn1 . . . AQnm (54), and the optional instructions VJn1 . . . VJnk (52) that may be entered into the service and/or information entry request forms IE1 . . . IEn (38), to derive the to the completed service and/or information entry request forms IF1 . . . IFn (230), and which result in the user responses UR1 . . . URn (37), as the service and/or information response forms IS1 . . . ISn (39) at the user interfaces I1 . . . In (14). Likewise, names and/or links and/or other information are incorporated into the typical ones of the user responses UR1 . . . URn (37), as the service and/or information response forms IS1 . . . ISn (39) at the user interfaces I1 . . . In 914), shown in FIGS. 27A–52C , inclusive, for illustrative purposes, and are not intended to limit the large variety of the user responses UR1 . . . URn (37), as the service and/or information response forms IS1 . . . ISn (39), at the user interfaces I1 . . . In (14), and the names and/or links and/or information that are possible, and that may be incorporated into the user responses UR1 . . . URn (37), as the service and/or information response forms IS1 . . . ISn (39) at the user interfaces I1 . . . In (14).
[0747] The server addresses AQn1 . . . AQnm (54), such as WebCrawler®, Altavista®, Lycos®, Infoseek®, Excite®, Yahoo®, LookSmart®, HotBot®, Dejanews®, Amazon®, Borders®, BarnesandNoble®, Google®, and/or others that may have been used herein are for illustrative purposes, to illustrate typical ones of the service and/or information entry request forms IE1 . . . IEn (38) at the user interfaces I1 . . . In (14) shown in FIGS. 5A , 5B, and 6–10, typical ones of the completed service and/or information entry request forms IF1 . . . IFn (230) at the user interfaces I1 . . . In 914) shown in FIG. 11–26 , and/or typical ones of the user responses UR1 . . . URn (37), as the service and/or information response forms IS1 . . . ISn (39) at the user interfaces I1 . . . In (14), shown in FIGS. 27A–52C , inclusive, and other examples used herein, are used merely to illustrate typical examples of the server addresses AQn1 . . . AQnm (54) and results therefrom that may be possible. The examples shown in FIGS. 5A , 5B, and 6–10, 11–26, and FIGS. 27A–52C , inclusive, and other examples used herein, are examples of the substantially infinite variety of the server addresses AQn1 . . . AQnm (54) that may be used with the client-server multitasking system 10 of the present invention and the results that may be obtained therefrom. The typical server addresses AQn1 . . . AQnm (54), such as WebCrawler®, Altavista®, Lycos®, Infoseek®, Excite®, Yahoo®, LookSmart®, HotBot®, Dejanews®, Amazon®, Borders®, BarnesandNoble®, Google®, and/or others that may have been used herein are for illustrative purposes only and are not intended to limit the scope of the client-server multitasking system 10 of the present invention.
[0748] It should also be obvious that the typical queries QQn1 . . . QQnm (53) used in the examples shown in FIGS. 5A , 5B, and 6–10, 11–26, and FIGS. 27A–52C , inclusive, and other examples used herein are for illustrative purposes and are merely typical examples of the substantially infinite variety of the queries QQn1 . . . QQnm (53) that may be used with the client-server multitasking system 10 of the present invention and the results that may be obtained therefrom, and are not intended to limit the substantially infinite variety of the queries QQn1 . . . QQnm (53) that may be used with the client-server multitasking system 10 of the present invention and the results that may be obtained therefrom. The typical queries QQn1 . . . QQnm (53) used in the examples shown in FIGS. 5A , 5B, and 6–10, 11–26, and FIGS. 27A–52C , inclusive, and other examples used herein are for illustrative purposes only and are not intended to limit the scope of the client-server multitasking system 10 of the present invention.
[0749] The typical labelled individual information groups LLn11 . . . LLnzu (86), the typical optional links LDnm1 . . . LDnmr (82), and/or the typical optional descriptions DDnm1 . . . DDnmr (83), and/or the typical optional prices/values PDnm1 . . . PDnmr (84), and/or the typical optional images IDnm1 . . . IDnmr (85), and/or advertisements and/or advertisement links, and/or URL's, and/or locations, and/or other items and/or objects shown in FIGS. 5A , 5B, and 6–10, 11–26, and FIGS. 27A–52C , inclusive, and other examples used herein are typical examples for illustrative purposes only and are not intended to limit the scope of the client-server multitasking system 10 of the present invention. A substantially infinite variety of the labelled individual information groups LLn11 . . . LLnzu (86), the optional links LDnm1 . . . LDnmr (82), and/or the optional descriptions DDnm1 . . . DDnmr (83), and/or the optional prices/values PDnm1 . . . PDnmr (84), and/or the optional images IDnm1 . . . IDnmr (85), and/or advertisement links and/or URL's, and/or locations, and/or other items and/or objects may result from the substantially infinite varieties and combinations of the queries QQn1 . . . QQnm (53) and the substantially infinite varieties and combinations of the server addresses AQn1 . . . AQnm (54) of the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process.
[0750] Likewise, the e typical grouping/sorting criteria shown herein in the examples is for illustrative purposes only and is not intended to limit the scope of the client-server multitasking system 10 of the present invention. It is possible to sort the responses within the service and/or information response, such as, for example, by category, query, group, page, order of importance, ascending and/or descending order, alphabetically and/or numerically, or other characteristics, as determined by the requestor, and/or the user, and/or the client-server multitasking system, or to combine the responses within the service and/or information response, such as, for example, interleaving the responses one with the other, such as, for example, by order of relevance or other parameters. The responses then are capable of being grouped by search criteria, server, order of importance, or by numerical factors such as value, price, or other numerical quantifier. The responses may be presentable, for example, in ascending or descending order in interleaved format, such as top ones, twos, threes, and so on, or presentable separately to the requestor and/or the user. The order may be order of importance or relevance related, or, for example, numerically valued, such as price or stock market value. A substantially infinite variety of results may be generated from the substantially infinite variety of grouping/sorting criteria possible with the client-server multitasking system 10 of the present invention.
[0751] A substantially infinite variety of URL's, links, locations, sites, servers, and/or clients, other items and/or objects may be used with the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process. Examples of URL's links, locations, sites, servers, and/or clients, other items and/or objects shown in FIGS. 5A , 5B, and 6–52C, inclusive, are typical examples of URL's, links, locations, sites, servers, and/or clients, other items and/or objects that may be of used with the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, and are used herein for illustrative purposes only, and are not intended to limit the scope of the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and/or the multitasking process 104.
[0752] A substantially infinite variety of advertisements and/or links may be used with the client-server multitasking system 10 of the present invention. The advertisements and/or links to such sites as Netscape® and/or “ABC NEWS”®, Disney®, Discovery®, Warner®, ABC®, Universal®, CBS®, NBC®, “TV Guide”®, NYtimes®, ESPN®, WSjournal®, CNN®, and/or other sites used in the examples shown in FIGS. 5A , 5B, and 6–10, 11–26, and FIGS. 27A–52C , inclusive, and other examples used herein are for illustrative purposes only and are not intended to limit the scope of the client-server multitasking system 10 of the present invention.
[0753] It should also be obvious that advertisements and/or links to such sites as Netscape® and/or “ABC News”®, and/or other sites that may be used herein are for illustrative purposes only and are not intended to limit the scope of the client-server multitasking system 10 of the present invention.
[0754] Each of the typical service and/or information entry request forms IEn at the user interface In , which the user Un may communicate other typical user input UIn thereinto, may also have news stories, which may be updated intermittently on a substantially routine basis.
[0755] The client-server multitasking system and process are also capable of performing as a multiple query search engine, which performs multiple queries of multiple sites, and performing as a single point of sale for purchasing multiple products from multiple sources.
[0756] Although the present invention has been described in considerable detail with reference to certain preferred versions thereof, other versions are possible. Therefore, the spirit and scope of the appended claims should not be limited to the description of the preferred versions contained herein.
Claims
What is claimed is:
1. A process for metasearching on a distributed network activated by a request executed by a user on a client device to request a metasearch engine to send a plurality of search queries to a plurality of search engines, the request specifying to which of the plurality of search engines each of the plurality of search queries specified in the request by the user is to be sent to, each of the plurality of search queries comprising a keyword phrase, each of the keyboard phrases comprising at least one keyword specified in the request by the user, at least two of the keyword phrases of the plurality of search queries being different from each other, comprising the steps of:
(a) receiving, at the metasearch engine, the request from the client device for the metasearch engine to send the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines;
(b) sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines, each as specified in the request executed by the user;
(c) receiving, at the metasearch engine, search results from the plurality of search engines in response to the plurality of search queries comprising the at least two keyword phrases sent to the plurality of search engines, wherein at least one of the received search results comprises information about at least one item that may be ordered;
(d) incorporating, by the metasearch engine, the received search results into at least two different display lists corresponding to the at least two different keyword phrases and
incorporating, by the metasearch engine, means for inputting at least one quantity of the at least one item that may be ordered into each of the at least two different display lists that comprise the at least one of the received search results comprising the information about the at least one item that may be ordered, the at least one quantity of the at least one item to be ordered to be input on the client device, wherein:
each different one of the at least two different display lists comprises the received search results in response to the plurality of search queries comprising a different one of the at least two keyword phrases,
each same one of the at least two different display lists comprises the received search results therein in response to the plurality of search queries comprising a same one of the at least two keyword phrases;
(e) incorporating, by the metasearch engine, the at least two different display lists of received search results into a response for communicating to the client device and incorporating, by the metasearch engine, into the response for communicating to the client device means for executing on the client device another request to be activated by the user for ordering the at least one quantity of the at least one item that may be ordered.
(f) communicating, by the metasearch engine, the response from the metasearch engine to the client device.
2. The process of claim 1, wherein the request executed by the user on the client device comprises a sorting order specified by the user that specifies the order of each of the search results to be returned in each of the at least tow different display lists, step (d) further comprises:
sorting, by the metasearch engine, the received search results in each of the at least two different display lists into the sorting order specified in the request executed by the user.
3. The process of claim 2, wherein the sorting order specified by the user on the client device comprises sorting the search results alphanumerically, the sorting comprises:
sorting, by the metasearch engine, the search results within each of the at least two different display lists into alphanumeric order.
4. The process of claim 3, wherein the alphanumerical order is from the group consisting of ascending and descending.
5. The process of claim 2, wherein the sorting order specified by the user on the client device comprises interleaving the search results, the sorting comprises:
sorting, by the metasearch engine, by interleaving the search results within each of the at least two different display lists by rank of the search results as received from each of the plurality of search engines and alternating each of the search results from each of the plurality of search engines from which the search results were received with each other.
6. The process of claim 1, wherein step (d) further comprises:
identifying, by the metasearch engine, the at least two different display lists with information that identifies which of the at least two different keyword phrases each of the at least two different display lists corresponds to.
7. The process of claim 6, wherein step (d) further comprises:
identifying, by the metasearch engine, each of the received search results with information that identifies which of the plurality of search engines the received search results were received from.
8. The process of claim 7, wherein step (d) further comprises:
identifying, by the metasearch engine, the rank of each of the received search results within each of the plurality of search engines.
9. The process of claim 1, further comprising the steps of:
(g) inputting on the client device, by the user, the at least one quantity of the at least one item to be ordered;
(h) activating the other request, by executing on the client device, by the user, the other request for the metasearch engine to order the at least one quantity of the at least one item;
(i) receiving, at the metasearch engine, the other request from the client device for the metasearch engine to order the at least one quantity of the at least one item;
(j) processing, by the metasearch engine, an order for the at least one quantity of the at least one item.
10. The process of claim 9, prior to activating the other request, by executing on the client device, by the user, the other request for the metasearch engine to order the at least one quantity of the at least one item, further comprising the steps of:
incorporating, by the metasearch engine, into another response for communicating to the client device means for executing on the client device yet another request to be activated by the user for previewing the order;
activating the yet other request, by executing on the client device, by the user, the yet other request for the metasearch engine to communicate, by the metasearch engine, to the client device a preview of the order;
receiving, at the metasearch engine, the yet other request from the client device for the metasearch engine to communicate to the client device the preview of the order;
communicating, by the metasearch engine, to the client device the preview of the order.
11. The process of claim 9, prior to activating the other request, by executing on the client device, by the user, the other request for the metasearch engine to order the at least one quantity of the at least one item, further comprising the steps of:
incorporating by the metasearch engine, into yet another response for communicating to the client device means for executing on the client device yet another additional request to be activated by the user for updating the order;
updating at the client device, by the user, the order; activating the yet other additional request, by executing on the client device, by the user, the yet other request for the metasearch engine to communicate, by the metasearch engine, to the client device the updated order;
receiving, at the metasearch engine, the yet other additional request from the client device for the metasearch engine to communicate to the client device the updated order;
communicating, by the metasearch engine, to the client device the updated order.
12. The process of claim 9, further comprising the step of:
(k) confirming, by the metasearch engine, the order.
13. The process of claim 9, further comprising the step of:
(k) confirming, by the metasearch engine, the order by e-mail.
14. The process of claim 9, further comprising the step of:
(k) placing, by the metasearch engine, the order with at least one server device on the distributed network and/or at least one third party for the at least one quantity of the at least one item..
15. The process of claim 9, further comprising the step of:
(k) placing, by the metasearch engine, the order with at least one server device on the distributed network and/or at least one third party for the at least one quantity of the at least one item by e-mail.
16. The process of claim 9, wherein the step of activating the other request, by executing on the client device, by the user, the other request for the metasearch engine to order the at least one quantity of the at least one item comprises
activating the other request, by executing on the client device, by the user, the other request for the metasearch engine to purchase the at least one quantity of the at least one item.
17. The process of claim 1, wherein the incorporating, by the metasearch engine, the means for inputting the at least one quantity of the at least one item that may be ordered into the each of the at least two different display lists that comprise the at least one of the receive search results comprising the information about the at least one item that may be ordered, of step (d) comprises:
appending, by the metasearch engine, at least one input element for inputting the at least one quantity of the at least one item that may be ordered to the at least one of the received search results comprising the information about the at least one item that may be ordered and
incorporating, by the metasearch engine, the appended at least one input element into the each of the at least two different display lists that comprise the at least one of the received search results comprising the information about the at least one item that may be ordered.
18. The process of claim 17, wherein the at least one input element comprises at least one text entry field for inputting the at least one quantity of the at least one item that may be ordered.
19. The process of claim 1, wherein the at least one item that may be ordered comprises at least two items that may be ordered and the incorporating, by the metasearch engine, of the received search results into the at least two different display lists corresponding to the at least two different keyword phrases comprises incorporating the at least two items that may be ordered into any one of the at least two different display lists, step (d) further comprises:
sorting, by the metasearch engine, the received search results into the any one of the at least two different display lists according to price of the at least two items that may be ordered.
20. The process of claim 19, wherein the request executed by the user on the client device comprises a sorting order specified by the user that specifies the order of each of the search results to be returned in each of the at least two different display lines, wherein the sorting order is selected from the group consisting of ascending price and descending price, step (d) further comprises:
sorting, by the metasearch engine, the received search results into the any one of the at least two different display lists into the sorting order specified in the request executed by the user according to the price of the at least two items that may be ordered.
21. The process of claim 1, wherein step (d) further comprises:
eliminating, by the metasearch engine, any duplicates of the received search results in any particular one of the at least two different display lists comprising the received search results corresponding to the same one of the at least two keyword phrases.
22. The process of claim 1, wherein step (e) further comprises:
incorporating, by the metasearch engine, into the response for communicating to the client device means for inputting on the client device, by the user, payment and/or shipping information.
23. The process of claim 1, wherein:
at least one of the at least two different display lists comprises the received search results therein in response to at least two of the plurality of search queries comprising a same one of the at least two keyword phrases.
24. The process of claim 1, wherein prior to sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines, step (b) further comprises:
opening connections, by the metasearch engine, substantially simultaneously with the plurality of search engines.
25. The process of claim 1, wherein step (b) further comprises:
opening connections, by the metasearch engine, substantially simultaneously with the plurality of search engines, and
sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases substantially simultaneously to the plurality of search engines.
26. The process of claim 1, wherein step (b) further comprises:
sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases substantially simultaneously to the plurality of search engines.
27. A system for metasearching on a distributed network activated by a request executed by a user on a client device to request a metasearch engine to send a plurality of search queries to a plurality of search engines, the request specifying to which of the plurality of search engines each of the plurality of search queries specified in the request by the user is to be sent to, each of the plurality of search queries comprising a keyword phrase, each of the keyword phrases comprising at least one keyword specified in the request by the user, at least two of the keyword phrases of the plurality of search queries being different from each other, comprising:
(a) means for receiving, at the metasearch engine, the request from the client device for the metasearch engine to send the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines;
(b) means for sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines, each as specified in the request executed by the user;
(c) means for receiving, at the metasearch engine, search results from the plurality of search engines in response to the plurality of search queries comprising the at least two keyword phrases sent to the plurality of search engines, wherein at least one of the received search results comprises information about at least one item that may be ordered;
(d) means for incorporating, by the metasearch engine, the received search results into at least two different display lists corresponding to the at least two different keyword phrases and
means for incorporating, by the metasearch engine, means for inputting at least one quantity of the at least one item that may be ordered into each of the at least two different display lists that comprise the at least one of the received search results comprising the information about the at least one item that may be ordered, the at least one quantity of the at least one item to be ordered to be input on the client device, wherein:
each different one of the at least two different display lists comprises the received search results in response to the plurality of search queries comprising a different one of the at least two keyword phrases, each same on of the at least two different display lists comprise the received search results therein in response to the plurality of search queries comprising a same one of the at least two keyword phrases;
(e) means for incorporating, by the metasearch engine, the at least two different display lists of received search results into a response for communicating to the client device and
means for incorporating, by the metasearch engine, into the response for communicating to the client device means for executing on the client device another request to be achieved by the user for ordering the at least one quantity of the at least one item that may be ordered.
(f) means for communicating, by the metasearch engine, the response from the metasearch engine to the client device.
28. The system of claim 27, wherein the means for incorporating, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases further comprises:
means for identifying, by the metasearch engine, the at least two different display lists with information that identifies which of the at least two different keyword phrases each of the at least two different display lists corresponds to.
29. The system of claim 28, wherein the means for incorporating, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases further comprises:
means for identifying, by the metasearch engine, each of the received search results with information that identifies which of the plurality of search engines the received search results were received from.
30. The system of claim 29, wherein the means for incorporating, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases further comprises:
means for identifying, by the metasearch engine, the rank of each of the received search results within each of the plurality of search engines.
31. The system of claim 27, wherein the request executed by the user on the client device comprises a sorting order specified by the user that specifies the order of each of the search results to be returned in each of the at least two different display lists, the means for incorporating, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases further comprises:
means for sorting, by the metasearch engine, the received search results in each of the at least two different display lists into the sorting order specified in the request executed by the user.
32. The system of claim 31, wherein the sorting order specified by the user on the client device comprises sorting the search results alphanumerically, the means for sorting comprises:
means for sorting, by the metasearch engine, the search results within each of the at least two different display lists into alphanumeric order.
33. The system of claim 27, further comprising:
(g) means for inputting on the client device, by the user, the at least one quantity of the at least one item to be ordered.
(h) means for activating the other request, by executing on the client device, by the user, the other request for the metasearch engine to order the at least one quantity of the at least one item;
(i) means for receiving, at the metasearch engine, the other request from the client device for the metasearch engine to order the at least one quantity of the at least one item;
(j) means for processing, by the metasearch engine, an order for the at least one quantity of the at least one item.
34. The system of claim 33, further comprising:
(k) means for placing, by the metasearch engine, the order with at least one server device on the distributed network and/or at least one third party for the at least one quantity of the at least one item.
35. The system of claim 27, wherein prior to the means for sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines, the system further comprises:
means for opening connections, by the metasearch engine, substantially simultaneously with the plurality of search engines.
36. The system of claim 35, wherein the means for sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines, each as specified in the request executed by the user further comprises:
means for sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases substantially simultaneously to the plurality of search engines.
37. The system of claim 27, wherein the means for incorporating, by the metasearch engine, the means for inputting the at least one quantity of the at least one item that may be ordered into the each of the at least two different display lists that comprise the at least one of the received search results comprising the information about the at least one item that may be ordered, of (d) comprises:
means for appending, by the metasearch engine, at least one input element for inputting the at least one quantity of the at least one item that may be ordered to the at least one of the received search results comprising the information about the at least one item that may be ordered and means for incorporating, by the metasearch engine, the appended at least one input element into the each of the at least two different display lists that comprise the at least one of the received search results comprising the information about the at least one item that may be ordered.
38. The system of claim 27, wherein the at least one item that may be order comprises at least two items that may be ordered and the means for incorporating, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases comprises means for incorporating the at least two items that may be ordered into any one of the at least two different display lists, (d) further comprises:
means for sorting, by the metasearch engine, the received search results into the any one of the at least two different display lists according to price of the at least two item that may be ordered.
39. The system of claim 27, wherein:
at least one of the at least two different display lists comprises the received search results therein in response to at least two of the plurality of search queries comprising a same one of the at least two keyword phrases.
40. The system of claim 27, wherein the means for sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines, each as specified in the request executed by the user further comprises:
means for sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases substantially simultaneously to the plurality of search engines.
41. A computer readable storage medium containing computer executable instructions for metasearching on a distributed network activated by a request executed by a user on a client device to request a metasearch engine to send a plurality of search queries to a plurality of search engines, the request specifying to which of the plurality of search engines each of the plurality of search queries specified in the request by the user is to be sent to, each of the plurality of search queries comprising a keyword phrase, each of the keyword phrases comprising at least one keyword specified in the request by the user, at least two of the keyword phrases of the plurality of search queries being different from each other, causing one or more computers to:
(a) receive, at the metasearch engine, the request from the client device for the metasearch engine to send the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines;
(b) send, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines, each as specified in the request executed by the user;
(c) receive, at the metasearch engine, search results from the plurality of search engines in response to the plurality of search queries comprising the at least two keyword phrases sent to the plurality of search engines, wherein at least one of the received search results comprises information about at least one item that may be ordered;
(d) incorporate, by the metasearch engine, the received search results into at least two different display lists corresponding to the at least two different keyword phrases and
incorporate, by the metasearch engine, means for inputting at least one quantity of the at least one item that may be ordered into each of the at least two different display lists that comprise the at least one of the received search results comprising the information about the at least one item that may be ordered, the at least one quantity of the at least one item to be ordered to be input on the client device, wherein:
each different one of the at least two different display lists comprises the received search results in response to the plurality of search queries comprising a different one of the at least two keyword phrases, each same one of the at least two different display lists comprises the received search results therein in response to the plurality of search queries comprising a same one of the at least two keyword phrases;
(e) incorporate, by the metasearch engine, the at least two different display lists of received search results into a response for communicating to the client device incorporate, by the metasearch engine, into the response for communicating to the client device means for executing on the client device another request to be activated by the user for ordering the at least one quantity of the at least one item that may be ordered;
(f) communicate, by the metasearch engine, the response from the metasearch engine to the client device.
42. The computer readable storage medium containing computer executable instructions of claim 41, further causing one or more computers to:
incorporate, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases and identify, by the metasearch engine, the at least two different display lists with information that identifies which of the at least two different keyword phrases each of the at least two different display lists corresponds to.
43. The computer readable storage medium containing computer executable instructions of claim 42, further causing one or more computers to:
incorporate, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases and identify, by the metasearch engine, each of the received search results with information that identifies which of the plurality of search engines the received search results were received from.
44. The computer readable storage medium containing computer executable instructions of claim 43, further causing one or more computers to:
incorporate, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases and identify, by the metasearch engine, the rank of each of the received search results within each of the plurality of search engines.
45. The computer readable storage medium containing computer executable instructions of claim 41, wherein the request executed by the user one the client device comprises a sorting order specified by the user that specifies the order of each of the search results to be returned in each of the at least two different display lists, further causing one or more computers to:
incorporate, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases and sort, by the metasearch engine, the received search results in each of the at least two different display lists into the sorting order specified in the request executed by the user.
46. The computer readable storage medium containing computer executable instructions of claim 45, wherein the sorting order specified by the user on the client device comprises sorting the search results alphanumerically, further causing one or more computers to:
sort, by the metasearch engine, the search results within each of the at least two different display lists into alphanumeric order.
47. The computer readable storage medium containing computer executable instructions of claim 41, which further comprises the other request activated by the user on the client device for the metasearch engine to order the at least one quantity of the at least one item, the other request comprising the input inputted by the user onto the client device into the means for inputting the at least one quantity of the at least one item to be ordered, further causing one or more computers to:
(g) receive, at the metasearch engine, the other request from the client device for the metasearch engine to order the at least one quantity of the at least one item;
(h) process, by the metasearch engine, an order for the at least one quantity of the at least one item.
48. The computer readable storage medium containing computer executable instructions of claim 47, further causing one or more computers to:
(i) place, by the metasearch engine, the order with at least one server device on the distributed network and/or at least one third party for the at least one quantity of the at least one item.
49. The computer readable storage medium containing computer executable instructions of claim 41, further causing one or more computers to:
open connections, by the metasearch engine, substantially simultaneously with the plurality of search engines and send, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines.
50. The computer readable storage medium containing computer executable instructions of claim 49, further causing one or more computers to:
send, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases substantially simultaneously to the plurality of search engines.
51. The computer readable storage medium containing computer executable instructions of claim 41, causing one or more computers at (d) to incorporate, by the metasearch engine, into the response for communicating to the client device means for executing on the client device another request to be activated by the user for ordering the at least one quantity of the at least one item that may be ordered, further causing one or more computers at (d) to:
append, by the metasearch engine, at least one input element for inputting the at least one quantity of the at least one item that may be ordered to the at least one of the received search results comprising the information about the at least one item that may be ordered and
incorporate, by the metasearch engine, the appended at least one input element into the each of the at least two different display lists that comprise the at least one of the received search results comprising the information about the at least one item that may be ordered.
52. The computer readable storage medium containing computer executable instructions of claim 41, wherein the at least one item that may be ordered comprises at least two items that may be ordered causing one or more computers at (d) to incorporate, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases and causing one or more computers at (d) to incorporate that at least two items that may be ordered into any one of the at least two different display lists, further causing one or more computers at (d) to:
sort, by the metasearch engine, the received search results into the any one of the at least two different display lists according to price of the at least two items that may be ordered.
53. The computer readable storage medium containing computer executable instructions of claim 41, wherein:
at least one of the at least two different display lists comprises the received search results therein in response to at least two of the plurality of search queries comprising a same one of the at least two keyword phrases.
54. The computer readable storage medium containing computer executable instructions of claim 41, further causing one or more computers to:
send, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases substantially simultaneously to the plurality of search engines.
55. An apparatus for metasearching on a distributed network activated by a request executed by a user on a client device to request a metasearch engine to send a plurality of search queries to a plurality of search engines, the request specifically to which of the plurality of search engines each of the plurality of search queries specified in the request by the user it to be sent to, each of the plurality of search queries comprising a keyword phrase, each of the keyword phrases comprising at least one keyword specified in the request by the user, at least two of the keyword phrases of the plurality of search queries being different from each other, comprising:
(a) a receiver receiving, at the metasearch engine, the request from the client device for the metasearch engine to send the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines;
(b) a sender sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines, each as specified in the request executed by the user;
(c) the receiver receiving, at the metasearch engine, search results from the plurality of search engines in response to the plurality of search queries comprising the at least two keyword phrases send to the plurality of search engines, wherein at least one of the received search results comprises information about at least one item that may be ordered;
(d) an incorporator incorporating, by the metasearch engine, the received search results into at least two different display lists corresponding to the at least two different keyword phrases and
the incorporator incorporating, by the metasearch engine, means for inputting at least one quantity of the at lest one item that may be ordered into each of the at least two different display lists that comprise the at least one of the received search results comprising the information about the at least one items that may be ordered, the at least one quantity of the at least one item to be ordered to be input on the client device, wherein:
each different one of the at least two different display lists comprises the received search results in response to the plurality of search queries comprising a different one of the at least two keyword phrases, each same one of the at least two different display lists comprises the received search results therein in response to the plurality of search queries comprising a same one of the at least two keyword phrases;
(e) the incorporated incorporating, by the metasearch engine, the at least two different display lists of received search results into a response for communicating to the client device and
the incorporator incorporating, by the metasearch engine, into the response for communicating to the client device means for executing on the client device another request to be activated by the user for ordering the at least one quantity of the at least one item that may be ordered;
(f) a communicator communicating, by the metasearch engine, the response from the metasearch engine to the client device.
56. The apparatus of claim 55, wherein the incorporator incorporating, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases further comprises:
an identifier identifying, by the metasearch engine, the at least two different display lists with information that identifies which of the at least two different keyword phrases each of the at least two different display lists corresponds to.
57. The apparatus of claim 56, wherein the incorporator incorporating, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases further comprises:
the identifier identifying, by the metasearch engine, each of the received search results with information that identifies which of the plurality of search engines that received search results were received from.
58. The apparatus of claim 57, wherein the incorporator incorporating, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases further comprises:
the identifier identifying, by the metasearch engine, the rank of each of the received search results within each of the plurality of search engines.
59. The apparatus of claim 55, where the request executed by the user on the client device comprises a sorting order specified by the user that specifies the order of each of the search results to be returned in each of the at least two different display lists, the incorporator incorporating, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases further comprises:
a sorter sorting, by the metasearch engine, the receive search results in each of the at least two different display lists into the sorting order specified in the request executed by the user.
60. The apparatus of claim 59, wherein the sorting order specified by the user on the client device comprises sorting the search results alphanumerically, the sorter comprises:
the sorter sorting, by the metasearch engine, the search results within each of the at least two different display lists into alphanumeric order.
61. The apparatus of claim 55, which further comprises the other request activated by the user on the client device for the metasearch engine to order the at least one quantity of the at least one item the other request comprising the input inputted by the user onto the client device into the means for inputting the at least one quantity of the at least one item to be ordered, further comprising:
(g) the receiver receiving, at the metasearch engine, the other request from the client device for the metasearch engine to order the at least one quantity of the at least one item;
(h) a processor processing, by the metasearch engine, an order for the at least one quantity of the at least one item.
62. The apparatus of claim 61, further comprising:
(i) a placer placing, by the metasearch engine, the order with at least one server device on the distributed network and/or at least one third party for the at least one quantity of the at least one item.
63. The apparatus of claim 55, wherein prior to the sender sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines, the apparatus further comprises:
an opener opening connections, by the metasearch engine, substantially simultaneously with the plurality of search engines.
64. The apparatus of claim 63, wherein the sender sending, by the metasearch engine, the plurality of search queries comprising the at least tow keyword phrases to the plurality of search engines, each as specified in the request executed by the user further comprisies:
the sender sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases substantially simultaneously to the plurality of search engines.
65. The apparatus of claim 55, wherein the incorporator incorporating, by the metasearch engine, the means for inputting the at least one quantity of the at least one item that may be ordered into the each of the at least two different display lists that comprise the at least one of the received search results comprising the information about the at least one item that may be ordered, (d) comprises:
an appended appending, by the metasearch engine, at least one input element for inputting the at least one quantity of the at least one item that may be order to the at least one of the received search results comprising the information about the at least one item that may be ordered and the incorporator incorporating, by the metasearch engine, the appended at least one input element into the each of the at least two different display lists that comprise the at least one of the received search results comprising the information about the at least one item that may be ordered.
66. The apparatus of claim 55, wherein the at least one item that may be ordered comprises at least two items that may be ordered and the incorporator incorporating, by the metasearch engine, the received search results into the at least two different display lists corresponding to the at least two different keyword phrases comprises the incorporator incorporating that at least two items that may be ordered into any one of the at least two different display lists, (d) further comprises:
a sorter sorting, by the metasearch engine, the received search results into the any one of the at least two different display lists according to price of the at least two items that may be ordered.
67. The apparatus of claim 55, wherein:
at least one of the at least two different display lists comprises the received search results therein in response to tat least to of the plurality of search queries comprising a same one of the at least two keyword phrases.
68. The system of claim 55, wherein the sender sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases to the plurality of search engines, each as specified in the request executed by the user further comprises:
the sender sending, by the metasearch engine, the plurality of search queries comprising the at least two keyword phrases substantially simultaneously to the plurality of search engines.
Patent Citations (10)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5913215(A) | 1999-06-01 | Rubinstein et al. | Examiner |
| US6085186(A) | 2000-07-01 | Christianson et al. | Examiner |
| US6102969(A) | 2000-08-01 | Christianson et al. | Examiner |
| US6275820(B1) | 2001-08-01 | Navin-Chandra et al. | Examiner |
| US6298382(B1) | 2001-10-01 | Doi et al. | Examiner |
| US6327590(B1) | 2001-12-01 | Chidlovskii et al. | Examiner |
| US6370527(B1) | 2002-04-01 | Singhal | Examiner |
| US6523023(B1) | 2003-02-01 | Sonnenberg | Examiner |
| US6721736(B1) | 2004-04-01 | Krug et al. | Examiner |
| US6751612(B1) | 2004-06-01 | Schuetze et al. | Examiner |