Client-server multitasking

Abstract

A client-server multitasking process comprising: receiving a request comprising searching criteria, comprising search queries, at least two of which comprise different query values directed to different server addresses, criteria specifying for which request group information is to be returned; for the search queries in the specified request group, sending to the server designated by the server address a query derived from the corresponding search query; receiving response information from the servers; processing the response information into a plurality of return groups by associating a different query value with a different one of the return groups and merging into the return group the response information from the servers that received queries directed to the query value associated with the return group; incorporating into the return group means for inputting at least one request for ordering at least one item; consolidating the return groups into a consolidated response; returning the consolidated response.

Claims

What is claimed is:

1. A client-server multitasking process comprising the steps of:

(a) Receiving a request from a client at a server comprising searching criteria, request grouping criteria, and display criteria, wherein (1) the searching criteria comprise n search query and server address pairs, (2) each search query comprises at least one query value, (3) at least two of the n search queries comprise different query values and are directed to different server addresses, (4) n is greater than one, (5) the request grouping criteria comprises information for splitting the n search query and server address pairs into m request groups, (6) m is less than n and m is greater than or equal to 1, (7) the display criteria specifies for which request group information is to be returned;

(b) Processing the n search query and server address pairs into m request groups;

(c) For only the search query and server address pairs in the specified request group for which information is to be returned, opening a connection with the server specified by the server address and sending to the specified server a query derived from the corresponding search query comprising at least one query value, wherein the connections to the specified servers are opened substantially simultaneously;

(d) Receiving response information from the servers in the specified request group;

(e) Processing the response information from the servers into a plurality of return groups by (1) associating a different query value from the search query and server address pairs in the specified request group for which information is to be returned with a different one of the return groups and (2) merging into the return group the response information from the servers in the specified request group that received queries directed to the query value associated with the return group;

wherein the response information to be merged into the return group in step (e)(2) comprises information about at least one item that may be ordered, step (e)(2) further comprises:

Incorporating into the return group a means for inputting at least one request for ordering the at least one item;

(f) Consolidating the return groups into a consolidated response;

(g) Returning the consolidated response to the client.

2. The client-server multitasking process of claim 1, further comprising the steps of:

(h) Receiving a request from the client at the server for ordering one or more items;

(i) Processing an order for the one or more items.

3. The client-server multitasking process of claim 2, further comprising the step of:

(j) Confirming the order.

4. The client-server multitasking process of claim 2, further comprising the step of:

(j) Placing at least one order with at least one third party and/or at least one other server for the one or more items.

5. The client-server multitasking process of claim 2, further comprising the step of:

(j) Updating the order.

6. The client-server multitasking process of claim 1, wherein step (e)(2) further comprises:

Incorporating into the return group a means for previewing the at least one request for ordering the at least one item.

7. The client-server multitasking process of claim 1, wherein step (e)(2) further comprises:

Incorporating into the return group a means for updating the at least one request for ordering the at least one item.

8. The client-server multitasking process of claim 6, wherein step (e)(2) further comprises:

Incorporating into the return group a means for updating the at least one request for ordering the at least one item.

9. The client-server multitasking process of claim 1, wherein the means for inputting the at least one request for ordering the at least one item comprises:

Means for inputting at least one quantity of the at least one item into the at least one request for ordering the at least one quantity of the at least one item.

10. The client-server multitasking process of claim 1, wherein step (f) further comprises:

Incorporating into the consolidated response a means for inputting payment and/or shipping information.

11. The client-server multitasking process of claim 3, wherein the step of confirming the order comprises:

Confirming the order by e-mail.

12. The client-server multitasking process of claim 4, wherein the step of placing the at least one order with the at least one third party and/or the at least one other server for the one or more items comprises:

Placing the at least one order with the at least one third party and/or the at least one other server for the one or more items by e-mail.

13. The client-server multitasking process of claim 1, wherein the response information to be merged into the return group in step (e)(2) comprises at least one other value, step (e)(2) further comprises:

Sorting into the return group the response information from the servers in the specified request group that received queries directed to the query value associated with the return group, according to other value of the response information.

14. The client-server multitasking process of claim 13, wherein the other value is from the group consisting of: price, value, cost, quantity, amount, numerical value, rank, position, index, server address, alphanumeric value, location in the specified request group, and combination of at least any two thereof.

15. The client-server multitasking process of claim 13, wherein the sorting comprises a sorting order according to the other value from the group consisting of: ascending, descending, interleaved, as-is, and elimination of any duplicate response information or any duplicate portion of any of the foregoing.

16. The client-server multitasking process of claim 15, wherein the request comprises sorting criteria, which comprises the sorting order.

17. The client-server multitasking process of claim 15, wherein the other value is from the group consisting of: price, value, cost, quantity, amount, numerical value, rank, position, index, server address, alphanumeric value, location in the specified request group, and combination of at least any two thereof.

18. The client-server multitasking process of claim 13, wherein the means for inputting the at least one request for ordering the at least one item comprises:

Means for inputting at least one quantity of the at least one item into the at least one request for ordering the at least one quantity of the at least one item.

19. The client-server multitasking process of claim 1, prior to step (e)(2), further comprising the step of:

Processing the response information from the servers into a plurality of portions;

Step (e)(2) comprising:

Merging into the return group the response information portions from the servers in the specified request group that received queries directed to the query value associated with the return group.

20. The client-server multitasking process of claim 19, wherein each of the response information portions to be merged into the return group in step (e)(2) comprises at least one other value, step (e)(2) further comprises:

Sorting into the return group the response information portions from the servers in the specified request group that received queries directed to the query value associated with the return group, according to the other value of the response information portion.

21. The client-server multitasking process of claim 19, wherein at least one of the response information portions has the information about the at least one item that may be ordered, the means for inputting the at least one request for ordering the at least one item comprises:

Means for inputting at least one quantity of the at least one item into the at least one request for ordering the at least one quantity of the at least one item.

22. The client-server multitasking process of claim 20, wherein at least one of the response information portions has the information about the at least one item that may be ordered, the means for inputting the at least one request for ordering the at least one item comprises:

Means for inputting at least one quantity of the at least one item into the at least one request for ordering the at least one quantity of the at least one item.

23. The client-server multitasking process of claim 20, wherein the other value is from the group consisting of: price, value, cost, quantity, amount, numerical value, rank, position, index, server address, alphanumeric value, location in the specified request group, and combination of at least any two thereof.

24. The client-server multitasking process of claim 20, wherein the sorting comprises a sorting order according to the other value from the group consisting of: ascending, descending, interleaved, as-is, and elimination of any duplicate response information or any duplicate portion of any of the foregoing.

25. The client-server multitasking process of claim 24, wherein the request comprises sorting criteria, which comprises the sorting order.

26. The client-server multitasking process of claim 1, prior to step (e)(2), further comprising the step of:

Processing the response information from the servers into a plurality of addressable portions;

Step (e)(2) comprising:

Pointing/addressing the addressable response information portions;

Merging into the return group the pointed/addressed addressable response information portions from the servers in the specified request group that received queries directed to the query value associated with the return group.

27. The client-server multitasking process of claim 26, wherein each of the addressable response information portions to be merged into the return group in step (e)(2) comprises at least one other value, step (e)(2) further comprises:

Sorting into the return group the pointed/addressed addressable response information portions from the servers in the specified request group that received queries directed to the query value associated with the return group, according to the other value of the pointed/addressed addressable response information portion.

28. The client-server multitasking process of claim 26, wherein:

the step of processing the response information from the servers into the plurality of addressable portions comprises:

Processing the response information from the servers into the plurality of addressable portions comprising addressable pointer/address indexes;

the step of pointing/addressing the addressable response information portions comprises:

Pointing/addressing the addressable pointer/address indexes of the addressable response information portions.

29. The client-server multitasking process of claim 27, wherein:

the step of processing the response information from the servers into the plurality of addressable portions comprises:

Processing the response information from the servers into the plurality of addressable portions comprising addressable pointer/address indexes;

the step of pointing/addressing the addressable response information portions comprises:

Pointing/addressing the addressable pointer/address indexes of the addressable response information portions.

30. The client-server multitasking process of claim 1, wherein the merged response information comprises at least one link to at least one site.

31. The client-server multitasking process of claim 1, further comprising the step of:

(h) Updating at least one of the steps of the client-server multitasking process.

32. The client-server multitasking process of claim 1, wherein the connections to the specified servers are opened substantially simultaneously step (c) further comprises:

Sending to the specified servers the queries substantially simultaneously.

33. The client-server multitasking process of claim 1, wherein the client-server multitasking process is performed substantially on-the-fly and in real time.

34. The client-server multitasking process of claim 1, wherein the client, the server, and the specified servers are on a network.

35. The client-server multitasking process of claim 34, wherein:

the network is from the group consisting of: the internet, a metropolitan area network, a wide area network, a local area network, and combination of at least any two thereof.

36. The client-server multitasking process of claim 1, wherein:

the client is from the group consisting of: a process, a program, a site, a client, a server, a search engine, a computer, and combination of at least any two thereof;

the server is from the group consisting of: a process, a program, a site, a client, a server, a search engine, a computer, and combination of at least any two thereof;

the servers in the specified request group are from the group consisting of: processes, programs, sites, clients, servers, search engines, computers, databases, and combination of at least any two thereof.

37. The client-server multitasking process of claim 1, wherein the client and the server are from the group consisting of: the client and the server integrated one with the other, the client and the server separate one from the other, the client and the server collocated one with the other, the client and the server remotely located one from the other, the client comprising the server, and the server comprising the client.

38. The client-server multitasking process of claim 1, prior to step (a), further comprising the step of:

Communicating from a user through a user interface to the client the searching criteria, request grouping criteria, and display criteria.

39. A client-server multitasking system comprising:

(a) Means for receiving a request from a client at a server comprising searching criteria, request grouping criteria, and display criteria, wherein (1) the searching criteria comprise n search query and server address pairs, (2) each search query comprises at least one query value, (3) at least two of the n search queries comprise different query values and are directed to different server addresses, (4) n is greater than one, (5) the request grouping criteria comprises information for splitting the n search query and server address pairs into m request groups, (6) m is less than n and m is greater than or equal to 1, (7) the display criteria specifies for which request group information is to be returned;

(b) Means for processing the n search query and server address pairs into m request groups;

(c) Means for only the search query and server address pairs in the specified request group for which information is to be returned, opening a connection with the server specified by the server address and sending to the specified server a query derived from the corresponding search query comprising at least one query value, wherein the connections to the specified servers are opened substantially simultaneously;

(d) Means for receiving response information from the servers in the specified request group;

(e) Means for processing the response information from the servers into a plurality of return groups by (1) associating a different query value from the search query and server address pairs in the specified request group for which information is to be returned with a different one of the return groups and (2) merging into the return group the response information from the servers in the specified request group that received queries directed to the query value associated with the return group;

wherein the response information to be merged into the return group comprises information about at least one item that may be ordered, further comprising:

Means for incorporating into the return group a means for inputting at least one request for ordering the at least one item;

(f) Means for consolidating the return groups into a consolidated response;

(g) Means for returning the consolidated response to the client.

40. The client-server multitasking system of claim 39, further comprising:

(h) Means for receiving a request from the client at the server for ordering one or more items;

(i) Means for processing an order for the one or more items.

41. The client-server multitasking system of claim 40, further comprising:

(j) Means for confirming the order.

42. The client-server multitasking system of claim 40, further comprising:

(j) Means for placing at least one order with at least one third party and/or at least one other server for the one or more items.

43. The client-server multitasking system of claim 39, further comprising:

Means for incorporating into the return group a means for previewing the at least one request for ordering the at least one item.

44. The client-server multitasking system of claim 39, further comprising:

Means for incorporating into the return group a means for updating the at least one request for ordering the at least one item.

45. The client-server multitasking system of claim 43, further comprising:

Means for incorporating into the return group a means for updating the at least one request for ordering the at least one item.

46. The client-server multitasking system of claim 39, wherein the means for inputting the at least one request for ordering the at least one item comprises:

Means for inputting at least one quantity of the at least one item into the at least one request for ordering the at least one quantity of the at least one item.

47. The client-server multitasking system of claim 39, further comprising:

Means for incorporating into the consolidated response a means for inputting payment and/or shipping information.

48. The client-server multitasking system of claim 41, wherein the means for confirming the order comprises:

Means for confirming the order by e-mail.

49. The client-server multitasking system of claim 42, wherein the means for placing the at least one order with the at least one third party and/or the at least one other server for the one or more items comprises:

Means for placing the at least one order with the at least one third party and/or the at least one other server for the one or more items by e-mail.

50. The client-server multitasking system of claim 39, wherein the response information to be merged into the return group comprises at least one other value, further comprising:

Means for sorting into the return group the response information from the servers in the specified request group that received queries directed to the query value associated with the return group, according to other value of the response information.

51. The client-server multitasking system of claim 39, wherein the connections to the specified servers are opened substantially simultaneously, further comprising:

Means for sending to the specified servers the queries substantially simultaneously.

52. A computer readable medium containing computer executable instructions for causing one or more computers to:

(a) Receive a request from a client at a server comprising searching criteria, request grouping criteria, and display criteria, wherein (1) the searching criteria comprise n search query and server address pairs, (2) each search query comprises at least one query value, (3) at least two of the n search queries comprise different query values and are directed to different server addresses, (4) n is greater than one, (5) the request grouping criteria comprises information for splitting the n search query and server address pairs into m request groups, (6) m is less than n and m is greater than or equal to 1, (7) the display criteria specifies for which request group information is to be returned;

(b) Process the n search query and server address pairs into m request groups;

(c) For only the search query and server address pairs in the specified request group for which information is to be returned, open a connection with the server specified by the server address and send to the specified server a query derived from the corresponding search query comprising at least one query value, wherein the connections to the specified servers are opened substantially simultaneously;

(d) Receive response information from the servers in the specified request group;

(e) Process the response information from the servers into a plurality of return groups by (1) associating a different query value from the search query and server address pairs in the specified request group for which information is to be returned with a different one of the return groups and (2) merging into the return group the response information from the servers in the specified request group that received queries directed to the query value associated with the return group;

wherein the response information to be merged into the return group comprises information about at least one item that may be ordered, further causing one or more computers to:

Incorporate into the return group a means for inputting at least one request for ordering the at least one item;

(f) Consolidate the return groups into a consolidated response;

(g) Return the consolidated response to the client.

53. The computer readable medium of claim 52, further causing one or more computers to:

(h) Receive a request from the client at the server for ordering one or more items;

(i) Process an order for the one or more items.

54. The computer readable medium of claim 53, further causing one or more computers to:

(j) Confirm the order.

55. The computer readable medium of claim 53, further causing one or more computers to:

(j) Place at least one order with at least one third party and/or at least one other server for the one or more items.

56. The computer readable medium of claim 52, further causing one or more computers to:

Incorporate into the return group a means for previewing the at least one request for ordering the at least one item.

57. The computer readable medium of claim 52, further causing one or more computers to:

Incorporate into the return group a means for updating the at least one request for ordering the at least one item.

58. The computer readable medium of claim 56, further causing one or more computers to:

Incorporate into the return group a means for updating the at least one request for ordering the at least one item.

59. The computer readable medium of claim 52, further causing one or more computers to:

Incorporate means for inputting at least one quantity of the at least one item into the means for inputting the at least one request for ordering the at least one quantity of the at least one item.

60. The computer readable medium of claim 52, further causing one or more computers to:

Incorporate into the consolidated response a means for inputting payment and/or shipping information.

61. The computer readable medium of claim 54, further causing one or more computers to:

Confirm the order by e-mail.

62. The computer readable medium of claim 55, further causing one or more computers to:

Place the at least one order with the at least one third party and/or the at least one other server for the one or more items by e-mail.

63. The computer readable medium of claim 52, wherein the response information to be merged into the return group comprises at least one other value, further causing one or more computers to:

Sort into the return group the response information from the servers in the specified request group that received queries directed to the query value associated with the return group, according to other value of the response information.

64. The computer readable medium of claim 52, wherein the connections to the specified servers are opened substantially simultaneously, further causing one or more computers to:

send to the specified servers the queries substantially simultaneously.

65. An apparatus for client-server multitasking, comprising:

(a) A receiver receiving a request from a client at a server comprising searching criteria, request grouping criteria, and display criteria, wherein (1) the searching criteria comprise n search query and server address pairs, (2) each search query comprises at least one query value, (3) at least two of the n search queries comprise different query values and are directed to different server addresses, (4) n is greater than one, (5) the request grouping criteria comprises information for splitting the n search query and server address pairs into m request groups, (6) m is less than n and m is greater than or equal to 1, (7) the display criteria specifies for which request group information is to be returned;

(b) A processor processing the n search query and server address pairs into m request groups;

(c) A transmitter, for only the search query and server address pairs in the specified request group for which information is to be returned, opening a connection with the server specified by the server address and sending to the specified server a query derived from the corresponding search query comprising at least one query value, wherein the connections to the specified servers are opened substantially simultaneously;

(d) The receiver receiving response information from the servers in the specified request group;

(e) The processor processing the response information from the servers into a plurality of return groups by (1) associating a different query value from the search query and server address pairs in the specified request group for which information is to be returned with a different one of the return groups and (2) merging into the return group the response information from the servers in the specified request group that received queries directed to the query value associated with the return group;

wherein the response information to be merged into the return group comprises information about at least one item that may be ordered, further comprising:

An incorporator incorporating into the return group a means for inputting at least one request for ordering the at least one item;

(f) A consolidator consolidating the return groups into a consolidated response;

(g) The transmitter returning the consolidated response to the client.

66. The apparatus of claim 65, further comprising:

(h) The receiver receiving a request from the client at the server for ordering one or more items;

(i) The processor processing an order for the one or more items.

67. The apparatus of claim 66, further comprising:

(j) A confirmer confirming the order.

68. The apparatus of claim 66, further comprising:

(j) An order placer placing at least one order with at least one third party and/or at least one other server for the one or more items.

69. The apparatus of claim 66, further comprising:

(j) An updater updating the order.

70. The apparatus of claim 65, further comprising:

An incorporator incorporating into the return group a means for previewing the at least one request for ordering the at least one item.

71. The apparatus of claim 65, further comprising:

An incorporator incorporating into the return group a means for updating the at least one request for ordering the at least one item.

72. The apparatus of claim 70, further comprising:

An incorporator incorporating into the return group a means for updating the at least one request for ordering the at least one item.

73. The apparatus of claim 65, wherein the incorporator incorporating into the return group the means for inputting the at least one request for ordering the at least one item comprises:

Means for inputting at least one quantity of the at least one item into the at least one request for ordering the at least one quantity of the at least one item.

74. The apparatus of claim 65, further comprising:

An incorporator incorporating into the consolidated response a means for inputting payment and/or shipping information.

75. The apparatus of claim 67, wherein:

The confirmer confirms the order by e-mail.

76. The apparatus of claim 68, wherein:

The order placer places the at least one order with the at least one third party and/or the at least one other server for the one or more items by e-mail.

77. The apparatus of claim 65, wherein the response information to be merged into the return group comprises at least one other value, further comprising:

A sorter sorting into the return group the response information from the servers in the specified request group that received queries directed to the query value associated with the return group, according to other value of the response information.

78. The apparatus of claim 65, wherein the connections to the specified servers are opened substantially simultaneously, further comprising:

The transmitter sending to the specified servers the queries substantially simultaneously.

79. The apparatus of claim 65, further comprising:

A user interface communicating from a user to the client the searching criteria, request grouping criteria, and display criteria.

80. The apparatus of claim 65, further comprising:

A user interface communicating from a user to the client the searching criteria, request grouping criteria, display criteria, and at least one input for inputting the at least one request for ordering the at least one item.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

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

2. Background Art

Clients, servers, and client-server systems have been known. However there is a need for client-server multitasking. A client-server multitasking system and process are needed, which are capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly.

A requester and/or user should be capable of making substantially multiple simultaneous same and/or different requests of same and/or different servers. The client server-multitasking system and process should be capable of organizing responses from the servers into service and/or information responses, and communicating the service and/or information responses to the requestors and/or users substantially simultaneously, and on-the-fly.

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 requesters and/or the users substantially simultaneously. The same and/or different ones of uniform resource locators, target resources, and/or paths may be used.

The requesters and/or the users should be capable of making multiple simultaneous searches. The searches should be capable of having at least one or a plurality of same or different queries of the same and/or different servers and/or clients. The responses from the servers and/or the clients should be capable of being organized into the service and/or information response in a variety of formats. It should be possible to sort the responses within the service and/or information response, such as, for example, by category, query, group, page, order of importance, ascending and/or descending order, alphabetically and/or numerically, or other characteristics, as determined by the requester, and/or the user, and/or the client-server multitasking system, or to combine the responses within the service and/or information response, such as, for example, interleaving the responses one with the other, such as, for example, by order of relevance or other parameters. The responses should be capable of being grouped by search criteria, server, order of importance, or by numerical factors such as value, price, or other numerical quantifier. For example, the responses should be presentable, for example, in ascending or descending order in interleaved format, such as top ones, twos, threes, and so on, or presentable separately to the requester and/or the user. The order may be order of importance or relevance related, or, for example, numerically valued, such as price or stock market value.

The client-server multitasking system and process 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.

The client-server multitasking system and process should be capable of substantially multiple simultaneous searching, using the same and/or different ones of queries of the same and/or different ones of the clients and/or servers, which may be search engines, and/or sites, and/or servers, and/or locations on the network, and additionally and/or alternatively building a client-server multitasking search engine and/or database. The client-server multitasking search engine and/or database should be capable of storing the information and/or services retrieved therefrom the search engines, and/or sites, and/or servers, and/or locations being queried on the network therein, and building the client-server search engine and/or database. The client-server multitasking search engine should also be capable of being queried either directly and/or in combination therewith the substantially simultaneous searching, using the same and/or different queries of the same and/or different search engines, sites, servers, and/or databases. The client-server multitasking search engine and/or database should also be capable of updating information and/or services stored therein by querying sites, servers, search engines, and/or databases containing information and/or services referenced in client-server multitasking search engine and/or database.

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.

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.

The client-server multitasking system and process should also be capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the 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 drilling down and/or up to different levels within the search engines, sites, and/or servers being queried.

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

The client-server multitasking system and process should be capable of incorporating information and/or services thereinto a variety of user interfaces at different locations therein the user interfaces, grouping, and/or organizing the information and/or services, and optionally eliminating duplicate information and/or services.

The client-server multitasking system and process should be capable of incorporating links, graphics, video, text, and audio, and/or combinations thereof, and selective advertising, according to selectable search, query, sorting, and/or grouping criteria, and/or combinations thereof thereinto the information and/or services to be delivered thereto the user interfaces. The user should also be capable of placing orders, such as purchases, and/or other types of orders, payments, confirmations thereof, and/or combinations thereof, either directly and/or therethrough servers and/or sites thereon the network.

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.

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 requester, and/or the user, and/or optional storage, and/or retrieval of such services and/or information from the optional storage. The client-server multitasking system and process should be capable of building a client-server multitasking system search engine and/or database therefrom responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof. The client-server multitasking system search engine and/or database having stored information and/or services therein should also be searchable, be capable of full text searches thereof, and be searchable by the servers and/or the clients on the network, either separately and/or in combination therewith the substantially simultaneous multiple same and/or different searches and/or queries of the same and/or different servers on the network. Information therein the client-server multitasking system search engine and/or database should also be searchable and/or retrievable, and should be capable of being incorporated therein the service and/or information responses delivered thereto the user interfaces, according to search criteria, selectively and/or automatically, by the requester, and/or the user. The client-server multitasking system search engine and/or database should also be capable of spidering, and/or roboting, and/or querying sites, services and/or information to be stored therein and/or stored therein the client-server multitasking system search engine and/or database, and updating the services and/or information to be stored and/or stored therein the client-server multitasking system search engine and/or database.

The client-server multitasking system and process should be capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information therefrom the same and/or different ones of the servers and/or clients having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information thereinto user responses for delivery to and use by the requesters and/or users.

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 of performing as a single point of sale for purchasing multiple products from multiple sources.

For the foregoing reasons, there is a need for a client-server multitasking system and process capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries of the same and/or different ones of the servers, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly, and communicating service and/or information responses to the requestors and/or users substantially simultaneously and on-the-fly. The client-server multitasking system and process should be capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks, and be capable of searching search engines and/or other sites substantially simultaneously and on-the-fly. The client-server multitasking system and process should be capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the requesters, and/or the users, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system should also be capable of use in a variety of applications, and capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system and process should also be capable of building a client-server multitasking system search engine and/or database therefrom responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof, be capable of being searched and/or queried, querying sites referenced therein the client-server multitasking system search engine and/or database, and updating information and/or services stored therein. The client-server multitasking system and process should be capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information therefrom the same and/or different ones of the servers and/or clients having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information thereinto user responses for delivery to and use by the requestors and/or users.

SUMMARY

The present invention is directed to a client-server multitasking system and process capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries of the same and/or different ones of the servers, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly, and communicating service and/or information responses to the requestors and/or users substantially simultaneously and on-the-fly. The client-server multitasking system and process is capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks, and be capable of searching search engines and/or other sites substantially simultaneously and on-the-fly.

The client-server multitasking system and process is capable of retrieving substantially multiple simultaneous services and/or information having the same and/or different criteria from the same and/or different servers, sorting, grouping, and/or organizing the responses from the servers and/or the clients into information and/or services responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously. The requesters and/or the users may make substantially simultaneous service and/or information requests of servers and clients, using the same and/or different queries, and/or the same and/or different instructions.

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

The client-server multitasking system and process is capable of making multiple substantially simultaneous same and/or different requests of same and/or different servers, organizing responses from the servers into service and/or information responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously.

The client-server multitasking system and process is also capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the requestors and/or the users, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system is capable of use in a variety of applications, and is capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system and process is also be capable of building a client-server multitasking system search engine and/or database therefrom responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof, be capable of being searched and/or queried, querying sites referenced therein the client-server multitasking system search engine and/or database, and updating information and/or services stored therein.

The client-server multitasking system and process are capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly.

A requestor and/or user is capable of making substantially multiple simultaneous same and/or different requests of same and/or different servers. The client server-multitasking system and process is capable of organizing responses from the servers into service and/or information responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously, and on-the-fly.

The requesters and/or users are capable of making substantially simultaneous service and/or information requests of the same and/or different ones of servers and/or clients, using the same and/or different queries, and/or the same and/or different instructions. The client-server multitasking system and process is capable of retrieving substantially multiple simultaneous services and/or information having the same and/or different criteria from the same and/or different servers, sorting, grouping, and/or organizing the responses from the servers and/or the clients into information and/or services responses, and communicating the service and/or information responses to the requestors and/or the users substantially simultaneously. The same and/or different ones of uniform resource locators, target resources, and/or paths may be used.

The requestors and/or users are capable of making multiple simultaneous searches. The searches may have at least one or a plurality of same or different queries of the same and/or different servers and/or clients. The responses from the servers and/or the clients may be of being organized into the service and/or information response in a variety of formats. The responses may be sorted within the service and/or information response, such as, for example, by category, query, group, page, order of importance, ascending and/or descending order, alphabetically and/or numerically, or other characteristics, as determined by the requester, and/or the user, and/or the client-server multitasking system, and/or the responses may be combined within the service and/or information response, such as, for example, interleaving the responses one with the other, such as, for example, by order of relevance or other parameters. The responses may also be capable of being grouped by search criteria, server, order of importance, or by numerical factors such as value, price, or other numerical quantifier. For example, the responses may be presentable, for example, in ascending or descending order in interleaved format, such as top ones, twos, threes, and so on, or presentable separately to the requestor and/or the user. The order may be order of importance or relevance related, or, for example, numerically valued, such as price or stock market value.

The client-server multitasking system and process is be capable of information and/or service retrieval from the same and/or different ones of the servers substantially simultaneously and on-the-fly, using the same and/or different ones of the queries, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly.

The client-server multitasking system and process is capable of substantially multiple simultaneous searching, using the same and/or different ones of queries of the same and/or different ones of the clients and/or servers, which may be search engines, and/or sites, and/or servers, and/or locations on the network, and additionally and/or alternatively building a client-server multitasking search engine and/or database. The client-server multitasking search engine and/or database is capable of storing the information and/or services retrieved therefrom the search engines, and/or sites, and/or servers, and/or locations being queried on the network therein, and building the client-server search engine and/or database. The client-server multitasking search engine should is also capable of being queried either directly and/or in combination therewith the substantially simultaneous searching, using the same and/or different queries of the same and/or different search engines, sites, servers, and/or databases. The client-server multitasking search engine and/or database should is also capable of updating information and/or services stored therein by querying sites, servers, search engines, and/or databases containing information and/or services referenced in client-server multitasking search engine and/or database.

The client-server multitasking system and process is also capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks.

The client-server multitasking system and process are capable of substantially simultaneous searching of the same and/or different ones of search engines and/or sites on the network substantially on-the-fly, with the same and/or different ones of the queries, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly.

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

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

The client-server multitasking system and process are capable of incorporating information and/or services thereinto a variety of user interfaces at different locations therein the user interfaces, grouping, and/or organizing the information and/or services, and optionally eliminating duplicate information and/or services.

The client-server multitasking system and process are capable of incorporating links, graphics, video, text, and audio, and/or combinations thereof, and selective advertising, according to selectable search, query, sorting, and/or grouping criteria, and/or combinations thereof thereinto the information and/or services to be delivered thereto the user interfaces. The requestor and/or the user may place orders, such as purchases, and/or other types of orders, payments, confirmations thereof, and/or combinations thereof, either directly and/or therethrough servers and/or sites thereon the network.

The client-server multitasking system is capable of use in a variety of applications, and is capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system is capable of, for example, determining best query results, with respect to a plurality of search engine results; purchasing and/or price comparisons, viewing and/or reviewing prices/values and trends for different sites, determining lowest costs and lowest cost analyses for wholesale and retail purposes; product availability, e.g., airline tickets, pricing, and ticket availability, from different airlines to the same and/or different locations; purchasing of commodities and/or stocks form the same and/or different sites with updates every few seconds and/or minutes; obtaining prices and/or values in different stock markets substantially simultaneously; and searching for jobs on the same and/or different job sites, using the same and/or different job criteria, for example, on a daily basis, the job sites having changing job availability; and/or a combination thereof, all substantially simultaneously. The client-server multitasking system is capable of presenting information and/or services for review and/or updating from the same and/or different ones of sites, servers, and/or applications substantially simultaneously, and trend analysis thereof, using a variety of sorting, grouping and/or organizing criteria, according to the needs of the requester, and/or the user, and/or resident within the client-server multitasking system.

The client server-multitasking system and process are capable of service and/or information retrieval from at least one server, organization, communication, and presentation of such services and/or information to at least one requestor and/or user, and/or optional storage, and/or retrieval of such services and/or information from the optional storage. The client-server multitasking system and process are capable of building a client-server multitasking system search engine and/or database therefrom responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof. The client-server multitasking system search engine and/or database having stored information and/or services therein are also searchable, are capable of full text searches thereof, and are searchable by the servers and/or the clients on the network, either separately and/or in combination therewith the substantially simultaneous multiple same and/or different searches and/or queries of the same and/or different servers on the network. Information therein the client-server multitasking system search engine and/or database are also searchable and/or retrievable, and are capable of being incorporated therein the service and/or information responses delivered thereto the user interfaces, according to search criteria, selectively and/or automatically, by the requestor and/or the user. The client-server multitasking system search engine and/or database are capable of spidering, and/or roboting, and/or querying sites, services and/or information to be stored therein and/or stored therein the client-server multitasking system search engine and/or database, and updating the services and/or information to be stored and/or stored therein the client-server multitasking system search engine and/or database.

The client-server multitasking system and process are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information therefrom the same and/or different ones of the servers and/or clients having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information thereinto user responses for delivery to and use by the requestors and/or users.

The client-server multitasking system and process, then, are capable of information and/or service retrieval from the same and/or different ones of servers substantially simultaneously and on-the-fly, using the same and/or different ones of queries of the same and/or different ones of the servers, and sorting, grouping, and/or organizing responses therefrom substantially on-the-fly, and communicating service and/or information responses to the requesters and/or users substantially simultaneously and on-the-fly. The client-server multitasking system and process are capable of use on a variety of networks, such as global area networks, and in particular the internet, metropolitan area networks, wide area networks, and local area networks, and are capable of searching search engines and/or other sites substantially simultaneously and on-the-fly. The client-server multitasking system and process are capable of sorting, grouping, and/or organizing results therefrom the servers, search engines, and/or sites, in accordance with instructions from the requesters, and/or users, and/or instructions resident within the client-server multitasking system and/or process. The client-server multitasking system is capable of use in a variety of applications, and capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking system and process are capable of building a client-server multitasking system search engine and/or database therefrom responses returned from the servers, search engines, and/or sites being queried and/or searched, and/or having requests made thereof, is capable of being searched and/or queried, querying sites referenced therein the client-server multitasking system search engine and/or database, and updating information and/or services stored therein. The client-server multitasking system and process are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information therefrom the same and/or different ones of the servers and/or clients having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information thereinto user responses for delivery to and use by the requestors and/or users.

The client-server multitasking system and process are also capable of performing as a multiple query search engine, which performs multiple queries of multiple sites, and of performing as a single point of sale for purchasing multiple products from multiple sources.

A multitasking process having features of the present invention comprises: parsing, processing, and/or formatting a service and/or information request thereinto a current request group; opening connections therewith and making at least one request thereof at least one server; parsing, processing, formatting, grouping, and/or organizing at least one response therefrom the at least one server thereinto at least one addressable response information group; formulating information therefrom the current request group thereinto a request pointer/address group having at least one pointer/address; formulating at least one addressable query pointer/address group having at least one other pointer/address; incorporating information and/or services therefrom the at least one addressable response information group thereinto at least one addressable query information group; and incorporating the at least one addressable query information group thereinto a service and/or information response.

A client-server multitasking system having features of the present invention comprises: means for parsing, processing, and/or formatting a service and/or information request thereinto a current request group; means for opening connections therewith and making at least one request thereof at least one server; means for parsing, processing, formatting, grouping, and/or organizing at least one response therefrom the at least one server thereinto at least one addressable response information group; means for formulating information therefrom the current request group thereinto a request pointer/address group having at least one pointer/address; means for formulating at least one addressable query pointer/address group having at least one other pointer/address; means for incorporating information and/or services therefrom the at least one addressable response information group thereinto at least one addressable query information group; and means for incorporating the at least one addressable query information group thereinto a service and/or information response.

DRAWINGS

These and other features, aspects, and advantages of the present invention will become better understood with regard to the following description, appended claims, and accompanying drawings where:

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

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

FIG. 3 is a schematic representation of user input UI.sub.n from user U.sub.n thereinto user interface I.sub.n of the client-server multitasking system;

FIG. 4 is a schematic representation of a server S.sub.z of the client-server multitasking system;

FIG. 5A depicts a typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate typical user input UI.sub.n thereinto;

FIG. 5B depicts the typical service and/or information entry request form IE.sub.n at the user interface I.sub.n of FIG. 5A with reference alphanumerics;

FIG. 6 depicts another typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate other typical user input UI.sub.n thereinto;

FIG. 7 depicts another typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate other typical user input UI.sub.n thereinto;

FIG. 8 depicts another typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate other typical user input UI.sub.n thereinto;

FIG. 9 depicts another typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate other typical user input UI.sub.n thereinto;

FIG. 10 depicts another typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate other typical user input UI.sub.n thereinto;

FIG. 11 depicts a typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 12 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 13 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 14A depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 14B depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 14C depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 15 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 16 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 17 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 18 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 19 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 20 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 21 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 22 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 23 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 24 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 25 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIG. 26 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIGS. 27A-27C depict a typical user response UR.sub.n, as a typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 28A-28C depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 29A-29C depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 30A-30B depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 31A-31B depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 32A-32B depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 33A-33C depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 34A-34C depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 35A-35C depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 36A-36C depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 37A-37D depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 38A-38D depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 39A-39C depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 40A-40M depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 41A-41F depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 42A-42O depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 43A-43O depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 44A-44C depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 45A-45C depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 46A-46E depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 47A-47C depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 48A-48D depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 49A-49I depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 50A-50K depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 51A-51G depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIGS. 52A-52C depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

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

FIG. 53B is a schematic representation of a client C.sub.n of the client-server multitasking system having an optional database;

FIG. 54 is a schematic representation of a particular one of the clients C.sub.1 . . . C.sub.n of the client-server multitasking system, designated as the particular client C.sub.n, communicating with ones of the servers S.sub.1 . . . S.sub.z, in accordance with the designation scheme corresponding to the corresponding ones of the server designations S.sub.n1 . . . S.sub.nm, corresponding to the requests Q.sub.n1 . . . Q.sub.nm, therethrough the server PS;

FIG. 55 is a schematic representation of the particular client C.sub.n of the client-server multitasking system communicating with ones of the servers S.sub.1 . . . S.sub.z, in accordance with the designation scheme corresponding to the corresponding ones of the server designations S.sub.n1 . . . S.sub.nm, corresponding to the requests Q.sub.n1 . . . Q.sub.nm ;

FIG. 56 is a schematic representation of the particular client C.sub.n of the client-server multitasking system communicating with ones of the servers S.sub.1 . . . S.sub.z, in accordance with the designation scheme corresponding to the corresponding ones of the server designations S.sub.n1 . . . S.sub.nm, corresponding to the requests Q.sub.n1 . . . Q.sub.nm, and also therethrough the server PS;

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;

FIG. 58 is a schematic representation of a particular service and/or information request IQ.sub.n ;

FIG. 59 is a schematic representation of a particular service and/or information request IQ.sub.n parsed, processed, and/or formatted into a current request group QA.sub.nc, request groups QA.sub.n1 . . . QA.sub.nz, and corresponding optional instructions VJ.sub.n1 . . . VJ.sub.nk, and utilization of information therefrom to make the requests Q.sub.n1 . . . Q.sub.nm, obtain the responses R.sub.n1 . . . R.sub.nm, and incorporate information therefrom into a particular service and/or information response IR.sub.n ;

FIG. 60 is a schematic representation of the particular service and/or information request IQ.sub.n parsed, processed, and/or formatted into a current request group QA.sub.nc, request groups QA.sub.n1 . . . QA.sub.nz, and corresponding optional instructions VJ.sub.n1 . . . VJ.sub.nk, and utilization of information therefrom to make the requests Q.sub.n1 . . . Q.sub.nm, obtain the responses R.sub.n1 . . . R.sub.nm, and incorporate information therefrom into the particular service and/or information response IR.sub.n, having other grouping/sorting that may be used additionally and/or alternatively to that of FIG. 59;

FIG. 61 is a schematic representation of the particular service and/or information response IR.sub.n having a service and/or information group G.sub.n, additional request links SL.sub.n1 . . . SL.sub.nw, optional order form, optional additional advertisements and/or links, optional hidden information, and the optional service and/or information entry request form;

FIG. 62 is a schematic representation of a particular user service and/or information request iq.sub.n ;

FIG. 63 is a schematic representation of a particular user service and/or information request iq.sub.n parsed, processed, and/or formatted into the current request group QA.sub.nc, the request groups QA.sub.n1 . . . QA.sub.nz, and the corresponding optional instructions VJ.sub.n1 . . . VJ.sub.nk, and utilization of information therefrom to make the requests Q.sub.n1 . . . Q.sub.nm, obtain the responses R.sub.n1 . . . R.sub.nm, and incorporate information therefrom into the particular user service and/or information response ir.sub.n ;

FIG. 64 is a schematic representation of the particular user service and/or information request iq.sub.n parsed, processed, and/or formatted into the current request group QA.sub.nc, the request groups QA.sub.n1 . . . QA.sub.nz, and the corresponding optional instructions VJ.sub.n1 . . . VJ.sub.nk, and utilization of information therefrom to make the requests Q.sub.n1 . . . Q.sub.nm, obtain the responses R.sub.n1 . . . R.sub.nm, and incorporate information therefrom into the particular user service and/or information response ir.sub.n, having other grouping/sorting that may be used additionally and/or alternatively to that of FIG. 63;

FIG. 65 is a schematic representation of the particular user service and/or information response ir.sub.n having the service and/or information group G.sub.n, the additional request links SL.sub.n1 . . . SL.sub.nw, the optional order form, the optional additional advertisements and/or links, the optional hidden information, and the optional service and/or information entry request form;

FIG. 66A is a schematic representation of a response information group RG.sub.nm having addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr showing optional addressable pointer/address indices IN.sub.nm1 . . . IN.sub.nmr correspondingly associated therewith optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr, which may be addressed/pointed therewith pointer/address PP.sub.nm1 ;

FIG. 66B is a schematic representation of the addressable response information group RG.sub.nm having the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr showing the optional addressable pointer/address indices IN.sub.nm1 . . . IN.sub.nmr correspondingly associated therewith the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr, which may be addressed/pointed therewith the pointer/address PP.sub.nm2 ;

FIG. 66C is a schematic representation of the addressable response information group RG.sub.nm having the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr showing the optional addressable pointer/address indices IN.sub.nm1 . . . IN.sub.nmr correspondingly associated therewith the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr, which may be addressed/pointed therewith the pointer/address PP.sub.nmr ;

FIG. 67 is a schematic representation of the individual information groups LG.sub.nm1 . . . LG.sub.nmr having corresponding optional links LD.sub.nm1 . . . LD.sub.nmr, and/or corresponding optional descriptions DD.sub.nm1 . . . DD.sub.nmr, and/or corresponding optional prices/values PD.sub.nm1 . . . PD.sub.nmr, and/or corresponding optional images ID.sub.nm1 . . . ID.sub.nmr ;

FIG. 68 is a schematic representation of a labelled individual information group LL.sub.nmr ;

FIG. 69 is a schematic representation of an addressable query information group GI.sub.nz ;

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

FIG. 71 is a schematic representation of a multitasking process of deriving the service and/or information response IR.sub.n and/or the user service and/or information response ir.sub.n, with reference to FIGS. 59 and 63;

FIG. 72 is a schematic representation of a multitasking process of deriving the service and/or information response IR.sub.n and/or the user service and/or information response ir.sub.n 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;

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

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

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

FIG. 76 is a schematic representation of user review of user response UR.sub.n and/or selection of additional services and/or information;

FIG. 77 is a schematic representation of the user input UI.sub.n thereinto the service and/or information entry request form IE.sub.n ;

FIG. 78 is a schematic representation of the service and/or information entry request form IE.sub.n showing fields, links, and elements of the service and/or information entry request form IE.sub.n ;

FIG. 79 is a schematic representation of a completed service and/or information entry request form IF.sub.n showing typical elements, values, and field names;

FIG. 80 is a schematic representation of the completed service and/or information entry request form IF.sub.n, a user service and/or information request iq.sub.n, and the client C.sub.n of the client-server multitasking system;

FIG. 81 is a schematic representation of the user service and/or information request iq.sub.n ;

FIG. 82 is a schematic representation of the service and/or information request IQ.sub.n ;

FIG. 83 is an alternate schematic representation of the user service and/or information request iq.sub.n of FIG. 81;

FIG. 84 is an alternate schematic representation of the service and/or information request IQ.sub.n of FIG. 82;

FIG. 85 is a more detailed schematic representation of the service and/or information request IQ.sub.n of FIGS. 82 and 84 showing typical field names and values;

FIG. 86 is an alternate more detailed schematic representation of the service and/or information request IQ.sub.n of FIGS. 82 and 84;

FIG. 87 is a schematic representation showing queries QQ.sub.n1 . . . QQ.sub.nm and corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm ;

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

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

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

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

FIG. 92 is a schematic representation of information that may be used for formulating a typical particular one of the requests Q.sub.n1 . . . Q.sub.nm, designated as the request Q.sub.nm, and optional instructions VJ.sub.nm1 . . . VJ.sub.nk from the particular service and/or information request IQ.sub.n and opening a connection OC.sub.nm ;

FIG. 93 is a schematic representation of information that may be used for formulating the typical particular one of the requests Q.sub.n1 . . . Q.sub.nm, designated as the request Q.sub.nm, and the optional instructions VJ.sub.nm1 . . . VJ.sub.nk from the particular user service and/or information request iq.sub.n and opening the connection OC.sub.nm ;

FIG. 94 is an alternate schematic representation of information that may be used for formulating the typical particular one of the requests Q.sub.n1 . . . Q.sub.nm, designated as the request Q.sub.nm, and optional instructions VJ.sub.nm1 . . . VJ.sub.nk from the particular service and/or information request IQ.sub.n and opening a connection OC.sub.nm of FIG. 92;

FIG. 95 is an alternate schematic representation of information that may be used for formulating the typical particular one of the requests Q.sub.n1 . . . Q.sub.nm, designated as the request Q.sub.nm, and the optional instructions VJ.sub.nm1 . . . VJ.sub.nk from the particular user service and/or information request iq.sub.n and opening the connection OC.sub.nm of FIG. 93;

FIG. 96 is a schematic representation of queries QQ.sub.n1 . . . QQ.sub.nm, corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm, and optional instructions VJ.sub.nm1 . . . VJ.sub.nk that may be parsed, processed, and/or formatted from the service and/or information request IQ.sub.n and/or the user service and/or information request iq.sub.n ;

FIG. 97 is a schematic representation of a request pointer/address group QZ.sub.ns, having a particular one of query pointer/address groups QG.sub.n1 . . . QG.sub.nz, designated as the query pointer/address group QG.sub.nz, associated ones of the addressable response information groups RG.sub.n1 . . . RG.sub.nm, the pointers/addresses PP.sub.n11 . . . PP.sub.nmr, and the query information group GI.sub.nz associated therewith the query pointer/address group QG.sub.nz ;

FIG. 98 is a schematic representation of a sorting criteria addressing scheme having a particular query pointer/address group QG.sub.nz, associated ones of response information groups RG.sub.nm, and query information group GI.sub.nz associated therewith the query pointer/address group QG.sub.nz ;

FIG. 99 is a schematic representation of an alternate sorting criteria addressing scheme having a particular query pointer/address group QG.sub.nz, associated ones of response information groups RG.sub.nm, and query information group GI.sub.nz associated therewith the query pointer/address group QG.sub.nz ;

FIG. 100 is a schematic representation of typical ones of the query pointer/address groups QG.sub.n1 . . . QG.sub.nz, having the sorting criteria addressing scheme of FIG. 98, having typical ones of queries QQ.sub.n1 . . . QQ.sub.nz and corresponding server addresses AQ.sub.n1 . . . AQ.sub.nz associated therewith;

FIG. 101 is another schematic representation of the typical ones of the query pointer/address groups QG.sub.n1 . . . QG.sub.nz, having the sorting criteria addressing scheme of FIG. 98, having the typical ones of the of queries QQ.sub.n1 . . . QQ.sub.nz and the corresponding ones of the server addresses AQ.sub.n1 . . . AQ.sub.nz of FIG. 100 associated therewith;

FIG. 102 is a generic schematic representation of the query pointer/address groups QG.sub.n1 . . . QG.sub.nz, having the sorting criteria addressing scheme of FIG. 98, having the ones of queries QQ.sub.n1 . . . QQ.sub.nz and the corresponding ones of the server addresses AQ.sub.n1 . . . AQ.sub.nz associated therewith;

FIG. 103 is a schematic representation of a request Q.sub.nm of the client-server multitasking system;

FIG. 104 is a schematic representation of a response R.sub.nm of the client-server multitasking system;

FIG. 105 is a schematic representation of an entity body RH.sub.nm of the response R.sub.nm of FIG. 104 having optional response individual information groups LS.sub.nm1 . . . LS.sub.nmr, and/or optional information LI.sub.nm ;

FIG. 106 is a schematic representation of the addressable response information group RG.sub.nm having the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr parsed, and/or processed, and/or formatted, and/or organized, and/or grouped thereinto the addressable response information group RG.sub.nm therefrom the optional entity body RH.sub.nm of FIG. 105;

FIG. 107 is a schematic representation of the optional response individual information group LS.sub.nmr parsed, and/or processed, and/or formatted, and/or organized, and/or grouped thereinto the addressable individual information group LG.sub.nmr ;

FIG. 108 is a schematic representation of the optional links LD.sub.nm1 . . . LD.sub.nmr, and/or the optional descriptions DD.sub.nm1 . . . DD.sub.nmr, and/or the optional prices/values PD.sub.nm1 . . . PD.sub.nmr, and/or the optional images ID.sub.nm1 . . . ID.sub.nmr parsed individually and/or separately, and incorporated thereinto the addressable response information group RG.sub.nm therefrom the optional entity body RH.sub.nm ;

FIGS. 109 is a schematic representation of a typical one of the addressable query information group GI.sub.nz, based upon certain sorting and/or grouping criteria, having the labelled individual information groups LL.sub.nz1 . . . LL.sub.nzu, the optional database labelled individual information groups RL.sub.nz1 . . . RL.sub.nzx, the optional query description QT.sub.nz, the optional server descriptions and/or links ST.sub.nz1 . . . ST.sub.nzf, and the optional advertisements and/or links LT.sub.nz1 . . . LT.sub.nzt incorporated thereinto certain typical ones of the typical service and/or information response forms IS.sub.n of FIGS. 27A-52C, inclusive;

FIGS. 110 is a another schematic representation of a typical one of the addressable query information group GI.sub.nz, based upon certain sorting and/or grouping criteria, having the labelled individual information groups LL.sub.nz1 . . . LL.sub.nzu, the optional database labelled individual information groups RL.sub.nz1 . . . RL.sub.nzx, the optional query description QT.sub.nz, the optional server descriptions and/or links ST.sub.nz1 . . . ST.sub.nzf and the optional advertisements and/or links LT.sub.nz1 . . . LT.sub.nzt incorporated thereinto certain typical ones of the typical service and/or information response forms IS.sub.n of FIGS. 27A-52C, inclusive;

FIG. 111 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIGS. 112A-112H depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIG. 113 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIGS. 114A-114H depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIG. 115 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIGS. 116A-116H depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIG. 117 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIGS. 118A-118H depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIG. 119 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIGS. 120A-120H depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIG. 121 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIGS. 122A-122H depict a typical combined user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, and an order entry form OF.sub.n, which the user U.sub.n may enter an order therewith, illustrated in partial views;

FIGS. 123A-123H depict the typical combined user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, and the order entry form OF.sub.n, which the user U.sub.n may enter the order therewith, of FIGS. 114A-114H, with typical order information entered therein, illustrated in partial views;

FIGS. 124A-124B depict a typical preview form of an order OP.sub.n, resulting from submission of the order entry form OF.sub.n, of the typical combined user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, and the order entry form OF.sub.n, which the user U.sub.n may enter the order therewith, of FIGS. 114A-114H, with the typical order information entered therein, as shown in FIGS. 123A-123H, illustrated in partial views;

FIGS. 125A-125B depict a typical order placement form OL.sub.n, having the typical preview form of the order OP.sub.n, resulting from submission of the order entry form OF.sub.n, of the typical combined user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, and the order entry form OF.sub.n, which the user U.sub.n may enter the order therewith, of FIGS. 114A-114H, with the typical order information entered therein, as shown in FIGS. 123A-123H, or which the user U.sub.n may enter therethrough the typical preview form of the order OP.sub.n of FIGS. 124A-124B, illustrated in partial views;

FIGS. 126A-126B depict a typical completed order placement form OL.sub.n, having a preview of the order OP.sub.n, resulting from submission of the order entry form OF.sub.n, of the typical combined user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, and the order entry form OF.sub.n, which the user U.sub.n may enter the order therewith, of FIGS. 114A-114H, with the typical order information entered therein, as shown in FIGS. 123A-123H, or which the user U.sub.n may enter therethrough the typical preview form of the order OP.sub.n of FIGS. 124A-124B, illustrated in partial views;

FIGS. 127A-127B depict a typical order confirmation OC.sub.n, resulting from submission of the typical completed order placement form OL.sub.n of FIGS. 126A-126B, illustrated in partial views;

FIGS. 128A-128C depict a typical e-mail order placement EP.sub.n, resulting from submission of the typical completed order placement form OL.sub.n of FIGS. 126A-126B, illustrated in partial views;

FIGS. 129A-129C depict a typical e-mail confirmation of receipt of order EC.sub.n, resulting from submission of the typical completed order placement form OL.sub.n of FIGS. 126A-126B, illustrated in partial views;

FIGS. 130A-130B depict a typical e-mail order placement EP.sub.n of a portion of the order, resulting from submission of the typical completed order placement form OL.sub.n of FIGS. 126A-126B, illustrated in partial views;

FIGS. 131A-131B depict a typical e-mail order placement EP.sub.n of another portion of the order, resulting from submission of the typical completed order placement form OL.sub.n of FIGS. 126A-126B, illustrated in partial views;

FIGS. 132A-132B depict a typical e-mail order placement EP.sub.n of another portion of the order, resulting from submission of the typical completed order placement form OL.sub.n of FIGS. 126A-126B, illustrated in partial views;

FIG. 133 is a schematic representation of certain typical optional instructions VJ.sub.nm1 . . . VJ.sub.nk and/or certain additional request links SL.sub.n1 . . . SL.sub.nw ;

FIG. 134 is a schematic representation of other certain typical optional instructions VJ.sub.nm1 . . . VJ.sub.nk and/or other certain additional request links SL.sub.n1 . . . SL.sub.nw ;

FIG. 135 depicts certain typical additional request links SL.sub.n1 . . . SL.sub.nw ;

FIG. 136 depicts another typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate other typical user input UI.sub.n thereinto;

FIG. 137 depicts another typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate other typical user input UI.sub.n thereinto;

FIG. 138 depicts another typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate other typical user input UI.sub.n thereinto;

FIG. 139 depicts another typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate other typical user input UI.sub.n thereinto;

FIG. 140 depicts another typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate other typical user input UI.sub.n thereinto;

FIG. 141 depicts another typical service and/or information entry request form IE.sub.n at the user interface I.sub.n, which the user U.sub.n may communicate other typical user input UI.sub.n thereinto;

FIG. 142 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIGS. 143A-143H depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIG. 144 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ;

FIGS. 145A-145G depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views;

FIG. 146 depicts another typical completed service and/or information entry request form IF.sub.n at the user interface I.sub.n ; and

FIGS. 147A-147G depict another typical user response UR.sub.n, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated thereto the user U.sub.n, illustrated in partial views.

DESCRIPTION

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

FIGS. 1 and 2 show a client-server multitasking system 10 of the present invention, having requesters U.sub.1 . . . U.sub.n (12), hereinafter called users U.sub.1 . . . U.sub.n (12), corresponding user interfaces I.sub.1 . . . I.sub.n (14), corresponding clients C.sub.1 . . . C.sub.n (16), server PS (18), servers S.sub.1 . . . S.sub.z (20), and optional servers SO.sub.1 . . . SO.sub.p (22), constructed in accordance with the present invention, which reside on a network 24. Each of the users U.sub.1 . . . U.sub.n (12) communicate with the corresponding clients C.sub.1 . . . C.sub.n (16) therethrough the corresponding user interfaces I.sub.1 . . . I.sub.n (14).

Each of the users U.sub.1 . . . U.sub.n (12) enter corresponding user inputs UI.sub.1 . . . UI.sub.n (25) having one or more same and/or different user requests qu.sub.11 . . . qu.sub.nu (26) thereinto the corresponding user interfaces I.sub.1 . . . I.sub.n (14), as shown in FIG. 3. The user requests qu.sub.11 . . . qu.sub.nu (26) are communicated from the user interfaces I.sub.1 . . . I.sub.n (14) to the corresponding clients C.sub.1 . . . C.sub.n (16) within corresponding user service and/or information requests iq.sub.1 . . . iq.sub.n (27), having the user requests qu.sub.11 . . . qu.sub.nu (26) and other optional information. The users U.sub.1 . . . U.sub.n (12) may enter the corresponding user inputs UI.sub.1 . . . UI.sub.n (25) at the same and/or different times.

Each of the user interfaces I.sub.1 . . . I.sub.n (14) communicate the user service and/or information requests iq.sub.1 . . . iq.sub.n (27) thereto the corresponding clients C.sub.1 . . . C.sub.n (16), which optionally format the corresponding user service and/or information requests iq.sub.1 . . . iq.sub.n (27) into corresponding service and/or information requests IQ.sub.1 . . . IQ.sub.n (28), as required. Each of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) have information therein that may be used to formulate one or more same and/or different requests Q.sub.11 . . . Q.sub.nm (29) to be made of one or more of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20), which may hereinafter be called server designations S.sub.11 . . . S.sub.nm (30), in accordance with a designation scheme which designates the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.11 . . . Q.sub.nm (29) as the corresponding server designations S.sub.11 . . . S.sub.nm (30), as shown in FIGS. 2 and 4. FIG. 4 shows the server designations S.sub.11 . . . S.sub.nm (30) for typical ones of the requests Q.sub.11 . . . Q.sub.nm (29) and a typical one of the servers S.sub.z (20). Each of the requests Q.sub.11 . . . Q.sub.nm (29) may be the same and/or different one from the other and may be made of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20) at the same time and/or different times.

Each of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) may be communicated thereto the server PS (18), which parses, processes, and/or formats the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) into the requests Q.sub.11 . . . Q.sub.nm (29).

The corresponding clients C.sub.1 . . . C.sub.n (16) may also and/or alternatively optionally parse, process, and/or format the corresponding user service and/or information requests iq.sub.1 . . . iq.sub.n (27) into one or more of the same and/or different requests Q.sub.11 . . . Q.sub.nm (29) to be made of one or more of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme corresponding to the corresponding ones of the server designations S.sub.11 . . . S.sub.nm (30), as required.

Certain ones of the clients C.sub.1 . . . C.sub.n (16) may communicate corresponding certain ones of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) to the server PS (18), which parses, processes and/or formats the certain ones of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) into certain ones of the requests Q.sub.11 . . . Q.sub.nm (29), as required, and communicates the certain ones of the requests Q.sub.11 . . . Q.sub.nm (29) to the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme corresponding to the corresponding certain ones of the server designations S.sub.11 . . . S.sub.nm (30).

Alternate ones of the clients C.sub.1 . . . C.sub.n (16) may communicate corresponding alternate ones of the requests Q.sub.11 . . . Q.sub.nm (29) to corresponding alternate ones of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme corresponding to the corresponding alternate ones of the server designations S.sub.11 . . . S.sub.nm (30).

Other alternate ones of the clients C.sub.1 . . . C.sub.n (16) may communicate corresponding other alternate ones of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) to the server PS (18), which parses, processes and/or formats the other alternate ones of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) into other alternate ones of the requests Q.sub.11 . . . Q.sub.nm (29), as required, communicates the other alternate ones of the requests Q.sub.11 . . . Q.sub.nm (29) to corresponding other alternate ones of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme corresponding to the corresponding other alternate ones of the server designations S.sub.11 . . . S.sub.nm (30); and additionally the other alternate ones of the clients C.sub.1 . . . C.sub.n (16) may also parse, process, and/or format the user service and/or information requests iq.sub.1 . . . iq.sub.n (27) into one or more of the same and/or different yet other alternate ones of the requests Q.sub.11 . . . Q.sub.nm (29), and communicate the yet other alternate ones of the requests Q.sub.11 . . . Q.sub.nm (29) to corresponding yet other alternate ones of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme corresponding to the corresponding yet other alternate ones of the server designations S.sub.11 . . . S.sub.nm (30).

Each of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) may, thus, be communicated therefrom the corresponding clients C.sub.1 . . . C.sub.n (16) to the server PS (18). The requests Q.sub.11 . . . . Q.sub.nm (29) may be communicated therefrom the server PS (18) and/or therefrom the corresponding clients C.sub.1 . . . C.sub.n (16) to the servers S.sub.11 . . . S.sub.z (20), and may depend upon instructions from and/or generated by the corresponding users U.sub.1 . . . U.sub.n (12), and/or the corresponding user interfaces I.sub.1 . . . I.sub.n (14) and/or the corresponding clients C.sub.1 . . . C.sub.n (16), and/or information generated by the server PS (18) and/or the servers S.sub.1 . . . S.sub.z (20), and/or ancillary instructions, a combination thereof, and/or other suitable means.

Each of the servers S.sub.1 . . . S.sub.z (20) corresponding to the designation scheme S.sub.11 . . . S.sub.nm (30) replies to the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), accordingly, and communicates corresponding responses R.sub.11 . . . R.sub.nm (32), associated with the requests Q.sub.11 . . . Q.sub.nm (29), to the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) making the requests Q.sub.11 . . . Q.sub.nm (29), as shown in FIG. 2 for typical ones of the requests Q.sub.11 . . . Q.sub.nm (29) and the corresponding responses R.sub.11 . . . R.sub.nm (32).

The server PS (18) and/or the appropriate clients C.sub.1 . . . C.sub.n (16) parse, process, format, sort, group, and/or organize the responses R.sub.11 . . . R.sub.nm (32) into corresponding service and/or information responses IR.sub.1 . . . IR.sub.n (34), having corresponding parsed, processed, formatted, sorted, grouped, and/or organized service and/or information groups G.sub.1 . . . G.sub.n (35) (shown later in FIGS. 27A-52C, inclusive) acceptable to the corresponding clients C.sub.1 . . . C.sub.n (16) and the corresponding respective user interfaces I.sub.1 . . . I.sub.n (14). The server PS (18) communicates the appropriate service and/or information responses IR.sub.n1 . . . IR.sub.n (34) to the corresponding clients C.sub.1 . . . C.sub.n (16).

The clients C.sub.1 . . . C.sub.n (16) format the service and/or information responses IR.sub.1 . . . IR.sub.n (34) into corresponding user service and/or information responses ir.sub.1 . . . ir.sub.n (36), as required, and communicate the user service and/or information responses ir.sub.1 . . . ir.sub.n (36) thereto the corresponding user interfaces I.sub.1 . . . I.sub.n (14). The user interfaces I.sub.1 . . . I.sub.n (14) incorporate the user service and/or information responses ir.sub.1 . . . ir.sub.n (36) into corresponding user responses UR.sub.1 . . . UR.sub.n (37), which are derived at the user interfaces I.sub.1 . . . I.sub.n (14), and communicated by the user interfaces I.sub.1 . . . I.sub.n (14) thereto the corresponding users U.sub.1 . . . U.sub.n (12). The users U.sub.1 . . . U.sub.n (12) review the corresponding user responses UR.sub.1 . . . UR.sub.n (37) at the user interfaces I.sub.1 . . . I.sub.n (14) and/or select additional services and/or information therefrom.

B. Typical Service and/or Information Entry Request Forms

FIGS. 5A, 5B, and 6-10 show typical ones of service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38) at the user interfaces I.sub.1 . . . I.sub.n (14), which the users U.sub.1 . . . U.sub.n (12) may communicate typical ones of the user inputs UI.sub.1 . . . UI.sub.n (25) thereinto, as requests for information and/or services. The typical ones of the service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38) at the user interfaces I.sub.1 . . . I.sub.n (14) shown in FIGS. 5A, 5B, and 6-10 are typical examples of the service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38) at the user interfaces I.sub.1 . . . I.sub.n (14), a much larger variety of which is possible. Names and/or links and/or other information are incorporated therein the typical ones of the service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38) shown in FIGS. 5A, 5B, and 6-10 for illustrative purposes, and are not intended to limit the large variety of the service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38) and the names and/or links and/or information that are possible, and that may be incorporated thereinto the service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38) at the user interfaces I.sub.1 . . . I.sub.n (14).

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

FIGS. 11-26 show typical ones of completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230) at the user interfaces I.sub.1 . . . I.sub.n (14).

FIG. 11 shows a typical particular one of the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230), hereinafter designated the completed service and/or information entry request form IF.sub.n (230), at a particular one of the user interfaces I.sub.1 . . . I.sub.n (14), hereinafter designated the user interface I.sub.n (14), having same and different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52). Typical same ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), are "Cat", "Dog", and "Mouse", which are different one from the other.

FIG. 12 shows the typical completed service and/or information entry request forms IF.sub.n (230), at the user interface I.sub.n (14), having same and different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52). Typical same ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) are "Cat", "Dog", and "Mouse", which are different one from the other. Typical same ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) are "HotBot", "WebCrawler", and "Dejanews", which are different one from the other, and which are also different from "Yahoo" and "LookSmart". The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) have 5 "URL's per Search Engine", which instructs the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) having 5 "URL's per Search Engine", rather than 10 "URL's per Search Engine", as instructed in FIG. 11.

FIG. 13 shows the typical completed service and/or information entry request forms IF.sub.n (230), at the user interface I.sub.n (14) having a single typical one of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) as "Big Elephants".

FIGS. 14A, 14B, and 14C show the typical completed service and/or information entry request form IF.sub.n (230), at the user interface I.sub.n (14), having same and different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), showing "Current Group" as "Group I", "Group II", and "Group III", in FIGS. 14A, 14B, and 14C, respectively. Typical same ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) are "Catcher in the Rye", "Catcher", "Rye", "Sports", and "Rye Bread", which are different one from the other. The typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) are different one from the other. The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) have a 5 second "Timeout (seconds) per Search Engine", rather than a 3 second "Timeout (seconds) per Search Engine" as in FIGS. 11-13. The "Timeout (seconds) per Search Engine" instructs the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) within a period of less than the "Timeout (seconds) per Search Engine" specified in the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52). It should be noted that response times of less than one second per search engine are typical, and response times of substantially less than one second are quite common. However, the "Timeout (seconds) per Search Engine" has been incorporated herein for the user U.sub.1 (12) to specify in the event of slow ones of the responses R.sub.n1 . . . R.sub.nm (32) from certain ones of the servers S.sub.1 . . . S.sub.z (20).

FIG. 15 shows the typical completed service and/or information entry request forms IF.sub.n (230), at the user interface I.sub.n (14), having same and different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52). Typical same ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) are "Charles Dickens", "A Tale of Two Cities", and "Oliver Twist", which are different one from the other. All blank entries beneath the entry above take on the characteristics of the completed entry above. Therefore, Searches 2, 3, and 4 take on the typical queries QQ.sub.n2 . . . QQ.sub.n4 (53) of "Charles Dickens" of Search 1, above. Likewise, Searches 7, 8, and 9 take on the typical queries QQ.sub.n7 . . . QQ.sub.n9 (53) of "Oliver Twist" of Search 6, above. Search 5 takes on the typical query QQ.sub.n5 (53) of "A Tale of Two Cities".

The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) of FIG. 15 have "Separate", which instructs the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) in separate groups, i.e., grouped by the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), rather than interleaved one with the other, as instructed in FIGS. 11-14.

The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) "Interleaved" of FIGS. 11-14 instructs the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) having information and/or services therein the responses R.sub.n1 . . . R.sub.nm (32) to be interleaved one with the other (or alternating one with the other) therein the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63). The labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) therein the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) are alternatingly interleaved one with the other and labelled and/or identified and associated correspondingly therewith the responses R.sub.n1 . . . . R.sub.nm (32) therefrom the servers S.sub.1 . . . S.sub.z (20). The "Interleaved" information and/or services may typically be incorporated therein the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) in substantially the same sequence as the information and/or services are therein the responses R.sub.n1 . . . R.sub.nm (32) communicated therefrom the servers S.sub.1 . . . S.sub.z (20). However, other sorting/grouping criteria may optionally be used, as will be discussed later.

The typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) are different one from the other in FIG. 15. The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) also instruct the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) having 5 "Searches per Group", rather than 3 "Searches per Group", as in FIGS. 11-14. The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) also instruct the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) having 8 "URL's per Search Engine".

FIG. 16 shows the typical completed service and/or information entry request form IF.sub.n (230), at the user interface I.sub.n (14), having the same ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52). The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) have "URL Details" as "List", which instructs the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) "List" format rather than "Summary" format, as instructed in FIGS. 11-15. The "URL Details" as "Summary" instruct the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37) showing descriptions and/or other information and/or services, in addition to links, therein the typical ones of the user responses UR.sub.n (37), as the typical service and/or information response forms IS.sub.n (39) at the user interface I.sub.n (14), while "URL Details" as "List" instruct the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37) showing only links therein the typical ones of the user responses UR.sub.n (37), as the typical service and/or information response forms IS.sub.n (39) at the user interface I.sub.n (14).

The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) have 25 "URL's per Search Engine", which instructs the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) having 25 "URL's per Search Engine". The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) also instruct the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) having 9 "Searches per Group". The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) also instruct the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) at "Page" 3 of the "Current Group", rather than "Page" 1 of the "Current Group", as in FIGS. 11-15. The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) also instruct the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) to use a 2 second "Timeout (seconds) per Search Engine".

FIG. 17 shows another one of the typical completed service and/or information entry request form IF.sub.n (230), at the user interface I.sub.n (14), having the same ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52). The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) have 18 "URL's per Search Engine", which instructs the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) having 18 "URL's per Search Engine". The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) also instruct the client C.sub.n (16) and/or the server PS (18) to return the typical user response UR.sub.n (37), as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14) at "Group" 2, having 4 "Searches per Group", at "Page" 2 of the "Current Group", with a 2 second "Timeout (seconds) per Search Engine", and to return the results "Separately".

FIG. 18 shows another one of the typical completed service and/or information entry request form IF.sub.n (230), at the user interface I.sub.n (14), having different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52).

FIG. 19 shows another one of the typical completed service and/or information entry request form IF.sub.n (230), at the user interface I.sub.n (14), having different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), as in FIG. 18, the same ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52).

FIG. 20 shows the typical completed service and/or information entry request forms IF.sub.n (230), at the user interface I.sub.n (14) having a single typical one of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) as "sports".

FIG. 21 show another one of the typical completed service and/or information entry request forms IF.sub.n (230), at the user interface I.sub.n (14) having a single typical one of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) as "television".

FIG. 22 shows another one of the typical completed service and/or information entry request form IF.sub.n (230), at the user interface I.sub.n (14), having different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), .i.e., "sports" and "television", different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52).

FIG. 23 shows another one of the typical completed service and/or information entry request form IF.sub.n (230), at the user interface I.sub.n (14), having the same ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), i.e., "weather", different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52).

FIG. 24 shows another one of the typical completed service and/or information entry request form IF.sub.n (230), at the user interface I.sub.n (14), having different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), i.e., "education", "universities," and "training", different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (62).

FIG. 25 shows another one of the typical completed service and/or information entry request form IF.sub.n (230), at the user interface I.sub.n (14), having different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), .i.e., "weather", "climate," and "training", different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52).

FIG. 26 shows another one of the typical completed service and/or in