Metasearching on a wireless sensor network, using a plurality of spatially distributed sensor nodes that monitor physical and environmental conditions at a plurality of locations

Abstract

Apparatus and method for metasearching on a wireless sensor network, which comprises a plurality of spatially distributed autonomous devices, comprising a plurality of spatially distributed sensor nodes, comprising a plurality of motes, each of which has a mote transceiver and at least one sensor that monitors physical and environmental conditions and collects physical and environmental data at a plurality of locations; and a gateway node, comprising a metasearch engine that sends a plurality of queries to at least of the plurality of motes, via the gateway node, based upon a request executed on a client device; the gateway node receiving search results from the at least two motes, the metasearch engine comprising a processor that groups and sorts the search results into at least two different groups comprising a plurality of physical and environmental data lists; the metasearch engine sending a response, via the gateway node, to the client device.

Claims

1. Apparatus for metasearching on a wireless sensor network, comprising: a plurality of spatially distributed sensor nodes, comprising a plurality of motes that monitor physical and environmental conditions at a plurality of locations, each mote of said plurality of motes comprising: at least one sensor, which collects physical and environmental data, a mote server device, and a mote-transceiver, said each mote of said plurality of motes communicating with at least one other mote of said plurality of motes; a gateway node, comprising a gateway transceiver and a gateway server device, which comprises a metasearch engine, said metasearch engine communicating with at least two motes of said plurality of motes directly or via said at least one other mote of said plurality of motes or combination thereof; a client device, comprising a client transceiver, said client device communicating with said metasearch engine; said metasearch engine receiving a request from said client device, activated by said request executed on said client device, for said metasearch engine to request said metasearch engine to send a plurality of search queries to said at least two motes of said plurality of motes, said metasearch engine sending said plurality of search queries to said at least two motes of said plurality of motes, said metasearch engine receiving search results from said at least two motes of said plurality of motes in response to said plurality of search queries sent to said at least two motes of said plurality of motes, said metasearch engine grouping and sorting said search results into a plurality of groups comprising a plurality of physical and environmental data lists, according to said plurality of search queries, said metasearch engine incorporating said grouped and sorted search results, comprising said plurality of groups comprising said plurality of physical and environmental data lists, into a response for communicating to said client device, said metasearch engine communicating said response to said client device.

2. The apparatus of claim 1, further comprising: at least one other gateway node, comprising at least one other gateway transceiver and at least one other gateway server device, said at least one other gateway node communicating with said gateway node and said at least one other mote.

3. The apparatus of claim 1, further comprising: said metasearch engine causing at least one advertisement associated with one or more of said plurality of search queries to be displayed in said response.

4. The apparatus of claim 1, wherein: said plurality of search queries comprises a plurality of keywords, further comprising: said metasearch engine causing at least one advertisement associated with one or more of said plurality of keywords to be displayed in said response.

5. The apparatus of claim 1, wherein: at least one mote of said plurality of motes comprising at least one robotic device, which comprises at least one motion device, which imparts motion to and controls said motion of at least one portion of said at least one mote.

6. The apparatus of claim 1, wherein: at least one mote of said plurality of motes comprising at least one robotic device, which comprises at least one motion device, which imparts motion to and controls said motion of said at least one mote and relocates said at least one mote from a first location to a second location.

7. The apparatus of claim 1, wherein: said physical data comprises at least location of at least one mote of said plurality of motes; said environmental data comprises data at said at least one mote of said plurality of motes from the group consisting of temperature, pressure, motion, vibration, heat, sound, light, magnetic fields, electromagnetic fields, wind speed, wind direction, and any combination thereof.

8. Apparatus for metasearching on a wireless sensor network, comprising: a plurality of spatially distributed sensor nodes, comprising a plurality of motes that monitor physical and environmental conditions at a plurality of locations, each mote of said plurality of motes comprising: at least one sensor, which collects physical and environmental data, a mote server device, and a mote-transceiver, said each mote of said plurality of motes communicating with at least one other mote of said plurality of motes; a gateway node, comprising a gateway transceiver and a gateway server device, which comprises a metasearch engine, said metasearch engine communicating with at least two motes of said plurality of motes directly or via said at least one other mote of said plurality of motes or combination thereof; a client device, comprising a client transceiver, said client device communicating with said metasearch engine; said metasearch engine receiving a request from said client device, activated by said request executed on said client device, for said metasearch engine to request said metasearch engine to send at least one search query to said at least two motes of said plurality of motes, said metasearch engine sending said at least one search query to said at least two motes of said plurality of motes, said metasearch engine receiving search results from said at least two motes of said plurality of motes in response to said at least one search query sent to said at least two motes of said plurality of motes, said metasearch engine grouping and sorting said search results into at least one group comprising at least one physical and environmental data list, according to said at least one search query, said metasearch engine incorporating said grouped and sorted search results, comprising said at least one group comprising said at least one physical and environmental data list, into a response for communicating to said client device; said metasearch engine communicating said response to said client device.

9. The apparatus of claim 8, further comprising: at least one other gateway node, comprising at least one other gateway transceiver and at least one other gateway server device, said at least one other gateway node communicating with said gateway node and said at least one other mote.

10. The apparatus of claim 8, further comprising: said metasearch engine causing at least one advertisement associated with said at least one search query to be displayed in said response.

11. The apparatus of claim 8, wherein: at least one mote of said plurality of motes comprising at least one robotic device, which comprises at least one motion device, which imparts motion to and controls said motion of at least one portion of said at least one mote.

12. The apparatus of claim 8, wherein: at least one mote of said plurality of motes comprising at least one robotic device, which comprises at least one motion device, which imparts motion to and controls said motion of said at least one mote and relocates said at least one mote from a first location to a second location.

13. The apparatus of claim 8, wherein: said physical data comprises at least location of at least one mote of said plurality of motes; said environmental data comprises data at said at least one mote of said plurality of motes from the group consisting of temperature, pressure, motion, vibration, heat, sound, light, magnetic fields, electromagnetic fields, wind speed, wind direction, and any combination thereof.

14. The apparatus of claim 8, wherein: said wireless sensor network is used to monitor and/or control a facility and/or process from the group consisting of: a process, a facility, a manufacturing facility, an industrial process, process control, industrial process control, automobile manufacturing, pharmaceutical manufacturing, a petrochemical process, petrochemical manufacturing, a chemical process, chemical manufacturing, mining, ore recovery, process management, a monitoring operation, a control operation, shipping, transportation, oil drilling, oil refining, an oil well, an oil field, a power plant, water treatment, and wastewater treatment.

15. Apparatus for metasearching on a wireless sensor network, comprising: a plurality of spatially distributed sensor nodes, comprising a plurality of motes that monitor physical and environmental conditions at a plurality of locations, each mote of said plurality of motes comprising: at least one sensor, which collects physical and environmental data, a mote server device, and a mote-transceiver, said each mote of said plurality of motes communicating with at least one other mote of said plurality of motes; a gateway node, comprising a gateway transceiver and a gateway server device, which comprises a metasearch engine, said metasearch engine communicating with at least two motes of said plurality of motes directly or via said at least one other mote of said plurality of motes or combination thereof; a client device, comprising a client transceiver, said client device communicating with said metasearch engine; said metasearch engine receiving a request from said client device, activated by said request executed on said client device, for said metasearch engine to request said metasearch engine to send at least one search query to said at least two motes of said plurality of motes, said at least one search query comprising at least one keyword, said metasearch engine sending said at least one search query to said at least two motes of said plurality of motes, said metasearch engine receiving search results from said at least two motes of said plurality of motes in response to said at least one search query sent to said at least two motes of said plurality of motes, said metasearch engine grouping and sorting said search results into at least one group comprising at least one physical and environmental data list, according to said at least one search query, said metasearch engine incorporating said grouped and sorted search results, comprising said at least one group comprising said at least one physical and environmental data list, into a response for communicating to said client device, said metasearch engine causing at least one advertisement associated with said at least one keyword to be displayed in said response; said metasearch engine communicating said response to said client device.

16. The apparatus of claim 15, further comprising: at least one other gateway node, comprising at least one other gateway transceiver and at least one other gateway server device, said at least one other gateway node communicating with said gateway node and said at least one other mote.

17. The apparatus of claim 15, wherein: at least one mote of said plurality of motes comprising at least one robotic device, which comprises at least one motion device, which imparts motion to and controls said motion of at least one portion of said at least one mote.

18. The apparatus of claim 15, wherein: at least one mote of said plurality of motes comprising at least one robotic device, which comprises at least one motion device, which imparts motion to and controls said motion of said at least one mote and relocates said at least one mote from a first location to a second location.

19. The apparatus of claim 15, wherein: said physical data comprises at least location of at least one mote of said plurality of motes; said environmental data comprises data at said at least one mote of said plurality of motes from the group consisting of temperature, pressure, motion, vibration, heat, sound, light, magnetic fields, electromagnetic fields, wind speed, wind direction, and any combination thereof.

20. The apparatus of claim 15, wherein: said wireless sensor network is used to monitor and/or control a facility and/or process from the group consisting of: a process, a facility, a manufacturing facility, an industrial process, process control, industrial process control, automobile manufacturing, pharmaceutical manufacturing, a petrochemical process, petrochemical manufacturing, a chemical process, chemical manufacturing, mining, ore recovery, process management, a monitoring operation, a control operation, shipping, transportation, oil drilling, oil refining, an oil well, an oil field, a power plant, water treatment, and wastewater treatment.

Description

DRAWINGS

(1) 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:

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

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

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

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

(6) 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;

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

(8) 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;

(9) 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;

(10) 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;

(11) 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;

(12) 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;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

(31) FIGS. 27A, 27B, and 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 to the user U.sub.n, illustrated in partial views;

(32) FIGS. 28A, 28B, and 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 to the user U.sub.n, illustrated in partial views;

(33) FIGS. 29A, 29B, and 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 to the user U.sub.n, illustrated in partial views;

(34) FIGS. 30A and 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 to the user U.sub.n, illustrated in partial views;

(35) FIGS. 31A and 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 to the user U.sub.n, illustrated in partial views;

(36) FIGS. 32A and 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 to the user U.sub.n, illustrated in partial views;

(37) FIGS. 33A, 33B, and 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 to the user U.sub.n, illustrated in partial views;

(38) FIGS. 34A, 34B, and 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 to the user U.sub.n, illustrated in partial views;

(39) FIGS. 35A, 35B, and 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 to the user U.sub.n, illustrated in partial views;

(40) FIGS. 36A, 36B, and 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 to the user U.sub.n, illustrated in partial views;

(41) FIGS. 37A, 37B, 37C, and 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 to the user U.sub.n, illustrated in partial views;

(42) FIGS. 38A, 38B, 38C, and 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 to the user U.sub.n, illustrated in partial views;

(43) FIGS. 39A, 39B, and 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 to the user U.sub.n, illustrated in partial views;

(44) FIGS. 40A, 40B, 40C, 40D, 40E, 40F, 40G, 40H, 40I, 40J, 40K, 40L, and 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 to the user U.sub.n, illustrated in partial views;

(45) FIGS. 41A, 41B, 41C, 41D, 41E, and 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 to the user U.sub.n, illustrated in partial views;

(46) FIGS. 42A, 42B, 42C, 42D, 42E, 42F, 42G, 42H, 42I, 42J, 42K, 42L, 42M, 42N, and 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 to the user U.sub.n, illustrated in partial views;

(47) FIGS. 43A, 43B, 43C, 43D, 43E, 43F, 43G, 43H, 43I, 43J, 43K, 43L, 43M, 43N, and 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 to the user U.sub.n, illustrated in partial views;

(48) FIGS. 44A, 44B, and 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 to the user U.sub.n, illustrated in partial views;

(49) FIGS. 45A, 45B, and 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 to the user U.sub.n, illustrated in partial views;

(50) FIGS. 46A, 46B, 46C, 46D, and 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 to the user U.sub.n, illustrated in partial views;

(51) FIGS. 47A, 47B, and 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 to the user U.sub.n, illustrated in partial views;

(52) FIGS. 48A, 48B, 48C, and 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 to the user U.sub.n, illustrated in partial views;

(53) FIGS. 49A, 49B, 49C, 49D, 49E, 49F, 49G, 49H, and 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 to the user U.sub.n, illustrated in partial views;

(54) FIGS. 50A, 50B, 50C, 50D, 50E, 50F, 50G, 50H, 50I, 50J, and 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 to the user U.sub.n, illustrated in partial views;

(55) FIGS. 51A, 51B, 51C, 51D, 51E, 51F, and 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 to the user U.sub.n, illustrated in partial views;

(56) FIGS. 52A, 52B, and 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 to the user U.sub.n, illustrated in partial views;

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

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

(59) 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, through the server PS;

(60) 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;

(61) 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 through the server PS;

(62) 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;

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

(64) 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;

(65) 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;

(66) 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;

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

(68) 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;

(69) 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;

(70) 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;

(71) 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 with optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr, which may be addressed/pointed with pointer/address PP.sub.nm1;

(72) 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 with the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr, which may be addressed/pointed with the pointer/address PP.sub.nm2;

(73) 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 with the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr, which may be addressed/pointed with the pointer/address PP.sub.nmr;

(74) 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;

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

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

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

(78) 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;

(79) 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;

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

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

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

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

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

(85) 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;

(86) 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;

(87) 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;

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

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

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

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

(92) 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;

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

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

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

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

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

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

(99) 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;

(100) 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;

(101) 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;

(102) 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;

(103) 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;

(104) 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 with the query pointer/address group QG.sub.nz;

(105) 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 with the query pointer/address group QG.sub.nz;

(106) 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 with the query pointer/address group QG.sub.nz;

(107) 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;

(108) 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;

(109) 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;

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

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

(112) 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;

(113) 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 into the addressable response information group RG.sub.nm from the optional entity body RH.sub.nm of FIG. 105;

(114) 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 into the addressable individual information group LG.sub.nmr;

(115) 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 into the addressable response information group RG.sub.nm from the optional entity body RH.sub.nm;

(116) FIG. 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 into certain typical ones of the typical service and/or information response forms IS.sub.n of FIGS. 27A-52C, inclusive;

(117) FIG. 110 is 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 into certain typical ones of the typical service and/or information response forms IS.sub.n of FIGS. 27A-52C, inclusive;

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

(119) FIGS. 112A, 112B, 112C, 112D, 112E, 112F, 112G, and 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 to the user U.sub.n, illustrated in partial views;

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

(121) FIGS. 114A, 114B, 114C, 114D, 114E, 114F, 114G, and 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 to the user U.sub.n, illustrated in partial views;

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

(123) FIGS. 116A, 116B, 116C, 116D, 116E, 116F, 116G, and 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 to the user U.sub.n, illustrated in partial views;

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

(125) FIGS. 118A, 118B, 118C, 118D, 118E, 118F, 118G, and 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 to the user U.sub.n, illustrated in partial views;

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

(127) FIGS. 120A, 120B, 120C, 120D, 120E, 120F, 120G, and 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 to the user U.sub.n, illustrated in partial views;

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

(129) FIGS. 122A, 122B, 122C, 122D, 122E, 122F, 122G, and 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 to the user U.sub.n, and an order entry form OF.sub.n, which the user U.sub.n may use to enter an order, illustrated in partial views;

(130) FIGS. 123A, 123B, 123C, 123D, 123E, 123F, 123G, and 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 to the user U.sub.n, and the order entry form OF.sub.n, which the user U.sub.n may use to enter the order, of FIGS. 114A-114H, with typical order information entered therein, illustrated in partial views;

(131) FIGS. 124A and 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 to the user U.sub.n, and the order entry form OF.sub.n, which the user U.sub.n may use to enter the order, of FIGS. 114A-114H, with the typical order information entered therein, as shown in FIGS. 123A-123H, illustrated in partial views;

(132) FIGS. 125A and 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 to the user U.sub.n, and the order entry form OF.sub.n, which the user U.sub.n may use to enter the order, of FIGS. 114A-114H, with the typical order information entered therein, as shown in FIGS. 123A-123H, or which the user U.sub.n may enter through the typical preview form of the order OP.sub.n of FIGS. 124A and 124B, illustrated in partial views;

(133) FIGS. 126A and 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 to the user U.sub.n, and the order entry form OF.sub.n, which the user U.sub.n may use to enter the order, of FIGS. 114A-114H, with the typical order information entered therein, as shown in FIGS. 123A-123H, or which the user U.sub.n may enter through the typical preview form of the order OP.sub.n of FIGS. 124A and 124B, illustrated in partial views;

(134) FIGS. 127A and 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 and 126B, illustrated in partial views;

(135) FIGS. 128A, 128B, and 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 and 126B, illustrated in partial views;

(136) FIGS. 129A, 129B, and 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 and 126B, illustrated in partial views;

(137) FIGS. 130A and 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 and 126B, illustrated in partial views;

(138) FIGS. 131A and 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 and 126B, illustrated in partial views;

(139) FIGS. 132A and 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 and 126B, illustrated in partial views;

(140) 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;

(141) 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;

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

(143) 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 therethrough;

(144) 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 therethrough;

(145) 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 therethrough;

(146) 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 therethrough;

(147) 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 therethrough;

(148) 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 therethrough;

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

(150) FIGS. 143A, 143B, 143C, 143D, 143E, 143F, 143G, and 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 to the user U.sub.n, illustrated in partial views;

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

(152) FIGS. 145A, 145B, 145C, 145D, 145E, 145F, and 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 to the user U.sub.n, illustrated in partial views;

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

(154) FIGS. 147A, 147B, 147C, 147D, 147E, 147F, and 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 to the user U.sub.n, illustrated in partial views.

(155) FIG. 148 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;

(156) FIG. 149 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 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;

(157) FIG. 150 is a schematic representation of a particular service and/or information group G.sub.n associated with a typical securities transaction, showing query information groups GI.sub.n1 . . . GI.sub.nz represented as a plurality of order books OB.sub.n1 . . . OB.sub.nz at the user interface I.sub.n for a plurality of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies; and

(158) FIG. 151 is a schematic representation of a particular service and/or information group G.sub.n associated with a typical securities transaction, showing the query information group GI.sub.nz represented as the order book OB.sub.nz at the user interface I.sub.n for a security, stock, financial product, financial instrument, commodity, and/or currency.

DESCRIPTION

(159) The preferred embodiments of the present invention will be described with reference to FIGS. 1-151 of the drawings. Identical elements in the various figures are identified with the same reference alphanumerics.

(160) I. System

(161) A. Overview

(162) FIGS. 1 and 2 show a client-server multitasking system 10 of the present invention, having requestors 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) through the corresponding user interfaces I.sub.1 . . . I.sub.n (14).

(163) 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) into 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.

(164) 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) to 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.

(165) Each of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) may be communicated to 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).

(166) 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.

(167) 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).

(168) 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).

(169) 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).

(170) Each of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) may, thus, be communicated from 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 from the server PS (18) and/or from the corresponding clients C.sub.1 . . . C.sub.n (16) to the servers S.sub.1 . . . 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.

(171) 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).

(172) 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.1 . . . IR.sub.n (34) to the corresponding clients C.sub.1 . . . C.sub.n (16).

(173) 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) to 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) to 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.

(174) B. Typical Service and/or Information Entry Request Forms

(175) 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 into 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 into 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).

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

(177) 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).

(178) 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.nm (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.

(179) 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 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 “URL's per Search Engine”, rather than 10 “URL's per Search Engine”, as instructed in FIG. 11.

(180) 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”.

(181) 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).

(182) 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”.

(183) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) of FIG. 15 have “Separate”, which 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) 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.

(184) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) “Interleaved” of FIGS. 11-14 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 information and/or services in the responses R.sub.n1 . . . R.sub.nm (32) to be interleaved one with the other (or alternating one with the other) into 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) in 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 with the responses R.sub.n1 . . . R.sub.nm (32) from the servers S.sub.1 . . . S.sub.z (20). The “Interleaved” information and/or services may typically be incorporated into 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 in the responses R.sub.n1 . . . R.sub.nm (32) communicated from the servers S.sub.1 . . . S.sub.z (20). However, other sorting/grouping criteria may optionally be used, as will be discussed later.

(185) 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”.

(186) 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 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) “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, in 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 in 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).

(187) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) have 25 “URL's per Search Engine”, which 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 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”.

(188) 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 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 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”.

(189) 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).

(190) 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).

(191) 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”.

(192) 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”.

(193) 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).

(194) 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).

(195) 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 (52).

(196) 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).

(197) FIG. 26 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 a single typical one of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) as “weather”.

(198) The typical ones of the 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) shown in FIG. 11-26 are typical examples of the 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), a much larger variety of which is possible. Typical queries QQ.sub.n1 . . . QQ.sub.nm (53), typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) in the typical ones of the 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) shown in FIG. 11-26 are typical examples for illustrative purposes, and are not intended to limit the substantially infinite variety of the queries QQ.sub.n1 . . . QQ.sub.nm (53), the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) that may be entered into the service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38), to derive the 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). Likewise, names and/or links and/or other information are incorporated into the typical ones of the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230) shown in FIGS. 11-26 for illustrative purposes, and are not intended to limit the large variety of the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230) and the names and/or links and/or information that are possible, and that may be incorporated into the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230) at the user interfaces I.sub.1 . . . I.sub.n (14).

(199) Any ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), any values within the ranges allowable for the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and any values allowable for the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) may be incorporated into the 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) of FIGS. 5A, 5B, and 6-10, which the users U.sub.1 . . . U.sub.n (12) enter to complete the typical ones of the 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) of FIGS. 11-26

(200) Any values within the ranges allowable for “Search Engine Results”; “URL's per Search Engine”; “URL Details”; “Timeout (seconds) per Search Engine”; “Page”; “Searches per Group”; and “Group” may be incorporated into the typical ones of service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38) at the user interfaces I.sub.1 . . . I.sub.n (14) of FIGS. 5A, 5B, and 6-10, which the users U.sub.1 . . . U.sub.n (12) enter to complete the typical ones of the 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) of FIGS. 11-26.

(201) The users U.sub.1 . . . U.sub.n (12), for example, may enter: the typical queries QQ.sub.n1 . . . QQ.sub.nm (53); any values within the ranges allowable for the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54); and any values allowable for the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), such as, for example, any allowable “Search Engine Results”; “URL's per Search Engine”; “URL Details”; “Timeout (seconds) per Search Engine”; “Page”; “Searches per Group”; and “Group” into the 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) of FIGS. 5A, 5B, and 6-10, which the users U.sub.1 . . . U.sub.n (12) enter to complete the typical ones of the 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). The typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), may then be communicated to the corresponding ones of the users U.sub.1 . . . U.sub.n (12), accordingly. FIGS. 27A-52C, inclusive, show typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as the typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), which may be communicated to the corresponding ones of the users U.sub.1 . . . U.sub.n (12). The scope of the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, however, is not limited to such values. Use of such values herein is meant only for illustrative purposes, in teaching certain aspects of the multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104 by example.

(202) D. Typical Service and/or Information Response Forms

(203) FIGS. 27A-52C, inclusive, show typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), which may be communicated to the corresponding ones of the users U.sub.1 . . . U.sub.n (12). A typical particular one of the user responses UR.sub.1 . . . UR.sub.n (37), as a particular typical one of the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the particular one of the user interfaces I.sub.1 . . . I.sub.n (14) may hereinafter be designated as the 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).

(204) FIGS. 27A-52C, inclusive, also show information in each of 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), pertaining to the “Current Group”, the “Previous Group”, if appropriate, the “Next Group”, if appropriate, and each “Group” by alphanumerics. FIGS. 27A-52C, inclusive, also show information in each of the typical ones of the user responses UR.sub.n (37), as the typical service and/or information response forms IS.sub.n (39) at the user interfaces I.sub.n (14), pertaining to links to additional selections, and/or links to previous selections, if appropriate, and/or links to future selections, if appropriate, that may be made by pointing to and clicking on the selections to be made.

(205) FIGS. 27A-29C, inclusive, show 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), with reference to FIG. 11, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group I, Group II, and Group III, respectively.

(206) The user U.sub.n (12) may optionally select Group II, and/or Group III from the typical one of the 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) of FIGS. 27A-27C, and/or Group I and/or Group III at the user interface I.sub.n (14) of FIGS. 28A-28C, and/or Group I, and/or Group II at the user interface I.sub.n (14) of FIGS. 29A-29C. The user U.sub.n (12) may also select Group I, and/or Group II, and/or Group III by entering such into the typical one of the service and/or information entry request form IE.sub.n (38) at the user interfaces I.sub.1 . . . I.sub.n (14), and completing the typical completed service and/or information entry request form IF.sub.n (230), at the user interface I.sub.n (14) with the appropriate selections to be made.

(207) The user U.sub.n (12) may also make other selections by entering such into the typical one of the service and/or information entry request form IE.sub.n (38) at the user interfaces I.sub.1 . . . I.sub.n (14), and completing the typical completed service and/or information entry request form IF.sub.n (230), at the user interface I.sub.n (14) with the appropriate selections to be made, and/or by making such selections through 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 user U.sub.n (12) may typically make selections by pointing and clicking on the appropriate selections and/or by entering the desired information. Such information may be entered by any suitable means, including but not limited to mouse, keyboard entry, audible entry, and/or other suitable means.

(208) FIGS. 27A-29C, inclusive, show 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), having the service and/or information group G.sub.n (35) having the addressable query information groups GI.sub.n1 . . . GI.sub.n (63) therein, the labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) in the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), the additional request links SL.sub.n1 . . . SL.sub.nw (71), the optional service and/or information entry request form IE.sub.n (38), and other information and/or services therein, resulting from the 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).

(209) FIGS. 27A-29C, inclusive, show 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), resulting from the typical ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53), “Cat”, “Mouse”, and “Dog”, the same ones of the typical queries QQ.sub.n1 . . . QQ.sub.n3 (53) and QQ.sub.n9 (53) being “Cat”, other same ones of the typical queries QQ.sub.n4 (53) and QQ.sub.n7 (53) being “Mouse”, but different from “Cat”, and other same ones of the typical queries QQ.sub.n5, QQ.sub.n6 (53), and QQ.sub.n8 (53) being “Dog”, but different from “Cat” and/or “Mouse”, the typical ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53), “Cat”, “Dog”, and “Mouse”, being different one from the other.

(210) The typical same ones of the typical queries QQ.sub.n1 . . . QQ.sub.n3 (53) as “Cat” are incorporated into the addressable query information groups GI.sub.n1 (63) of Group I.

(211) The typical one of the queries QQ.sub.n4 (53) as “Mouse” is incorporated into the addressable query information groups GI.sub.n1 (63) of Group II. The other same ones of the typical queries QQ.sub.n5 and QQ.sub.n6 (53) as “Dog are incorporated into the addressable query information groups GI.sub.n2 (63) of Group II.

(212) The typical one of the queries QQ.sub.n7 (53) as “Mouse” is incorporated into the addressable query information groups GI.sub.n1 (63) of Group III. The typical one of the queries QQ.sub.n8 (53) as “Dog” is incorporated into the addressable query information groups GI.sub.n2 (63) of Group III. The typical one of the queries QQ.sub.n9 (53) as “Cat” is incorporated into the addressable query information groups GI.sub.n3 (63) of Group III.

(213) FIGS. 27A-29C, inclusive, show 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), with reference to FIG. 11 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “3”; and “Group” as I, II, and III, respectively, for FIGS. 27A-29C, inclusive.

(214) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) “URL's per Search Engine” as “10” 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 substantially “10” ones of the typical labelled individual information groups LL.sub.n11 . . . LL.sub.mzu (86) per each one of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) in the typical “Current Group”, retrieved from the responses R.sub.n1 . . . R.sub.nm (32). In this case, the typical labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) may be “Uniform Resource Locators”, or “URL's” and/or other services and/or information associated therewith.

(215) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) “Searches per Group” as “3” 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 “3 Searches per Group” for the group selected, which is designated in the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) having “Group” as “1”.

(216) “Group I”, which is the “Current Group: I”, has the first three searches (“Searches per Group” designated as “3”), i.e., Search 1, Search 2, and Search 3, having the typical queries QQ.sub.n1 . . . QQ.sub.n3 (53) of “Cat”, “Cat”, and “Cat” and the typical server addresses AQ.sub.n1 . . . AQ.sub.n3 (54) of WebCrawler®, Altavista®, and Lycos®.

(217) The “Next Group: II” and/or the “Group: III” may be selected from 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). If the “Next Group: II” is selected, then Search 4, Search 5, and Search 6, having the typical queries QQ.sub.n4 . . . QQ.sub.n6 (53) of “Mouse”, “Dog”, and “Dog” and the typical server addresses AQ.sub.n4 . . . AQ.sub.n6 (54) of Infoseek®, Excite®, and Yahoo® are selected and returned as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14). If the “Group: III” is selected, then Search 7, Search 8, and Search 9, having the typical queries QQ.sub.n7 . . . QQ.sub.n9 (53) of “Mouse”, “Dog”, and “Cat” and the typical server addresses AQ.sub.n7 . . . AQ.sub.n9 (54) of LookSmart®, HotBot®, and Dejanews® are selected and returned as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14).

(218) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) having “URL's per Search Engine” as “10” and “Searches per Group” as “3”, then returns substantially “10 URL's per Search Engine” multiplied by “3 Searches per Group”, which is substantially “30 URL's per Group”, and/or other services and/or information associated therewith, returned in the “Current Group”.

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

(220) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) “Page” as “1” 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 the first “10 URL's per Search Engine” which is substantially the first “30 URL's per Group”, and/or other services and/or information associated therewith, in the “Current Group”.

(221) The “Next Page” and/or other pages may be selected, which in this typical case may be Pages 1-25, from the typical user response 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). If the “Next Page” is selected, then the next“10 URL's per Search Engine” which is substantially the next “30 URL's per Group”, and/or other services and/or information associated therewith, in the “Current Group” are selected and returned as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14). If, for example, the third “Page′ is selected, then the third “10 URL's per Search Engine” which is substantially the third “30 URL's per Group”, and/or other services and/or information associated therewith, in the “Current Group” are selected and returned as the typical service and/or information response form IS.sub.n (39) at the user interface I.sub.n (14).

(222) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) of “Search Engine Results” as “Interleave” 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 ones of the typical labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) and/or other services and/or information associated with the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) and the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) in the typical “Current Group”, portions of which have been retrieved from the responses R.sub.n1 . . . R.sub.nm (32), interleaved one with the other (or alternating one with the other) in the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63). The “Interleaved” information and/or services may typically be incorporated into the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) in the “Current Group” in substantially the same sequence as the information and/or services are in the responses R.sub.n1 . . . R.sub.nm (32) communicated from the servers S.sub.1 . . . S.sub.z (20). However, other sorting/grouping criteria may optionally be used, as will be discussed later. In this case, the typical labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) may be “Uniform Resource Locators”, or “URL's” and/or other services and/or information associated therewith.

(223) “Separate” may be selected from 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), 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) incorporated into the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) in the “Current Group”.

(224) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) “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 the typical labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) showing descriptions and/or other information and/or services, in addition to links, and/or URL's in the typical ones of the user responses 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).

(225) “List” may be selected from 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), 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) typically showing only links to URL's and/or other links in 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).

(226) 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).

(227) If the time it takes to retrieve information from certain ones of the servers S.sub.1 . . . S.sub.z (20) having the typical ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) at the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) is greater than the “Timeout” selected, then the client C.sub.n (16) and/or the server PS (18) typically incorporate a message and/or messages, such as “No Results Found for ‘Query ‘x” at ‘Server Address ‘y” within “z” seconds!” for each of the non-responding certain ones of the servers S.sub.1 . . . S.sub.z (20), as shown later in FIGS. 44A-44C. Information and/or services only from those ones of the servers S.sub.1 . . . S.sub.z (20) responding within the “Timeout” period are then incorporated into 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).

(228) FIGS. 30A-32B, inclusive, show 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), with reference to FIG. 12, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group I, Group II, and Group III, respectively.

(229) FIGS. 30A-32B, inclusive, show 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), having the service and/or information group G.sub.n (35) having the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) therein, the labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) in the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), the additional request links SL.sub.n1 . . . SL.sub.nw (71), the optional service and/or information entry request form IE.sub.n (38), and other information and/or services therein, resulting from the same and different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), and the same and 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), rather than results just from different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) as in FIGS. 27A-29C, inclusive.

(230) FIGS. 30A-32B, inclusive, show 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), resulting from the typical ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53), “Cat”, “Dog”, and “Mouse”, the same ones of the typical queries QQ.sub.n1, QQ.sub.n3 (53), and QQ.sub.n9 (53) being “Cat”, other same ones of the typical queries QQ.sub.n2 (53), QQ.sub.n5 (53), QQ.sub.n6 (53), and QQ.sub.n8 (53) being “Dog”, but different from “Cat”, and other same ones of the typical queries QQ.sub.n4 and QQ.sub.n7 (53) being “Mouse”, but different from “Cat” and/or “Dog”, the typical ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53), “Cat”, “Dog”, and “Mouse”, being different one from the other.

(231) FIGS. 30A-32B, inclusive, also show 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), resulting from the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), HotBot®, WebCrawler®, Yahoo®, LookSmart®, and Dejanews®, the same ones of the typical server addresses AQ.sub.n1 and AQ.sub.n2 (54) being HotBot®, other same ones of the typical server addresses AQ.sub.n3 . . . AQ.sub.n5 (54), being WebCrawler®, but different from HotBot®, another one of the server addresses AQ.sub.n6 (54), being Yahoo®, but different from HotBot® and/or WebCrawler®, another one of the server addresses AQ.sub.n7 (54), being LookSmart®, but different from HotBot® and/or WebCrawler® and/or Yahoo®, and other same ones of the typical server addresses AQ.sub.n8 (54) and QQ.sub.n9 (54) being Dejanews®, but different from HotBot® and/or WebCrawler® and/or Yahoo® and/or LookSmart®, the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), HotBot®, WebCrawler®, Yahoo®, LookSmart®, and Dejanews®, being different one from the other.

(232) The typical same ones of the typical queries QQ.sub.n1 and QQ.sub.n3 (53) as “Cat” are incorporated into the addressable query information groups GI.sub.n1 (63) of Group I. The typical one of the queries QQ.sub.n2 (53) as “Cat” is incorporated into the addressable query information groups GI.sub.n2 (63) of Group II.

(233) The typical one of the queries QQ.sub.n4 (53) as “Mouse” is incorporated into the addressable query information groups GI.sub.n1 (63) of Group II. The other same ones of the typical queries QQ.sub.n5 and QQ.sub.n6 (53) as “Dog are incorporated into the addressable query information groups GI.sub.n2 (63) of Group II.

(234) The typical one of the queries QQ.sub.n7 (53) as “Mouse” is incorporated into the addressable query information groups GI.sub.n1 (63) of Group III. The typical one of the queries QQ.sub.n8 (53) as “Dog” is incorporated into the addressable query information groups GI.sub.n2 (63) of Group III. The typical one of the queries QQ.sub.n9 (53) as “Cat” is incorporated into the addressable query information groups GI.sub.n3 (63) of Group III.

(235) FIGS. 30A-32B, inclusive, show 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), with reference to FIG. 12 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “5”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “5”; and “Group” as I, II, and III, respectively, for FIGS. 30A-32B, inclusive.

(236) Now again, FIGS. 30A-32B, inclusive, show 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), resulting from the same and different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), the same and 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), but which also result from the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) having 5 “URL's per Search Engine”, which 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 “URL's per Search Engine”, rather than 10 “URL's per Search Engine”, as in FIGS. 27A-29C, inclusive.

(237) FIGS. 33A-33C show a typical one of the 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), with reference to FIG. 13, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group I, having the typical ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) as “Big Elephants”. The user U.sub.n (12) may optionally select Group II, and/or Group III from the typical one of the 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) of FIGS. 33A-33C.

(238) FIGS. 33A-33C show the typical one of the user response 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), with reference to FIG. 13 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “3”; and “Group” as I. Groups I and/or II may be selected from the typical one of the user response 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) of FIGS. 33A-33C.

(239) FIGS. 34A-36C, inclusive, show 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), with reference to FIGS. 14A, 14B, and 14C, respectively, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group I, Group II, and Group III, respectively. FIGS. 34A-36C, inclusive, show the results “Interleaved”. Typical ones of links, prices, descriptions, savings, and shipping schedules are indicated for products in Group I. The prices may be compared, for example, one with the other for the same and/or different items, shipping schedules compared, and a decision can be made as to which items to order, as a result of the information provided in the typical one of the user responses 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). Typical similar items may have the same and/or similar titles, such as for example in book titles, but publication dates, for example, and/or editions may be the same and/or different, and shipping schedules may be the same and/or different. Prices, and cost savings may be traded off against shipping schedules, packaging (i.e., for example, hardcover and/or soft cover), author, publisher, for example, and/or other factors important to the user U.sub.n (12). The user U.sub.n (12) may select the items and/or items to order from such information that the user U.sub.n (12) considers to be important. The user U.sub.n (12) may place the order and/or orders directly through the links and/or URL's in 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 user U.sub.n (12) may additionally and/or alternatively collect the order and/or orders in a shopping cart and/or shopping carts associated with the typical ones of the user responses 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), and place the order and/or orders through the client C.sub.n (16) and/or the server PS (18).

(240) Now again, FIGS. 34A-36C, inclusive, show 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), having the service and/or information group G.sub.n (35) having the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) therein, the labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) in the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), the additional request links SL.sub.n1 . . . SL.sub.nw (71), the optional service and/or information entry request form IE.sub.n (38), and other information and/or services therein, resulting from the 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.nm . . . 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.

(241) FIGS. 34A-36C, inclusive, show 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), with reference to FIGS. 14A, 14B, and 14C having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “5”; “Page” as “1”; “Searches per Group as “3”; and “Group” as I, II, and III, respectively, for FIGS. 34A-36C, inclusive.

(242) Now again, 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. 27A-33C, inclusive. 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).

(243) FIGS. 37A-39C, inclusive, show 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), with reference to FIG. 15, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group I, Group II, and Group III, respectively. Links, Prices, descriptions, savings, and shipping schedules are indicated for products in Group I, and Group II. FIGS. 38A-38D show the results “Separately” for Group II, and FIGS. 39A-39C show the results “Interleaved” for Group II. Links, Prices, descriptions, savings, and shipping schedules are indicated for products in Groups I and II in FIGS. 37A-39C, inclusive.

(244) FIGS. 37A-39C, inclusive, show 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), with reference to FIG. 15 having: “Search Engine Results” as “Separate”; “URL's per Search Engine” as “8”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “1”; “Page” as “1”; “Searches per Group as “5”; and “Group” as I, II, and III, respectively for FIGS. 37A-39C, inclusive.

(245) Now again, the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) have “Separate”, which 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) 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 in FIGS. 27A-36C, inclusive.

(246) FIGS. 40A-40M show a typical one of the 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), with reference to FIG. 16, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into a single Group.

(247) FIGS. 40A-40M show the typical one of the user response 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), with reference to FIG. 16 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “25”; “URL Details” as “List”; “Timeout (seconds) per Search Engine” as “2”; “Page” as “3”; “Searches per Group as “9”; and “Group” as I. Groups I and/or II may be selected from the typical one of the user response 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) of FIGS. 40A-40M.

(248) Now again, 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, in 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), as in FIGS. 27A-39C, inclusive, 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 and/or URL's in 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), as in FIGS. 40A-40M.

(249) FIGS. 41A-41F show a typical one of the 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), with reference to FIG. 17, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group II.

(250) FIGS. 41A-41F show the typical one of the user response 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), with reference to FIG. 17 having: “Search Engine Results” as “Separate”; “URL's per Search Engine” as “18”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “1”; “Page” as “2”; “Searches per Group as “4”; and “Group” as “2”. Groups I and/or III may be selected from the typical one of the user response 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) of FIGS. 41A-41F.

(251) FIGS. 42A-42O show a typical one of the 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), with reference to FIG. 18, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into a single Group.

(252) FIGS. 42A-42O show the typical one of the user response 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), with reference to FIG. 18 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “25”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “5”; “Page” as “1”; “Searches per Group as “9”; and “Group” as “1”.

(253) FIGS. 43A-43O show a typical one of the 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), with reference to FIG. 19, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into a single Group.

(254) FIGS. 43A-43O show the typical one of the user response 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), with reference to FIG. 19 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “25”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “9”; and “Group” as “1”.

(255) FIGS. 44A-44C show a typical one of the 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), with reference to FIG. 20, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group I. FIGS. 44A-44C also show the results of a “Timeout” occurring.

(256) FIGS. 44A-44C show the typical one of the user response 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), with reference to FIG. 20 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “3”; and “Group” as I. Groups I and/or II may be selected from the typical one of the user response 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) of FIGS. 44A-44C.

(257) FIGS. 45A-45C show a typical one of the 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), with reference to FIG. 21, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group I.

(258) FIGS. 45A-45C show the typical one of the user response 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), with reference to FIG. 21 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “3”; and “Group” as I. Groups I and/or II may be selected from the typical one of the user response 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) of FIGS. 45A-45C.

(259) FIGS. 46A-46E show a typical one of the 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), with reference to FIG. 22, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group I. FIGS. 46A-46E also show the links/advertisements/images automatically inserted into the typical one of the user response 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), which may be associated with the typical queries QQ.sub.n1 . . . QQ.sub.nm (53). In the typical case shown in FIGS. 46A-46E, links/advertisements/images associated with the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) of “sports” and “television” have been automatically inserted into the typical one of the 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).

(260) FIGS. 46A-46E show the typical one of the user response 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), with reference to FIG. 22 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “15”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “5”; and “Group” as “1”. Next Group: II may be selected from the typical one of the user response 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) of FIGS. 46A-46E.

(261) FIGS. 47A-47C and 48A-48D show typical ones of the user response 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), with reference to FIG. 23, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group I. FIGS. 47A-47C and 48A-48D also show the results of a full text search of the optional database 41 and/or the optional database 42, which may be associated with the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), and which additionally and/or alternatively may function as an internal search engine. The full text search results are incorporated from the additional optional responses RA.sub.n1 . . . RA.sub.nm (40). The results of the full text search of the optional database 41 and/or the optional database 42 may be additionally and/or alternatively automatically inserted into the typical one of the 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 addition to the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) at the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54). In the typical case shown in FIGS. 47A-47C and 48A-48D, full text search results associated with the typical query QQ.sub.n1 . . . QQ.sub.nm (53) of “weather” have been automatically inserted into 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), in addition to the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) at the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54). The typical full text search results start and end with “Hotlist: Weather Science” in FIGS. 47A-47C. The typical full text search results start with “Hotlist: Weather Science” and end with “Search for: ‘weather’ in FIGS. 48A-48D.

(262) FIGS. 47A-47C and 48A-48D show the typical one of the user response 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), with reference to FIG. 23 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “3”; and “Group” as “1”. Next Group: I and/or Group: III may be selected from the typical one of the user response 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) of FIGS. 47A-47C and 48A-48D.

(263) FIGS. 49A-49I show a typical one of the 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), with reference to FIG. 24, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group I. FIGS. 49A-49I also show the typical results of the server PS (18) and/or the client C.sub.n (16) automatically optionally spidering the sites obtained as a result of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) at the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and incorporating the spidered results into the optional database 41 and/or the optional database 42. The spidered results incorporated into the optional database 41 and/or the optional database 42 may be searched as in FIGS. 47A-47C and 48A-48D with reference to FIG. 23 and/or based upon other ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) at the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the full text search results may be obtained from the additional optional responses RA.sub.n1 . . . RA.sub.nm (40).

(264) FIGS. 49A-49I also show the typical one of the user response 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), with reference to FIG. 24 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “3”; and “Group” as “1”. Next Group: I and/or Group: III may be selected from the typical one of the user response 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) of FIGS. 49A-49I.

(265) FIGS. 50A-50K show a typical one of the 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), with reference to FIG. 25, having information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) incorporated therein, and incorporated into Group I. FIGS. 50A-50K also show the typical results of the server PS (18) and/or the client C.sub.n (16) semi-automatically optionally spidering the sites obtained as a result of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) at the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and incorporating the spidered results into the optional database 41 and/or the optional database 42. The spidered results incorporated into the optional database 41 and/or the optional database 42 may also be searched as in FIGS. 47A-47C and 48A-48D with reference to FIG. 23 and/or based upon other ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) at the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the full text search results may be obtained from the additional optional responses RA.sub.n1 . . . RA.sub.nm (40).

(266) The user U.sub.n (12) may optionally select those sites to be spidered and incorporated into the optional database 41 and/or the optional database 42, as in the typical one of the user response 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 FIGS. 50A-50K. FIGS. 51A-51G show the typical results of the server PS (18) and/or the client C.sub.n (16) optionally spidering the sites obtained as a result of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) at the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and input resulting from user selection of sites to be spidered from FIGS. 50A-50K, and incorporating the spidered results into the optional database 41 and/or the optional database 42.

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

(268) FIGS. 50A-50K also show the typical one of the user response 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), with reference to FIG. 25 having: “Search Engine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as “3”; “Page” as “1”; “Searches per Group as “3”; and “Group” as “1”. Next Group: I and/or Group: III may be selected from the typical one of the user response 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) of FIGS. 50A-50K.

(269) FIGS. 52A-52C show a typical one of the 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), with reference to FIG. 26, having information and/or services from the additional optional responses RA.sub.n1 . . . RA.sub.nm (40). FIGS. 52A-52C show the results solely of a full text search of the optional database 41 and/or the optional database 42, which may be associated with the typical queries QQ.sub.n1 . . . QQ.sub.nm (53). The full text search results are incorporated from the additional optional responses RA.sub.n1 . . . RA.sub.nm (40). The typical full text search results start with “Hotlist: Weather Science” and end with “High Plains Climate Center Home Page” in FIGS. 52A-52C.

(270) The typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14) shown in FIGS. 27A-52C, inclusive, are typical examples of the user responses UR.sub.1 . . . UR.sub.n (37), as typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), a much larger variety of which is possible. FIGS. 27A-52C, inclusive, illustrate typical examples of typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14) to the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) having been entered into the typical ones of the 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) shown in FIGS. 11-26.

(271) The typical examples of the typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14) are for illustrative purposes, and are not intended to limit the substantially infinite variety of the user responses UR.sub.1 . . . UR.sub.n (37), as the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), the queries QQ.sub.n1 . . . QQ.sub.nm (53), the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) that may be entered into the service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38), to derive the to the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230), and which result in the user responses UR.sub.1 . . . UR.sub.n (37), as the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14). Likewise, names and/or links and/or other information are incorporated into the typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), shown in FIGS. 27A-52C, inclusive, for illustrative purposes, and are not intended to limit the large variety of the user responses UR.sub.1 . . . UR.sub.n (37), as the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), and the names and/or links and/or information that are possible, and that may be incorporated into the user responses UR.sub.1 . . . UR.sub.n (37), as the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14).

(272) E. Other Typical Service and/or Information Entry Request Forms, Other Typical Completed Service and/or Information Entry Request Forms, and Other Typical Service and/or Information Response Forms

(273) FIG. 111 shows another 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). 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 Amazon®, Borders®, and BarnesandNoble®, which are different one from the other, and which are also different from Google®. The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) having “URL's per Search Engine” as “10” and “Searches per Group” as “9”, then returns substantially “10 URL's per Search Engine” multiplied by “9 Searches per Group”, which is substantially “90 URL's per Group”, and/or other services and/or information associated therewith, returned in the “Current Group”, and Search Engine Results as “Interleaved”. In this case, however, order entry boxes 402 are also returned, which allow the user U.sub.1 (12) to order services, merchandise, information, other items, and/or objects through the user interface I.sub.1 (14), as shown in FIGS. 112A-112H. The user U.sub.1 (12) can place orders with sites that support such services and also obtain information on queried subjects from sites that support returning information and/or services.

(274) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) “Interleaved” of FIG. 111 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 information and/or services in the responses R.sub.n1 . . . R.sub.nm (32) to be interleaved one with the other (or alternating one with the other) in 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) in 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 with the responses R.sub.n1 . . . R.sub.nm (32) from the servers S.sub.1 . . . S.sub.z (20). The “Interleaved” information and/or services may typically be incorporated into the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) in substantially the same sequence as the information and/or services in the responses R.sub.n1 . . . R.sub.nm (32) communicated from the servers S.sub.1 . . . S.sub.z (20). However, other sorting/grouping criteria may optionally be used, as will be discussed.

(275) FIG. 113 shows another 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), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Combined $[a-z]”.

(276) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) “Combined $[a-z]” of FIG. 113 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 information and/or services in the responses R.sub.n1 . . . R.sub.nm (32) to be sorted in ascending order first numerically, and then alphabetically, in the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63). Items having prices will be sorted numerically by price, with lowest price first. The labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) in the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) are grouped and sorted in ascending order one with the other and labelled and/or identified and associated correspondingly with the responses R.sub.n1 . . . R.sub.nm (32) from the servers S.sub.1 . . . S.sub.z (20). The “Combined $[a-z]” information and/or services may typically be incorporated into the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nm (63) in accordance with the “Combined $[a-z]” optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and communicated in the other 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 to the user U.sub.n, as shown in FIGS. 114A-114H.

(277) FIGS. 114A-114H also depict typical order boxes 402 of a typical order entry form OF.sub.n, which is communicated with the typical user response UR.sub.n, to enter quantities that the user U.sub.n may elect to order, as the typical service and/or information response form IS.sub.n at the user interface I.sub.n, which may be communicated to the user U.sub.n, which the user U.sub.n may use to enter an order.

(278) FIG. 115 shows another 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), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Combined $[z-a]”.

(279) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) “Combined $[z-a]” of FIG. 115 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 information and/or services in the responses R.sub.n1 . . . R.sub.nm (32) to be sorted in descending order first alphabetically, and then numerically, in the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63). Items having prices will be sorted numerically by price, with highest price first. The labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) in the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) are grouped and sorted in descending order one with the other and labelled and/or identified and associated correspondingly with the responses R.sub.n1 . . . R.sub.nm (32) from the servers S.sub.1 . . . S.sub.z (20). The “Combined $[z-a]” information and/or services may typically be incorporated into the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nm (63) in accordance with the “Combined $[z-a]” optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and communicated in the other 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 to the user U.sub.n, as shown in FIGS. 116A-116H.

(280) FIG. 117 shows another 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), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Separate”. The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) of FIG. 117 have “Separate”, which 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) 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, and communicated in the other 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 to the user U.sub.n, as shown in FIGS. 118A-118H.

(281) FIG. 119 shows another 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), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Separate $[a-z]”. The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) of FIG. 119 have “Separate $[a-z]”, which 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) in separate groups, sorted in ascending order first numerically, and then alphabetically, in the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), i.e., grouped by the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and communicated in the other 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 to the user U.sub.n, as shown in FIGS. 120A-120H. Items having prices will be sorted numerically by price, with lowest price first within each of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) groups.

(282) FIG. 121 shows another 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), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Separate $[z-a]”. The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) of FIG. 121 have “Separate $[z-a]”, which 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) in separate groups, sorted in descending order alphabetically, and then numerically, in the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), i.e., grouped by the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and communicated in the other 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 to the user U.sub.n, as shown in FIGS. 122A-122H. Items having prices will be sorted numerically by price, with highest price first within each of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) groups.

(283) 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 to the user U.sub.n, and the order entry form OF.sub.n, which the user U.sub.n may use to enter the order, of FIGS. 114A-114H, with typical order information entered therein.

(284) FIGS. 124A-124B depict a typical preview form of an order OP.sub.n, resulting from submission of the quantities to be ordered in order boxes 402 of the order entry form OF.sub.n of FIGS. 114A-114H, of the 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, with the typical order information entered therein, as shown in FIGS. 123A-123H.

(285) 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 to the user U.sub.n, and the order entry form OF.sub.n, which the user U.sub.n may use to enter the order, of FIGS. 114A-114H, with the typical order information entered therein, as shown in FIGS. 123A-123H, or which the user U.sub.n may enter through the typical preview form of the order OP.sub.n of FIGS. 124A-124B.

(286) 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 to the user U.sub.n, and the order entry form OF.sub.n, which the user U.sub.n may use to enter the order, of FIGS. 114A-114H, with the typical order information entered therein, as shown in FIGS. 123A-123H, or which the user U.sub.n may enter through the typical preview form of the order OP.sub.n of FIGS. 124A-124B.

(287) 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.

(288) The orders are also confirmed automatically by e-mail, with e-mailed confirmations being sent to the user U.sub.n (12), i.e., the buyer, seller, order fulfillment organization, with the total order being totaled, portions of the order being segregated and separated one from the other, and subtotaled, each segregated and subtotaled portion being directed to individual suppliers.

(289) 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. 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. 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, and FIGS. 131A-131B and 132A-132B depict a typical e-mail order placements EP.sub.n of other portions of the order, resulting from submission of the typical completed order placement form OL.sub.n of FIGS. 126A-126B.

(290) 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, which is substantially the same as the typical service and/or information entry request form IE.sub.n at the user interface I.sub.n of FIG. 111, except the typical service and/or information entry request form IE.sub.n at the user interface I.sub.n of FIG. 136 is adapted to allow 10 different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) and 10 different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) to be entered, whereas the typical service and/or information entry request form IE.sub.n at the user interface I.sub.n of FIG. 111 is adapted to allow 9 different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) and 9 different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) to be entered.

(291) 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, which is substantially the same as the typical service and/or information entry request form IE.sub.n at the user interface I.sub.n of FIG. 136, except the typical service and/or information entry request form IE.sub.n at the user interface I.sub.n of FIG. 137 is adapted to allow the 10 different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) and the 10 different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) to be entered, aligned vertically one with the other in pairs, in two rows predominantly horizontally adjacent one with the other, whereas the typical service and/or information entry request form IE.sub.n at the user interface I.sub.n of FIG. 136 is adapted to allow the 10 different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) and the 10 different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) to be entered, aligned horizontally one with the other in pairs adjacent one with the other in vertical rows.

(292) 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, which is substantially the same as the typical service and/or information entry request form IE.sub.n at the user interface I.sub.n of FIG. 137, except the typical service and/or information entry request form IE.sub.n at the user interface I.sub.n of FIG. 138 is adapted to allow 12 different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) and 12 different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) to be entered, whereas the typical service and/or information entry request form IE.sub.n at the user interface I.sub.n of FIG. 138 is adapted to allow 10 different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) and 10 different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) to be entered.

(293) FIGS. 139-141 depict yet other 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, which are substantially the same as the typical service and/or information entry request forms IE.sub.n at the user interface I.sub.n of FIGS. 6, 8, and 10.

(294) Each of the 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, of FIGS. 136-141 also have “Top Stories”, which are news stories, and are updated intermittently on a substantially routine basis.

(295) FIG. 142 shows another 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), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Separate $[a-z]”. The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) of FIG. 142 have “Separate $[a-z]”, which 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) in separate groups, sorted in ascending order first numerically, and then alphabetically, in the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), i.e., grouped by the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and communicated in the other 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 to the user U.sub.n, as shown in FIGS. 143A-143H. Items having prices will be sorted numerically by price, with lowest price first within each of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54) groups.

(296) FIG. 144 shows another 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), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Combined $[a-z]”.

(297) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) “Combined $[a-z]” of FIG. 144 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 information and/or services in the responses R.sub.n1 . . . R.sub.nm (32) to be sorted in ascending order first numerically, and then alphabetically, in the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63). Items having prices will be sorted numerically by price, with lowest price first. The labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) in the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) are grouped and sorted in ascending order one with the other and labelled and/or identified and associated correspondingly with the responses R.sub.n1 . . . R.sub.nm (32) from the servers S.sub.1 . . . S.sub.z (20). The “Combined $[a-z]” information and/or services may typically be incorporated into the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nm (63) in accordance with the “Combined $[a-z]” optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and communicated in the other 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 to the user U.sub.n, as shown in FIGS. 145A-145G.

(298) FIG. 146 shows yet another 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), with other sorting/grouping criteria selected, i.e., with Search Engine Results as “Combined $[a-z]”.

(299) The typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) “Combined $[a-z]” of FIG. 146 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 information and/or services in the responses R.sub.n1 . . . R.sub.nm (32) to be sorted in ascending order first numerically, and then alphabetically, in the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nz (63). Items having prices will be sorted numerically by price, with lowest price first. The labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86) in the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) are grouped and sorted in ascending order one with the other and labelled and/or identified and associated correspondingly with the responses R.sub.n1 . . . R.sub.nm (32) from the servers S.sub.1 . . . S.sub.z (20). The “Combined $[a-z]” information and/or services may typically be incorporated into the appropriate addressable query information groups GI.sub.n1 . . . GI.sub.nm (63) in accordance with the “Combined $[a-z]” optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and communicated in the other 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 to the user U.sub.n, as shown in FIGS. 147A-147G.

(300) Each of the typical service and/or information entry request forms 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 into, of FIGS. 1-147 may also have news stories, which may be updated intermittently on a substantially routine basis.

(301) The typical ones of the 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) shown in certain ones of the FIGS. 1-147 are typical examples of the 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), a much larger variety of which is possible. Typical queries QQ.sub.n1 . . . QQ.sub.nm (53), typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) in the typical ones of the 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) shown in certain ones of the FIGS. 1-147 are typical examples for illustrative purposes, and are not intended to limit the substantially infinite variety of the queries QQ.sub.n1 . . . QQ.sub.nm (53), the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) that may be entered into the service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38), to derive the 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). Likewise, names and/or links and/or other information incorporated in the typical ones of the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230) shown in certain ones of the FIGS. 1-147 are for illustrative purposes, and are not intended to limit the large variety of the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230) and the names and/or links and/or information that are possible, and that may be incorporated into the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230) at the user interfaces I.sub.1 . . . I.sub.n (14).

(302) Any ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53), any values within the ranges allowable for the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and any values allowable for the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) may be incorporated into the 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) shown in certain ones of the FIGS. 1-147, which the users U.sub.1 . . . U.sub.n (12) enter to complete the typical ones of the 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) of shown in certain ones of the FIGS. 1-147.

(303) Any values within the ranges allowable for “Search Engine Results”; “URL's per Search Engine”; “URL Details”; “Timeout (seconds) per Search Engine”; “Page”; “Searches per Group”; and “Group” may be incorporated into the typical ones of service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38) at the user interfaces I.sub.1 . . . I.sub.n (14) shown in certain ones of the FIGS. 1-147, which the users U.sub.1 . . . U.sub.n (12) enter to complete the typical ones of the 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) shown in certain ones of the FIGS. 1-147.

(304) The users U.sub.1 . . . U.sub.n (12), for example, may enter: the typical queries QQ.sub.n1 . . . QQ.sub.nm (53); any values within the ranges allowable for the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54); and any values allowable for the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), such as, for example, any allowable “Search Engine Results”; “URL's per Search Engine”; “URL Details”; “Timeout (seconds) per Search Engine”; “Page”; “Searches per Group”; and “Group” into the 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 shown in certain ones of the FIGS. 1-147, which the users U.sub.1 . . . U.sub.n (12) enter to complete the typical ones of the 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). The typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), may then be communicated to the corresponding ones of the users U.sub.1 . . . U.sub.n (12), accordingly. Certain ones of the FIGS. 1-147 show typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as the typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), which may be communicated to the corresponding ones of the users U.sub.1 . . . U.sub.n (12). The scope of the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, however, is not limited to such values. Use of such values herein is meant only for illustrative purposes, in teaching certain aspects of the multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104 by example.

(305) F. Optional Database

(306) The server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) may also incorporate corresponding additional optional responses RA.sub.11 . . . RA.sub.nm (40) into the service and/or information responses IR.sub.1 . . . IR.sub.n (34), which may be obtained by accessing optional databases 41 and/or 42, shown in FIGS. 53A and 53B, which may be optionally resident within the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), respectively.

(307) The server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) may optionally store the responses R.sub.11 . . . R.sub.nm (32) communicated from the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme corresponding to the server designations S.sub.11 . . . S.sub.nm (30) in the optional databases 41 and/or 42, optionally resident within the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), respectively, which may be optionally retrieved from the optional databases 41 and/or 42, and/or optionally incorporated into the service and/or information responses IR.sub.1 . . . IR.sub.n (34), and accessed as the additional optional responses RA.sub.11 . . . RA.sub.nm (40).

(308) The server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) may optionally communicate with the optional servers SO.sub.1 . . . SO.sub.p (22), and obtain information from each of the optional servers SO.sub.1 . . . SO.sub.p (22), which may also be stored in the optional databases 41 and/or 42, which may be optionally resident within the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), respectively, and which may be optionally incorporated into the service and/or information responses IR.sub.1 . . . IR.sub.n (34), and accessed as the additional optional responses RA.sub.11 . . . RA.sub.nm (40).

(309) Each of the users U.sub.1 . . . U.sub.n (12) may optionally communicate corresponding additional optional requests q.sub.11 . . . q.sub.np (44) through the corresponding user interfaces I.sub.1 . . . I.sub.n (14) and the corresponding clients C.sub.1 . . . C.sub.n (16) to the optional servers SO.sub.1 . . . SO.sub.p (22), based upon information in the service and/or information responses IR.sub.1 . . . IR.sub.n (34) and/or other information presented to and/or available and/or known to the users U.sub.1 . . . U.sub.n (12) through the corresponding user interfaces I.sub.1 . . . I.sub.n (14). The optional servers SO.sub.1 . . . SO.sub.p (22) reply to the clients C.sub.1 . . . C.sub.n (16) with corresponding responses r.sub.11 . . . r.sub.np (46), which the clients C.sub.1 . . . C.sub.n (16) communicate through the corresponding user interfaces I.sub.1 . . . I.sub.n (14) to the corresponding users U.sub.1 . . . U.sub.n (12), as shown in FIG. 2 for typical ones of the requests q.sub.11 . . . q.sub.np (44) and the corresponding responses r.sub.11 . . . r.sub.np (46).

(310) G. Additional Details

(311) Now, in more detail, the clients C.sub.1 . . . C.sub.n (16) and the servers S.sub.1 . . . S.sub.z (20) reside on the network 24. The users U.sub.1 . . . U.sub.n (12) and the corresponding clients C.sub.1 . . . C.sub.n (16) communicate one with the other through the corresponding user interfaces I.sub.1 . . . I.sub.n (14). The user U.sub.1 (12), thus, communicates with the client C.sub.1 (16), one with the other, through the user interface I.sub.1 (14); the user U.sub.2 (12), thus, communicates with the client C.sub.2 (16), one with the other, through the user interface I.sub.2 (14); the user U.sub.n (12), thus, communicates with the client C.sub.n (16), one with the other, through the user interface I.sub.n (14); and so on. Any particular user, designated user U.sub.n (12), thus, communicates with corresponding client C.sub.n (16), one with the other, through corresponding user interface I.sub.n (14), as best shown later in FIGS. 54-56. The user U.sub.n (12) may be used to designate any one of the users U.sub.1 . . . U.sub.n (12); the user interface I.sub.n (14) may be used to designate any one of the user interfaces I.sub.1 . . . I.sub.n (14); the client C.sub.n (16) may be used to designate any one of the users clients C.sub.1 . . . C.sub.n (16); and so on. The client-server multitasking system 10 may also have the server PS (18) and the optional servers SO.sub.1 . . . SO.sub.p (22) residing on the network 24.

(312) There may be n different or same the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) present on the network 24 at any time. Each of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) may have 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), which are called server designations S.sub.11 . . . S.sub.nm (30), in accordance with the 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). The service and/or information request IQ.sub.n (28) may be used to designate any particular one of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28). Requests Q.sub.n1 . . . Q.sub.nm (29) may be used to designate the particular requests Q.sub.11 . . . Q.sub.nm (29) associated with and corresponding to the service and/or information request IQ.sub.n (28).

(313) Each of the requests Q.sub.11 . . . Q.sub.1m from the client C.sub.1 (16) may each be different one from the other or the same; each of the requests Q.sub.21 . . . Q.sub.2m from the client C.sub.2 (16) may each be different one from the other or the same; and each of the requests Q.sub.n1 . . . Q.sub.nm (29) from the client C.sub.n (16) may each be different one from the other or the same, and so on. The requests Q.sub.11 . . . Q.sub.1m (29), the requests Q.sub.21 . . . Q.sub.2m (29), and the requests Q.sub.n1 . . . Q.sub.nm (29), thus, may each be different one from the other, or the same, and so on. The requests Q.sub.11 . . . Q.sub.nm (29) from the clients C.sub.1 . . . C.sub.n (14), thus, may each be different, one from the other, or the same, and may be made of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20) at the same time and/or different times, in accordance with the corresponding server designations S.sub.11 . . . S.sub.nm (30). There may be m different or same ones of the requests Q.sub.n1 . . . Q.sub.nm (29) from the client C.sub.n (16) at any time, and n×m different and/or same ones of the requests Q.sub.11 . . . Q.sub.nm (29) of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20) present on the network 24 at any time.

(314) This designation format, in which the first alphanumeric subscript after the parameter of interest, for example, as in the parameters Q.sub.n1 . . . Q.sub.nm representing the requests Q.sub.n1 . . . Q.sub.nm (29), represents the particular parameters corresponding to the user U.sub.n (12), and the second alphanumeric subscript after the parameter of interest represents the 1.sup.st, 2.sup.nd, 3.sup.th, through the mth one of the particular parameters, will be used as a designation scheme throughout. In this particular instance, for example, there are then m distinctly the same and/or different ones of the requests Q.sub.n1 . . . Q.sub.nm (29) associated with the nth user U.sub.n, which is designated as the user U.sub.n (12). There are then the same and/or different m distinctly the same and/or different server designations S.sub.n1 . . . S.sub.nm (30) associated with the nth user U.sub.n, which is designated as the user U.sub.n (12). The same and/or different requests Q.sub.n1 . . . Q.sub.nm (29), then, may be made 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 certain ones of the server designations S.sub.n1 . . . S.sub.nm (30), associated with and corresponding to the user U.sub.n (12).

(315) Each of the clients C.sub.1 . . . C.sub.n (16) may optionally also function as servers. Certain ones of the clients C.sub.1 . . . C.sub.n (16) may, therefore, function only as clients, while alternate ones of the clients C.sub.1 . . . C.sub.n (16) may function as clients and as servers. Each of the user interfaces I.sub.1 . . . I.sub.n (14) may be integral with the clients C.sub.1 . . . C.sub.n (16) or separate from the clients C.sub.1 . . . C.sub.n (16). Therefore, certain ones of the user interfaces I.sub.1 . . . I.sub.n (14) may be integral with the clients C.sub.1 . . . C.sub.n (16), while yet other ones of the user interfaces I.sub.1 . . . I.sub.n (14) may be separate from the clients C.sub.1 . . . C.sub.n (16).

(316) The client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information from the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20), and/or the optional servers SO.sub.1 . . . SO.sub.p (22), and/or the clients C.sub.1 . . . C.sub.n (16), having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information into the user responses UR.sub.1 . . . UR.sub.n (37) for delivery to the user interfaces I.sub.1 . . . I.sub.n (14) and use by the users U.sub.1 . . . U.sub.n (12).

(317) Now, the user interfaces I.sub.1 . . . I.sub.n (14) may each be different, one from the other, or the same, and may change characteristics over time. Each of the user interfaces I.sub.1 . . . I.sub.n (14) may change characteristics as a function of time, information, and/or instructions, and/or other means, which may be derived by the users U.sub.1 . . . U.sub.n (12) and/or the clients C.sub.1 . . . C.sub.n (16) and/or the servers S.sub.1 . . . S.sub.z (20), and/or the server PS (18), and/or the optional servers SO.sub.1 . . . SO.sub.p (22), and/or derived within the user interfaces I.sub.1 . . . I.sub.n (14). The user interface I.sub.1 . . . I.sub.n (14) may change state.

(318) The user interface I.sub.1 . . . I.sub.n (14) may also change as a function of optional timers and/or timed instructions associated with the user interfaces I.sub.1 . . . I.sub.n (14), and/or associated with the clients C.sub.1 . . . C.sub.n (16) and/or associated with the servers S.sub.1 . . . S.sub.z (20), and/or associated with the server PS (18), and/or associated with the optional servers SO.sub.1 . . . SO.sub.p (22), and/or instructions from the user U.sub.1 . . . U.sub.n (12). Changes in the user interface I.sub.n (14) may appear continuous to the user U.sub.n (12), spaced in time, staccato, or static depending upon the optional timers and/or the timed instructions. Other conditions may change the user interface I.sub.1 . . . I.sub.n (14), as well.

(319) The user interfaces I.sub.1 . . . I.sub.n (14) may be updated continuously, intermittently, manually, randomly, semi-automatically, automatically, repetitively, non-repetitively, singly, plurally, multiplexed, and/or a combination thereof or other suitable manner.

(320) The user interfaces I.sub.1 . . . I.sub.n (14) may be visual, such as graphical user interfaces, aural, and/or tactile, a combination thereof, and/or other suitable means. The user interfaces I.sub.1 . . . I.sub.n (14) may be integral with the clients C.sub.1 . . . C.sub.n (16) or separate.

(321) II. A Particular User, User Interface, and Client on the Network

(322) A. Overview

(323) FIGS. 54-56 show typical particular ones of the users U.sub.n (12), the corresponding ones of the user interfaces U.sub.n (12), the corresponding ones of the clients C.sub.n (16), the server PS (18), the servers S.sub.1 . . . S.sub.z (20) designated by the server designations S.sub.n1 . . . S.sub.nm (30) corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) associated with the corresponding ones of the users U.sub.n (12), and the optional servers SO.sub.1 . . . SO.sub.p (22) of the client-server multitasking system 10 of the present invention, which reside on the network 24. The user U.sub.n (12) communicates with the corresponding client C.sub.n (16) through the corresponding user interface I.sub.n (14).

(324) The user U.sub.n (12) enters the corresponding user input UI.sub.n (25) having one or more same and/or different user requests qu.sub.n1 . . . qu.sub.nu (26) into the user interface I.sub.n (14). The user requests qu.sub.n1 . . . qu.sub.nu (26) are communicated from the user interface I.sub.n (14) to the client C.sub.n (16) within the user service and/or information request iq.sub.n (27), having the user requests qu.sub.n1 . . . qu.sub.nu (26) and other optional information.

(325) The user interface I.sub.n (14) communicates the user service and/or information request iq.sub.n (27) to the client C.sub.n (16), which optionally formats the corresponding user service and/or information request iq.sub.n (27) into the corresponding service and/or information request IQ.sub.n (28), as required. The service and/or information request IQ.sub.n (28) may have one or more the same and/or different requests Q.sub.n1 . . . Q.sub.nm (29) to be made of the servers S.sub.1 . . . S.sub.z (20) designated by the server designations S.sub.n1 . . . S.sub.nm (30) at the same time.

(326) The client C.sub.n (16) may communicate the corresponding service and/or information request IQ.sub.n (28) to the server PS (18). The server PS (18) parses, processes and/or formats the service and/or information request IQ.sub.n (28) received from the client C.sub.n (16) into the certain requests Q.sub.n1 . . . Q.sub.nm (29), and communicates the certain requests Q.sub.n1 . . . Q.sub.nm (29) to the corresponding certain ones of the servers S.sub.1 . . . S.sub.z (20) designated by the server designations S.sub.n1 . . . S.sub.nm (30), as shown for typical ones of the certain requests Q.sub.n1 . . . Q.sub.nm (29) in FIG. 54.

(327) The client C.sub.n (16) may alternatively parse, process and/or format the user service and/or information request iq.sub.n (27) into the alternate requests Q.sub.n1 . . . Q.sub.nm (29), and communicate the alternate requests Q.sub.n1 . . . Q.sub.nm (29) to the corresponding alternate ones of the servers S.sub.1 . . . S.sub.z (20) designated by the server designations S.sub.n1 . . . S.sub.nm (30), as shown for typical alternate ones of the requests Q.sub.n1 . . . Q.sub.nm (29) in FIG. 55.

(328) The client C.sub.n (16) may alternatively communicate the corresponding other alternate one of the service and/or information request IQ.sub.n (28) to the server PS (18), which parses, processes and/or formats the other alternate one of the service and/or information request IQ.sub.n (28) into the other alternate ones of the requests Q.sub.n1 . . . Q.sub.nm (29), and communicates the other alternate ones of the requests Q.sub.n1 . . . Q.sub.nm (29) to the corresponding other alternate ones of the servers S.sub.n1 . . . S.sub.nm (30), and additionally the client C.sub.n (16) may also parse, process and/or format the user service and/or information request iq.sub.n (27) into yet other alternate ones of the requests Q.sub.n1 . . . Q.sub.nm (29), and communicate the yet other alternate ones of the requests Q.sub.n1 . . . Q.sub.nm (29) to the corresponding yet other alternate ones of the servers S.sub.n1 . . . S.sub.nm (30), as shown for typical other alternate ones of the requests Q.sub.n1 . . . Q.sub.nm (29) and typical yet other alternate ones of the requests Q.sub.n1 . . . Q.sub.nm (29) in FIG. 56.

(329) Each of the servers S.sub.1 . . . S.sub.z (20) designated by the server designations S.sub.n1 . . . S.sub.nm (30) replies to the server PS (18) and/or the client C.sub.n (16), in accordance with the designation scheme corresponding to the corresponding certain ones of the server designations S.sub.n1 . . . S.sub.nm (30), accordingly, and communicates the corresponding responses R.sub.n1 . . . R.sub.nm (32), associated with the requests Q.sub.n1 . . . Q.sub.nm (29), to the server PS (18) and/or the client C.sub.n (16), accordingly. The server PS (18) and/or the client C.sub.n (16) parse, format, process, group, and organize the responses R.sub.n1 . . . R.sub.nm (32) into the corresponding service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36) having the corresponding parsed, processed, formatted, grouped, and organized service and/or information group G.sub.n (35) acceptable to the client C.sub.n (16) and the user interface I.sub.n (14). The server PS (18) communicates the service and/or information response IR.sub.n (34) to the client C.sub.n (16), as required.

(330) The client C.sub.n (16) formats the service and/or information responses IR.sub.1 . . . IR.sub.n (34) into the corresponding user service and/or information response ir.sub.n (36), as required, and communicates the user service and/or information responses ir.sub.n (36) to the user interfaces I.sub.n (14). The user interface I.sub.n (14) incorporates the user service and/or information response ir.sub.n (36) into the user response UR.sub.n (37), which is communicated by the user interfaces I.sub.n (14) to the user U.sub.n (12).

(331) The server PS (18) and/or the client C.sub.n (16) may optionally also incorporate the optional additional corresponding responses RA.sub.n1 . . . RA.sub.nm (40) (shown later in FIGS. 59, 60, 63, and 64) into the service and/or information response IR.sub.n (34), which may be obtained by accessing the optional databases 41 and/or 42, which may be optionally resident within the server PS (18) and/or the client C.sub.n (16), respectively

(332) The server PS (18) and/or the client C.sub.n (16) communicate the service and/or information response IR.sub.n (34) through the user interface I.sub.n (14) to the user U.sub.n (12).

(333) The server PS (18) and/or the clients C.sub.n (16) may optionally store the responses R.sub.n1 . . . R.sub.nm (32) communicated from the servers S.sub.1 . . . S.sub.z (20) designated by the server designations S.sub.n1 . . . S.sub.nm (30) in the optional databases 41 and/or 42, optionally resident within the server PS (18) and/or the client C.sub.n (16), respectively, which may be optionally retrieved from the optional databases 41 and/or 42, and/or optionally incorporated into the service and/or information response IR.sub.n (34), and accessed as the additional optional responses RA.sub.n1 . . . RA.sub.nm (40).

(334) The server PS (18) and/or the client C.sub.n (16) may optionally communicate with the optional servers SO.sub.1 . . . SO.sub.p (22), and obtain information from each of the optional servers SO.sub.1 . . . SO.sub.p (22), which may also be stored in the optional databases 41 and/or 42, which may be optionally resident within the server PS (18) and/or the client C.sub.n (16), respectively, and which may be optionally incorporated into the service and/or information response IR.sub.n (34), and accessed as the additional optional responses RA.sub.n1 . . . RA.sub.nm (40).

(335) The user U.sub.n (12) may optionally communicate the corresponding additional optional requests q.sub.n1 . . . q.sub.np (44) through the user interface I.sub.n (14) and the client C.sub.n (16) to the optional servers SO.sub.1 . . . SO.sub.p (22), based upon information in the service and/or information response IR.sub.n (34) and/or other information presented to and/or available and/or known to the user U.sub.n (12) through the user interface I.sub.n (14). The optional servers SO.sub.1 . . . SO.sub.p (22) reply to the client C.sub.n (16) with the corresponding responses r.sub.n1 . . . r.sub.np (46), which the client C.sub.n (16) communicates through the user interface I.sub.n (14) to the user U.sub.n (12), as shown in FIGS. 54-56 for typical ones of the requests q.sub.n1 . . . q.sub.np (44) and the corresponding responses r.sub.n1 . . . r.sub.np (46).

(336) B. Diagrammatic Regrouping

(337) Now, in more detail, FIG. 57 shows a schematic representation of ones of the users U.sub.1 . . . U.sub.n (12), the corresponding user interfaces I.sub.1 . . . I.sub.n (14), the corresponding clients C.sub.1 . . . C.sub.n (16), the server PS (18), the servers S.sub.1 . . . S.sub.z (20), and the optional servers SO.sub.1 . . . SO.sub.p (22) of the client-server multitasking system 10 of the present invention, constructed in accordance with the present invention, which reside on the network 24, regrouped diagrammatically and alternatively named for illustrative purposes only, to illustrate and visualize possible typical communication paths. Other than FIG. 57, the nomenclature previously described and utilized will be used throughout.

(338) Now, as shown in FIG. 57, for illustrative purposes only, ones of the clients C.sub.1 . . . C.sub.n (16) communicating with the server PS (18), as in FIG. 54, may optionally be designated clients CA.sub.1 . . . CA.sub.w (16A), and so on. Ones of the clients C.sub.1 . . . C.sub.n (16) communicating with the servers S.sub.1 . . . S.sub.z (20), as in FIG. 55, may optionally be designated clients CB.sub.1 . . . CB.sub.x (16B), and so on. Ones of the clients C.sub.1 . . . C.sub.n (16) communicating with the server PS (18) and with the servers S.sub.1 . . . S.sub.z (20), as in FIG. 56, may optionally be designated clients CC.sub.1 . . . CC.sub.y (16C), and so on.

(339) The users U.sub.1 . . . U.sub.n (12) and the corresponding user interfaces I.sub.1 . . . I.sub.n (14) corresponding to the clients C.sub.1 . . . C.sub.n (16) may, likewise, optionally be designated in FIG. 57 only: correspondingly to the clients CA.sub.1 . . . CA.sub.w (16A), as users UA.sub.1 . . . UA.sub.w (12A) and user interfaces IA.sub.1 . . . IA.sub.w (14A), respectively; correspondingly to the clients CB.sub.1 . . . CB.sub.x (16B), as users UB.sub.1 . . . UB.sub.x (12B) and user interfaces IB.sub.1 . . . IB.sub.x (14B), respectively; and correspondingly to the clients CC.sub.1 . . . CC.sub.y (16C), as users UC.sub.1 . . . UC.sub.y (12C) and IC.sub.1 . . . IC.sub.y (14C), respectively.

(340) The clients C.sub.1 . . . C.sub.n (16) being accounted for, the total of the clients CA.sub.1 . . . CA.sub.w (16A), CB.sub.1 . . . CB.sub.x (16B), and CC.sub.1 . . . CC.sub.y (16C) of FIG. 57 add up to n, where n may be any number greater or equal to one, such that the subscripts w+x+y=n.

(341) III. A Particular Service and/or Information Request and Associated Service and/or Information Response on the Network

(342) B. The Server PS (18)

(343) FIG. 58 shows a typical particular one of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28), designated as the service and/or information request IQ.sub.n (28), having queries QQ.sub.n1 . . . QQ.sub.nm (53), corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and optional instructions VJ.sub.n1 . . . VJ.sub.nk (52). The server addresses AQ.sub.n1 . . . AQ.sub.nm (54) and the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) may be optional, and may depend upon the user interface I.sub.n (14), and/or other information resident within the server PS (18).

(344) FIG. 59 shows the particular service and/or information request IQ.sub.n (28) parsed, processed, and/or formatted into current request group QA.sub.nc (50), request groups QA.sub.n1 . . . QA.sub.nz (51), and optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and utilization of information therefrom to make the requests Q.sub.n1 . . . Q.sub.nm (29), obtain the responses R.sub.n1 . . . R.sub.nm (32), and incorporate information therefrom into the particular service and/or information response IR.sub.n (34). The current request group QA.sub.nc (50) may be any particular one the request groups QA.sub.n1 . . . QA.sub.nz (51), which may be selected by the user U.sub.n (12).

(345) Upon receipt of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) at the server PS (18), communicated from the corresponding clients C.sub.1 . . . C.sub.n (16), the server PS (18) parses, processes, and/or formats each of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) into the corresponding current request groups QA.sub.1c . . . QA.sub.nc (50) having corresponding queries QQ.sub.11 . . . QQ.sub.nm (53) and corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54) to open connections with and make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of 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), shown for a particular one of the service and/or information requests IQ.sub.n (28) in FIG. 59.

(346) The server PS (18) also parses, processes, and/or formats each of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) into the corresponding request groups QA.sub.11 . . . QA.sub.nz (51) having corresponding other queries QQ.sub.1a . . . QQ.sub.nz (55) and corresponding other server addresses AQ.sub.1n . . . AQ.sub.nz (56), and the corresponding optional instructions VJ.sub.111 . . . VJ.sub.nk (52), also shown for a particular one of the service and/or information requests IQ.sub.n (28) in FIG. 59.

(347) The server PS (18) opens connections with and makes the requests Q.sub.n1 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of 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), shown for the particular one of the service and/or information requests IQ.sub.n (28) corresponding to the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) in the current request group QA.sub.mc (50).

(348) The servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.11 . . . S.sub.nm (30), designated in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) as the corresponding server designations S.sub.11 . . . S.sub.nm (30), respond to the requests Q.sub.11 . . . Q.sub.nm (29) with the corresponding responses R.sub.n1 . . . R.sub.nm (32).

(349) The server PS (18) parses, and/or processes, and/or formats, and/or groups, and/or organizes each of the responses R.sub.n1 . . . R.sub.nm (32) received from the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.11 . . . S.sub.nm (30) into corresponding addressable response information groups RG.sub.n1 . . . RG.sub.nm (57).

(350) The server PS (18) may also make additional optional requests QP.sub.n1 . . . QP.sub.nm (58) of the optional database 41, which may be optionally resident within the server PS (18), and which may reply with the corresponding additional optional responses RA.sub.n1 . . . RA.sub.nm (40). The server PS (18) parses, and/or processes, and/or formats, and/or groups, and/or organizes each of the additional optional responses RA.sub.n1 . . . RA.sub.nm (40) into corresponding response information groups RC.sub.n1 . . . RC.sub.nm (59).

(351) Information from the current request group QA.sub.nc (50) having the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) is formulated into a corresponding request pointer/address group QZ.sub.n (60) having pointers/addresses PG.sub.n1 . . . PG.sub.nz (61) associated therewith.

(352) Each of the pointers/addresses PG.sub.n1 . . . PG.sub.nz (61) are directed to point/address corresponding addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) associated therewith, which aid in obtaining information and/or services from certain ones of addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) to be incorporated into addressable query information groups GI.sub.n1 . . . GI.sub.nz (63).

(353) Grouping and/or sorting criteria may be incorporated into the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), which may be entered into the user interface I.sub.n (14) through the user input UI.sub.n (25) by the user U.sub.n (12). Grouping and/or sorting criteria may additionally and/or alternatively be optionally resident within the server PS (18) and/or the client C.sub.n (16).

(354) The grouping and/or sorting criteria gives the user U.sub.n (12) the ability to formulate the query information groups GI.sub.n1 . . . GI.sub.nz (63) and the way in which information and/or services from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is presented to the user U.sub.n (12) through the user interface I.sub.n (14).

(355) Each of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) are associated with the corresponding ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63). The addressable query pointer/address group QG.sub.n1 (62) is, thus, associated with the addressable query information group GI.sub.n1 (63); the addressable query pointer/address group QG.sub.n2 (62) is, thus, associated with the addressable query information group GI.sub.n2 (63); the addressable query pointer/address group QG.sub.nz (62) is, thus, associated with the addressable query information group GI.sub.nz (63), and so on.

(356) Each of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) is formulated based upon the grouping and/or sorting criteria, which may be incorporated into the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and/or which may additionally and/or alternatively optionally be resident within the server PS (18) and/or the client C.sub.n (16), and/or information within the current request group QA.sub.nc (50).

(357) Each of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) has pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) directed to address/point information in the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) based upon the grouping and/or sorting criteria, which may be incorporated into the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and/or which may additionally and/or alternatively optionally be resident within the server PS (18) and/or the client C.sub.n (16), and/or the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53), and/or the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) within the current request group QA.sub.nc (50).

(358) Information and/or services within each of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is addressed with the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) from the query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), and information and/or services from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is incorporated into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) corresponding to the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64), which are formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), in accordance with the grouping and/or sorting criteria.

(359) The corresponding other queries QQ.sub.na . . . QQ.sub.nz (55) and the corresponding other server addresses AQ.sub.na . . . AQ.sub.nz (56) in the corresponding request groups QA.sub.n1 . . . QA.sub.nz (51) may be used for other ones of the requests Q.sub.n1 . . . Q.sub.nm (29), and may be incorporated into the service and/or information response IR.sub.n (34), as part of other information OI.sub.n (65), for future use.

(360) Each of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) is incorporated into the service and/or information group G.sub.n (35). The service and/or information group G.sub.n (35) and the other information OI.sub.n (65) are incorporated into the service and/or information response IR.sub.n (34).

(361) The optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) may be used by the server PS (18) in making the requests Q.sub.n1 . . . Q.sub.nm (29) and/or the additional optional requests QP.sub.n1 . . . QP.sub.nm (58) of the optional database 41, and/or in processing, formatting, grouping, and organizing the responses R.sub.n1 . . . R.sub.nm (32) from the ones of the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.n1 . . . S.sub.nm (30), and/or the additional optional responses RA.sub.n1 . . . RA.sub.nm (40), into the corresponding service and/or information responses IR.sub.1 . . . IR.sub.n (34), for grouping and/or sorting criteria instructions, and/or may be used for other purposes.

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

(363) The user U.sub.n (12) is typically given the option through the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) as to the grouping and/or sorting criteria to be entered into the user interface I.sub.n (14) through the user input UI.sub.n (25) by the user U.sub.n (12). The user U.sub.n (12) is typically given the choice as to the grouping and/or sorting criteria to be used as in FIG. 59, and/or the grouping and/or sorting criteria of FIG. 60.

(364) Information from the current request group QA.sub.nc (50) having the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) is formulated into a corresponding request pointer/address group QY.sub.n (68) having pointers/addresses PF.sub.n11 . . . PF.sub.nmr (69) associated therewith, as shown in FIG. 60.

(365) Each of the pointers/addresses PF.sub.n11 . . . PF.sub.nmr (69) are directed to point/address the corresponding addressable response information groups RG.sub.n1 . . . RG.sub.nm (57), and aid in obtaining information and/or services from the corresponding addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) to be incorporated into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), as shown in FIG. 60.

(366) The grouping and/or sorting criteria allow the user U.sub.n (12) to direct the server PS (18) and/or the client C.sub.n (16) to sort information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) and/or the additional optional responses RA.sub.n1 . . . RA.sub.nm (40) from the optional database 41, such as, for example, by category, query, group, page, order of importance, ascending and/or descending order, alphabetically and/or numerically, value, price, and/or other characteristics, and/or to combine and/or interleave the information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) and/or the additional optional responses RA.sub.n1 . . . RA.sub.nm (40) one with the other, such as, for example, by order of relevance and/or other parameters.

(367) FIG. 61 shows the particular service and/or information response IR.sub.n (34) having a service and/or information group G.sub.n (35), additional request links SL.sub.n1 . . . SL.sub.nw (71), optional order form 72, optional additional advertisements and/or links 73, optional hidden information 74, and the optional service and/or information entry request form IE.sub.n (38).

(368) The service and/or information group G.sub.n (35) has the query information groups GI.sub.n1 . . . GI.sub.nz (63), optional database response groups 75, and optional additional advertisements and/or links 76.

(369) The additional request links SL.sub.n1 . . . SL.sub.nw (71) allow the user U.sub.n (12) to make additional optional selections, based upon information and/or services previously requested by the user U.sub.n (12). The additional request links SL.sub.n1 . . . SL.sub.nw (71), which are optional, may typically have Current Group/Next Group/Previous Group/Group Number Links, Server Names in Each Group, Queries in Each Group, Current Page/Next Page/Previous Page/Page Number Links, Search Display/Link and/or Description Placement/Interleave/Separate, and Link Description

(370) Options/Summary/Minimize. Other additional ones of the additional requests links SL.sub.n1 . . . SL.sub.nw (71) and/or combinations thereof may also be incorporated into the service and/or information response IR.sub.n (34).

(371) The optional order form 72 allows direct placement and/or confirmation of orders and/or purchases with the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22), which reside on the network 24. The user U.sub.n (12) may enter the order placement into the user interface I.sub.n (14) through the user input UI.sub.n (25), and receive order confirmation through the user interface I.sub.n (14). The client C.sub.n (16) may communicate the order placement from the user interface I.sub.n (14) to the server PS (18), which may communicate the order placement to the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22). The server PS (18) may alternatively and/or additionally communicate the order confirmation received from the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22) to the client C.sub.n (16), which may communicate the order confirmation to the user interface I.sub.n (14) for presentation to the user U.sub.n (12). The order placement and/or the order confirmation may be stored within the server PS (18) and/or the client C.sub.n (16). The order placement and/or the order confirmation is typically secure, and may be encrypted, and is typically communicated using secure communications means.

(372) C. Certain Ones of the Clients

(373) Certain ones of the clients C.sub.1 . . . C.sub.n (16) may alternatively and/or additionally make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), and formulate the corresponding user service and/or information response ir.sub.1 . . . ir.sub.n (36), as previously described.

(374) FIG. 62 shows a typical particular one of the user service and/or information requests iq.sub.1 . . . iq.sub.n (27), designated as the user service and/or information request iq.sub.n (27), having the queries QQ.sub.n1 . . . QQ.sub.nm (53), the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52). The server addresses AQ.sub.n1 . . . AQ.sub.nm (54) and the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) may be optional, and may depend upon the user interface I.sub.n (14), and/or other information resident within the client C.sub.n (16).

(375) FIG. 63 shows the particular user service and/or information request iq.sub.n (27) parsed, processed, and/or formatted into the current request group QA.sub.nc (50), the request groups QA.sub.n1 . . . QA.sub.nz (51), and the corresponding optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and utilization of information therefrom to make the requests Q.sub.n1 . . . Q.sub.nm (29), obtain the responses R.sub.n1 . . . R.sub.nm (32), and incorporate information therefrom into the particular user service and/or information response ir.sub.n (36);

(376) The server PS (18) makes the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of 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 FIG. 59, and certain ones of the clients C.sub.1 . . . C.sub.n (16) may additionally and/or alternatively make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of 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 FIG. 63.

(377) The clients C.sub.n (16) may parse, process, and/or format the user service and/or information requests iq.sub.n (27) and/or organize and/or group information and/or services from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) substantially the same as the server PS (18) parses, processes, and/or formats the service and/or information requests IQ.sub.n (28) from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), except that the client C.sub.n (16) may organize the addressable query information groups GI.sub.n1 . . . GI.sub.nm (63) into the user service and/or information response ir.sub.n (36), as in FIG. 63, and the server PS (18) organizes the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) into the corresponding service and/or information response IR.sub.n (34), as in FIG. 59.

(378) Upon receipt of the user service and/or information requests iq.sub.1 . . . iq.sub.n (27) at the corresponding clients C.sub.1 . . . C.sub.n (16), certain ones of the corresponding clients C.sub.1 . . . C.sub.n (16) may parse, process, and/or format the corresponding user service and/or information requests iq.sub.1 . . . iq.sub.n (27) into the corresponding current request groups QA.sub.1c . . . QA.sub.nc (50) having the corresponding queries QQ.sub.11 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54) to open connections with and make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of 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), shown for a particular one of the user service and/or information requests iq.sub.1 . . . iq.sub.n (27) in FIG. 63.

(379) The corresponding clients C.sub.1 . . . C.sub.n (16) may also parse, process, and/or format the corresponding user service and/or information response ir.sub.1 . . . ir.sub.n (36) into the corresponding request groups QA.sub.11 . . . QA.sub.nz (51) having the corresponding other queries QQ.sub.1a . . . QQ.sub.nz (55) and the corresponding other server addresses AQ.sub.1a . . . AQ.sub.nz (56), and the corresponding optional instructions VJ.sub.111 . . . VJ.sub.nk (52), also shown for a particular one of the user service and/or information requests iq.sub.n (27) in FIG. 63.

(380) A particular one of the corresponding clients C.sub.1 . . . C.sub.n (16), designated as the client C.sub.n (16), may open connections with and make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) as the corresponding server designations S.sub.11 . . . S.sub.nm (30), shown for the particular one of the user service and/or information requests iq.sub.n (27) corresponding to the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) in the current request group QA.sub.nc (50).

(381) The servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.11 . . . S.sub.nm (30), designated in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) as the corresponding server designations S.sub.11 . . . S.sub.nm (30), respond to the requests Q.sub.n1 . . . Q.sub.nm (29) with the corresponding responses R.sub.n1 . . . R.sub.nm (32).

(382) The client C.sub.n (16) may parse, and/or process, and/or format, and/or group, and/or organize each of the responses R.sub.n1 . . . R.sub.nm (32) received from the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.n1 . . . S.sub.nm (30) into the corresponding addressable response information groups RG.sub.n1 . . . RG.sub.nm (57).

(383) The client C.sub.n (16) may also make additional optional requests QP.sub.n1 . . . QP.sub.nm (58) of the optional database 42, which may be optionally resident within the client C.sub.n (16), and which may reply with the corresponding additional optional responses RA.sub.n1 . . . RA.sub.nm (40). The client C.sub.n (16) may parse, and/or process, and/or format, and/or group, and/or organize each of the additional optional responses RA.sub.n1 . . . RA.sub.nm (40) into the corresponding response information groups RC.sub.n1 . . . RC.sub.nm (59).

(384) Now again, for the client C.sub.n (16), information from the current request group QA.sub.nc (50) having the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) is formulated into the corresponding request pointer/address group QZ.sub.n (60) having the pointers/addresses PG.sub.n1 . . . PG.sub.nz (61) associated therewith.

(385) Now again, for the client C.sub.n (16), each of the pointers/addresses PG.sub.n1 . . . PG.sub.nz (61) are directed to point/address the corresponding addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) associated therewith, which aid in obtaining information and/or services from certain ones of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) to be incorporated into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63).

(386) Yet again, for the client C.sub.n (16), grouping and/or sorting criteria may be incorporated into the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), which may be entered into the user interface I.sub.n (14) through the user input UI.sub.n (25) by the user U.sub.n (12). Grouping and/or sorting criteria may additionally and/or alternatively optionally resident within the server PS (18) and/or the client C.sub.n (16).

(387) Now again, the grouping and/or sorting criteria gives the user U.sub.n (12) the ability to formulate the query information groups GI.sub.n1 . . . GI.sub.nz (63) and the way in which information from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is presented to the user U.sub.n (12) through the user interface I.sub.n (14).

(388) Now again, for the client C.sub.n (16), each of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) are associated with the corresponding ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63). Each of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) is formulated based upon the grouping and/or sorting criteria, which may be incorporated into the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and/or which may additionally and/or alternatively optionally be resident within the server PS (18) and/or the client C.sub.n (16), and/or information within the current request group QA.sub.nc (50).

(389) Now again, for the client C.sub.n (16), each of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) has pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) directed to address/point services and/or information in the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) based upon the grouping and/or sorting criteria, which may be incorporated into the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and/or which may additionally and/or alternatively optionally be resident within the server PS (18) and/or the client C.sub.n (16), and/or the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53), and/or the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) within the current request group QA.sub.nc (50).

(390) Yet again, for the client C.sub.n (16), the information and/or services in each of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is addressed with the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) from the query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), and information and/or services from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is incorporated into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) corresponding to the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64), which are formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), in accordance with the grouping and/or sorting criteria.

(391) Yet again, for the client C.sub.n (16), the corresponding other queries QQ.sub.na . . . QQ.sub.nz (55) and the corresponding other server addresses AQ.sub.n, . . . AQ.sub.nz (56) in the corresponding request groups QA.sub.n1 . . . QA.sub.nz (51) may be used for other ones of the requests Q.sub.n1 . . . Q.sub.nm (29), and may be incorporated into the user service and/or information response ir.sub.n (36), as part of other information OI.sub.n (65), for future use.

(392) Now again, for the client C.sub.n (16), each of the addressable query information groups GI.sub.n1 . . . GI.sub.nm (63) is incorporated into the service and/or information group G.sub.n (35). The service and/or information group G.sub.n (35) and the other information OI.sub.n (65) are incorporated into the service and/or information response IR.sub.n (34).

(393) The optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) may be used by the client C.sub.n (16), in making the requests Q.sub.n1 . . . Q.sub.nm (29) and/or the additional optional requests QP.sub.n1 . . . QP.sub.nm (58) of the optional database 42, and/or in processing, formatting, grouping, and organizing the responses R.sub.n1 . . . R.sub.nm (32) from the ones of the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.n1 . . . S.sub.nm (30), and/or the additional optional responses RA.sub.n1 . . . RA.sub.nm (40), into user service and/or information response ir.sub.n (36), for grouping and/or sorting criteria instructions, and/or may be used for other purposes.

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

(395) The user U.sub.n (12) is typically given the option through the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) as to the grouping and/or sorting criteria to be entered into the user interface I.sub.n (14) through the user input UI.sub.n (25) by the user U.sub.n (12). The user U.sub.n (12) is typically given the choice as to the grouping and/or sorting criteria of FIG. 63, and/or the grouping and/or sorting criteria of FIG. 64.

(396) Now again, the client C.sub.n (16) may parse, process, and/or format the user service and/or information requests iq.sub.n (27) and/or organize and/or group information and/or services from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) substantially the same as the server PS (18) parses, processes, and/or formats the service and/or information requests IQ.sub.n (28) from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), except that the client C.sub.n (16) may organize the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) into the user service and/or information response ir.sub.n (36), as in FIG. 64, and the server PS (18) organizes the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) into the corresponding service and/or information response IR.sub.n (34), as in FIG. 60.

(397) Now again, for the client C.sub.n (16), information from the current request group QA.sub.nc (50) having the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) is formulated into the corresponding request pointer/address group QY.sub.n (68) having the pointers/addresses PF.sub.n11 . . . PF.sub.nmr (69) associated therewith, as shown in FIG. 64.

(398) Now again, for the client C.sub.n (16), each of the pointers/addresses PF.sub.n11 . . . PF.sub.nmr (69) are directed to point/address the corresponding addressable response information groups RG.sub.n1 . . . RG.sub.nm (57), and aid in obtaining information and/or services from the corresponding addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) to be incorporated into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), as shown in FIG. 64.

(399) Again, the grouping and/or sorting criteria allow the user U.sub.n (12) to direct the server PS (18) and/or the client C.sub.n (16) to sort information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) and/or the additional optional responses RA.sub.n1 . . . RA.sub.nm (40) from the optional database 41, such as, for example, by category, query, group, page, order of importance, ascending and/or descending order, alphabetically and/or numerically, value, price, and/or other characteristics, and/or to combine and/or interleave the information and/or services from the responses R.sub.n1 . . . R.sub.nm (32) and/or the additional optional responses RA.sub.n1 . . . RA.sub.nm (40) one with the other, such as, for example, by order of relevance and/or other parameters.

(400) FIG. 65 shows the particular user service and/or information response ir.sub.n (36) having the service and/or information group G.sub.n (35), the additional request links SL.sub.n1 . . . SL.sub.nw (71), the optional order form 72, the optional additional advertisements and/or links 73, the optional hidden information 74, and the optional service and/or information entry request form IE.sub.n (38).

(401) Now again, the service and/or information group G.sub.n (35) has the query information groups GI.sub.n1 . . . GI.sub.nz (63), the optional database response groups 75, and the optional additional advertisements and/or links 76.

(402) Yet again, the additional request links SL.sub.n1 . . . SL.sub.nw (71) allow the user U.sub.n (12) to make additional optional selections, based upon information and/or services previously requested by the user U.sub.n (12). The additional request links SL.sub.n1 . . . SL.sub.nw (71), which are optional, may typically have Current Group/Next Group/Previous Group/Group Number Links, Server Names in Each Group, Queries in Each Group, Current Page/Next Page/Previous Page/Page Number Links, Search Display/Link and/or Description Placement/Interleave/Separate, and Link Description Options/Summary/Minimize. Other additional ones of the additional request links SL.sub.n1 . . . SL.sub.nw (71) and/or combinations thereof may also be incorporated into the user service and/or information response ir.sub.n (36).

(403) Now again, for the client C.sub.n (16), the optional order form 72 allows direct placement and/or confirmation of orders and/or purchases with the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22), which reside on the network 24. The user U.sub.n (12) may enter the order placement into the user interface I.sub.n (14) through the user input UI.sub.n (25), and receive order confirmation through the user interface I.sub.n (14). The client C.sub.n (16) may communicate the order placement from the user interface I.sub.n (14) to the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22), and/or receive the order confirmation therefrom, and communicate the order confirmation from the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22) to the user interface I.sub.n (14) for presentation to the user U.sub.n (12). The order placement and/or the order confirmation may be stored within the server PS (18) and/or the client C.sub.n (16). The order placement and/or the order confirmation is typically secure, and may be encrypted, and is typically communicated using secure communications means.

(404) D. Formulating Query Information Groups

(405) Each of the particular addressable response information groups RG.sub.n1 . . . RG.sub.nm (57), designated as the addressable response information group RG.sub.nm (57), has optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80), which may be addressed with the pointers/addresses PP.sub.nm1 . . . PP.sub.nmr (64), as shown in FIGS. 59, 63, 66A, 66B, and 66C.

(406) Each of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) and each of the optional addressable individual information groups LG.sub.n11 . . . LG.sub.nmr (80) in each of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) may be addressed with the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64).

(407) Now again, the addressable response information group RG.sub.nm (57) has the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80), which may be addressed with the pointers/addresses PP.sub.nm1 . . . PP.sub.nmr (64). Each of the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) in the addressable response information group RG.sub.nm (57) may be pointed/addressed by the server PS (18) and/or the client C.sub.n (16) to retrieve all and/or a portion and/or combinations of specific ones of the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80), from the addressable response information group RG.sub.nm (57), and incorporate information and/or services from the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) into certain ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nm (63), in accordance with the grouping and/or sorting criteria addressing scheme.

(408) The addressable response information group RG.sub.nm (57) having the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) may have optional addressable pointer/address indices IN.sub.nm1 . . . IN.sub.nmr (81) correspondingly associated with the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80), which may be addressed/pointed with the pointers/addresses PP.sub.nm1 . . . PP.sub.nmr (64), and which may be pointed/addressed by the server PS (18) and/or the client C.sub.n (16) to retrieve all and/or a portion and/or combinations of specific ones of the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80), and incorporate information and/or services from the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) into the certain ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), in accordance with the grouping and/or sorting criteria addressing scheme.

(409) FIGS. 66A, 66B, and 66C show the addressable response information group RG.sub.nm (57) having the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) showing the optional addressable pointer/address indices IN.sub.nm1 . . . IN.sub.nmr (81) correspondingly associated with the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80), which may be addressed/pointed with the pointer/addresses PP.sub.nm1 (64), PP.sub.nm2 (64), and PP.sub.nmr (64), respectively.

(410) The optional addressable pointer/address index IN.sub.nm1 (81) is correspondingly associated with the optional addressable individual information group LG.sub.nm1 (80). The optional addressable pointer/address index IN.sub.nm2 (81) is correspondingly associated with the optional addressable individual information group LG.sub.nm2 (80), and so on. The optional addressable pointer/address index IN.sub.nmr (81) is, thus, correspondingly associated with the optional addressable individual information group LG.sub.nm1 (80).

(411) The pointers/addresses PG.sub.n1 . . . PG.sub.nz (61) may be formulated as arrays and/or lists. The pointers/addresses PP.sub.nm1 . . . PP.sub.nmr (64) and/or the pointers/addresses PF.sub.nm1 . . . PF.sub.nmr (69) may be formulated as arrays and/or lists. The arrays may be multidimensional arrays, and the lists may be lists within lists.

(412) The optional addressable individual information group LG.sub.nmr (80) is associated with and corresponds to a particular one of the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) in a particular one of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57), designated as the addressable response information group RG.sub.nm (57). The first subscript of the optional addressable individual information groups LG.sub.nmr (80) is associated with and corresponds to the particular service and/or information request IQ.sub.n (28) and/or the user service and/or information request iq.sub.n (27). The second subscript of the optional addressable individual information groups LG.sub.nmr (80) is associated with and corresponds to a particular one of “1” through “m” i.e., 1 . . . m, of the addressable response information group RG.sub.n1 . . . RG.sub.nm (57). The third subscript of the optional addressable individual information groups LG.sub.nmr (80) is associated with and corresponds to a particular one of “1” through “r” i.e., 1 . . . r, of the optional addressable individual information group LG.sub.nm1 . . . LG.sub.nmr (80) within the addressable response information group RG.sub.nm (57).

(413) The subscripts of the optional addressable pointer/address indices IN.sub.nm1 . . . IN.sub.nmr (81) are correspondingly associated with the subscripts of the corresponding addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80).

(414) A number and variety of pointing/addressing schemes are possible, which may be used for a variety of grouping and sorting criteria schemes and addressing/pointing schemes.

(415) For example, the pointers/addresses PG.sub.n1 . . . PG.sub.nz (61) of the request pointer/address group QZ.sub.n (60) may be pointed/addressed to certain ones of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), in accordance with certain grouping and/or sorting criteria schemes and/or pointing/addressing schemes. The pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) of each of the pointed/addressed addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) may be pointed to the pointer/address indices IN.sub.n11 . . . IN.sub.nmr (81) of the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr, i.e., 1 . . . r, and the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64), i.e., 1 . . . m, corresponding to the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) may be pointed to certain ones of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57), in accordance with certain grouping and/or sorting criteria schemes and/or addressing schemes. This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is incorporated into the certain ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), in accordance with the grouping and/or sorting criteria addressing scheme, as formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) and the request pointer/address group QZ.sub.n (60).

(416) Alternatively and/or additionally, the pointers/addresses PG.sub.n1 . . . PG.sub.nz (61) of the request pointer/address group QZ.sub.n (60) may be incremented through each of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62). The pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) of each of the pointed/addressed addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) may be pointed to the pointer/address indices IN.sub.n11 . . . IN.sub.nmr (81) of the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr, i.e., 1 . . . r, and incremented once, and then the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64), i.e., 1 . . . m, corresponding to the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) may be incremented through each of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57). This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is incorporated into the certain ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), in accordance with the grouping and/or sorting criteria addressing scheme, and as formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62).

(417) Alternatively and/or additionally, the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64), i.e., 1 . . . m, may be incremented, corresponding to the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), and then the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64), i.e., 1 . . . r, pointing to the pointer/address indices IN.sub.n11 . . . IN.sub.nmr (81) of the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr may then be incremented. This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is incorporated into the certain ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), in accordance with the grouping and/or sorting criteria addressing scheme, and as formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62).

(418) Alternatively and/or additionally, the pointers/addresses PF.sub.nm1 . . . PF.sub.nmr (69), i.e., 1 . . . m, may be incremented, corresponding to the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), and then the pointers/addresses PF.sub.nm1 . . . PF.sub.nmr (69), i.e., 1 . . . r, pointing to the pointer/address indices IN.sub.n11 . . . IN.sub.nmr (81) of the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr may then be incremented. This subprocess may be repeated until the information and/or services from the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is incorporated into the certain ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), in accordance with the grouping and/or sorting criteria addressing scheme, and as formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62).

(419) The typical sorting and/or grouping criteria and the addressing/pointing schemes mentioned immediately above, for example, may group certain ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) having the same and/or substantially the same values into a particular one of the query information groups GI.sub.nz . . . GI.sub.nz (63), designated as the query information group GI.sub.nz (63), as shown in certain ones of FIGS. 27A-52C, inclusive.

(420) The grouping and/or sorting criteria and schemes and the addressing/pointing schemes mentioned herein are but only a small portion of a much larger variety of grouping and/or sorting criteria and schemes and addressing/pointing schemes and/or combinations thereof that the client-server multitasking system 10 of the present invention may use and is capable of. The above mentioned examples are included herein to illustrate but a few examples of the capabilities of the client-server multitasking system 10 of the present invention.

(421) The addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) are typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other, as the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) are incorporated into the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) from the responses R.sub.n1 . . . R.sub.nm (32).

(422) Alternatively and/or additionally the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) may be incorporated into the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) from the responses R.sub.n1 . . . R.sub.nm (32) in an as-is condition and/or in raw form.

(423) The optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) in the addressable response information group RG.sub.nm (57), having information and/or services parsed and/or processed, and/or formatted, and/or grouped from the response R.sub.nm (32), may be correspondingly associated with the locations of the information and/or services in the response R.sub.nm (32).

(424) Each of the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) may have and/or be parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into corresponding optional links LD.sub.nm1 . . . LD.sub.nmr (82), and/or corresponding optional descriptions DD.sub.nm1 . . . DD.sub.nmr (83), and/or corresponding optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84), and/or corresponding optional images ID.sub.nm1 . . . ID.sub.nmr (85), as shown in FIG. 67.

(425) The optional links LD.sub.nm1 . . . LD.sub.nmr (82), the corresponding optional descriptions DD.sub.nm1 . . . DD.sub.nmr (83), the corresponding optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84), and the corresponding optional images ID.sub.nm1 . . . ID.sub.nmr (85), corresponding to the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) are typically associated correspondingly one with the other.

(426) The optional link LD.sub.nm1 (82), the corresponding optional description DD.sub.nm1 (83), the corresponding optional price/value PD.sub.nm1 (84), and the corresponding optional image ID.sub.nm1 (85), corresponding to the optional individual information group LG.sub.nmr (80) are typically associated correspondingly one with the other. The optional link LD.sub.nm2 (82), the corresponding optional description DD.sub.nm2 (83), the corresponding optional price/value PD.sub.nm2 (84), and the corresponding optional image ID.sub.nm2 (85), corresponding to the addressable individual information group LG.sub.nm2 (80) are typically associated correspondingly one with the other, and so on. The optional link LD.sub.nmr (82), the corresponding optional description DD.sub.nmr (83), the corresponding optional price/value PD.sub.nmr (84), and the corresponding optional image ID.sub.nmr (85), corresponding to the addressable individual information group LG.sub.nmr (80) are, thus, typically associated correspondingly one with the other.

(427) The addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80), which may have the corresponding optional links LD.sub.nm1 . . . LD.sub.nmr (82), and/or the corresponding optional descriptions DD.sub.nm1 . . . DD.sub.nmr (83), and/or the corresponding optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84), and/or the corresponding optional images ID.sub.nm1 . . . ID.sub.nmr (85) are appended with labels/identifiers, as shown in FIG. 68, and incorporated into certain ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), depending upon the grouping and/or sorting criteria. FIG. 69 shows a particular one of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), designated as the query information group GI.sub.nz (63).

(428) Now again, the optional addressable individual information group LG.sub.nmr (80) is associated with and corresponds to a particular one of the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) in a particular one of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57), designated as the addressable response information group RG.sub.nm (57). The first subscript of the optional addressable individual information groups LG.sub.nmr (80) is associated with and corresponds to the particular service and/or information request IQ.sub.n (28) and/or the user service and/or information request iq.sub.n (27). The second subscript of the optional addressable individual information groups LG.sub.nmr (80) is associated with and corresponds to a particular one of “1” through “m” i.e., 1 . . . m, of the addressable response information group RG.sub.n1 . . . RG.sub.nm (57). The third subscript of the optional addressable individual information groups LG.sub.nmr (80) is associated with and corresponds to a particular one of “1” through “r”, i.e., 1 . . . r, of the optional addressable individual information group LG.sub.nm1 . . . LG.sub.nmr (80) within the addressable response information group RG.sub.nm (57).

(429) FIG. 68 shows a labelled individual information group LL.sub.nzu (86) associated with a particular one of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), designated as the addressable query information group GI.sub.nz (63), having optional group identifier GL.sub.nc (87), optional query link identifier LN.sub.ncu (88), optional resource location identifier SU.sub.nw (89), optional server and/or query identifier SI.sub.nm (90), and/or optional server link identifier LX.sub.nmr (91) appended to the addressable individual information group LG.sub.nmr (80).

(430) The first alphanumeric subscript of the labelled individual information group LL.sub.nzu (86) is associated with and corresponds to the service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36). The second alphanumeric subscript of the labelled individual information group LL.sub.nzu (86) is associated with and corresponds to a particular one of “1” through “z”, i.e., 1 z, of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), designated as the addressable query information group GI.sub.nz (63), which the labelled individual information group LL.sub.nzu (86) is incorporated in. The third alphanumeric subscript of the labelled individual information group LL.sub.nzu (86) is associated with and corresponds to a particular one of “1” through “u”, i.e., 1 . . . u, of labelled individual information groups LL.sub.nz1 . . . LL.sub.nzu (86) within the addressable query information group GI.sub.nz (63).

(431) The optional group identifier GL.sub.nc (87) labels and/or identifies the current request group QA.sub.nc (50). The optional group identifier GL.sub.nc (87) is associated with and corresponds to the current request group QA.sub.nc (50), which may be any particular one the request groups QA.sub.n1 . . . QA.sub.nz (51) selected by the user U.sub.n (12). The first alphanumeric subscript of the optional group identifier GL.sub.nc (87) is associated with and corresponds to the service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36). The second subscript of the optional group identifier GL.sub.nc (87) is associated with and corresponds to the particular one of the request groups QA.sub.n1 . . . QA.sub.nz (51) selected by the user U.sub.n (12) as the current request group QA.sub.nc (50).

(432) The optional query link identifier LN.sub.ncu (88) is also associated with and corresponds to the current request group QA.sub.nc (50). The optional query link identifier LN.sub.ncu (88) labels and/or identifies the labelled individual information group LL.sub.nzu (86). The first alphanumeric subscript of the optional query link identifier LN.sub.ncu (88) is associated with and corresponds to the service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36). The second subscript of the optional query link identifier LN.sub.ncu (88) is also associated with and corresponds to the particular one of the request groups QA.sub.n1 . . . QA.sub.nz (51) selected by the user U.sub.n (12) as the current request group QA.sub.nc (50). The third alphanumeric subscript of the optional query link identifier LN.sub.ncu (88) is associated with and corresponds to a particular one of “1” through “u”, i.e., 1 . . . u, of the labelled individual information groups LL.sub.nz1 . . . LL.sub.nzu (86) in the addressable query information group GI.sub.nz (63).

(433) The optional resource location identifier SU.sub.nw (89) labels and/or identifies resource locations of information and/or services associated with and corresponding to the optional addressable individual information group LG.sub.nmr (80) in the labelled individual information group LL.sub.nzu (86).

(434) The optional resource location identifier SU.sub.nw (89) indicates and is associated with and corresponds to resource locations of information and/or services associated with certain ones of the optional servers SO.sub.1 . . . SO.sub.p (22) and/or certain ones of the servers S.sub.1 . . . S.sub.z (20) The optional resource location identifier SU.sub.nw (89) may be obtained from certain information in the optional addressable individual information group LG.sub.nmr (80). The first alphanumeric subscript of the optional resource location identifier SU.sub.nw (89) is associated with and corresponds to the service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36). The second alphanumeric subscript of the optional resource location identifier SU.sub.nw (89) is associated with and corresponds to a particular one of “1” through “w”, i.e., 1 . . . w, of the optional resource location identifiers SU.sub.n1 . . . SU.sub.nw (89) in the labelled individual information group LL.sub.nzu (86).

(435) The optional server and/or query identifier SI.sub.nm (90) labels and/or identifies the query QQ.sub.nm (53) and/or the corresponding server address AQ.sub.nm (54) associated with and corresponding to the optional addressable individual information group LG.sub.nmr (80) in the corresponding labelled individual information group LL.sub.nzu (86) of the current request group QA.sub.nc (50). The first alphanumeric subscript of the optional server and/or query identifier SI.sub.nm (90) is associated with and corresponds to the service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36). The second alphanumeric subscript of the optional server and/or query identifier SI.sub.nm (90) is associated with and corresponds to a particular one of “1” through “m”, i.e., 1 . . . m, of the optional server and/or query identifiers SI.sub.n1 . . . SI.sub.nm (90), which may be correspondingly associated with the corresponding ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) and/or the corresponding ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54).

(436) The optional server link identifier LX.sub.nmr (91) labels and/or identifies the location of the optional addressable individual information group LG.sub.nmr (80) in the corresponding addressable response information groups RG.sub.nm (57). The first alphanumeric subscript of the optional server link identifier LX.sub.nmr (91) is associated with and corresponds to the service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36). The second alphanumeric subscript of the optional server link identifier LX.sub.nmr (91) is associated with and corresponds to the addressable response information group RG.sub.nm (57). The third alphanumeric subscript of the optional server link identifier LX.sub.nmr (91) is associated with and corresponds to a particular one of “1” through “r”, i.e., 1 . . . r, of the optional server link identifiers LX.sub.nm1 . . . LX.sub.nmr (91), which may be correspondingly associated with the locations of certain ones of the optional addressable individual information group LG.sub.nm1 . . . LG.sub.nmr (80) in the addressable response information groups RG.sub.nm (57). The certain ones of the optional addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) in the addressable response information group RG.sub.nm (57), having information and/or services parsed and/or processed, and/or formatted, and/or grouped from the response R.sub.nm (32), which are labelled and/or identified with the optional server link identifiers LX.sub.n1 . . . LX.sub.nmr (91), are correspondingly associated with the locations of the information and/or services in the response R.sub.nm (32). The optional server link identifiers LX.sub.nm1 . . . LX.sub.nmr (91), thus, identify and/or label the location of services and/or information in the response R.sub.nm (32).

(437) FIG. 69 shows the addressable query information group GI.sub.nz (63) having the labelled individual information groups LL.sub.nz1 . . . LL.sub.nzu (86), optional database labelled individual information groups RL.sub.nz1 . . . RL.sub.nzx (92), optional query description QT.sub.nz (93), optional server descriptions and/or links ST.sub.nz1 . . . ST.sub.nzf (94), and optional advertisements and/or links LT.sub.nz1 . . . LT.sub.nzt (95). The first and second subscripts of the optional database labelled individual information groups RL.sub.nz1 . . . RL.sub.nzx (92), the optional query description QT.sub.nz (93), the optional server descriptions and/or links ST.sub.nz1 . . . ST.sub.nzf (94), and the optional advertisements and/or links LT.sub.nz1 . . . LT.sub.nzt (95) are associated with and correspond to the addressable query information group GI.sub.nz (63). The third subscripts of the optional database labelled individual information groups RL.sub.nz1 . . . RI.sub.nzx (92), the optional server descriptions and/or links ST.sub.nz1 . . . ST.sub.nzf (94), and the optional advertisements and/or links LT.sub.nz1 . . . LT.sub.nzt (95) are associated with and correspond to ones of the optional database labelled individual information groups RL.sub.nz1 . . . RL.sub.nzx (92), the optional server descriptions and/or links ST.sub.nz1 . . . ST.sub.nzf (94), and the optional advertisements and/or links LT.sub.nz1 . . . LT.sub.nzt (95), respectively.

(438) IV Process

(439) FIG. 70 shows steps of a client-server multitasking process 99 of the present invention. The client-server multitasking process 99 is shown for the client-server multitasking system 10 for a particular one of the users U . . . U.sub.n (12), designated as the user U.sub.n (12), the corresponding particular one of the user interfaces I . . . I.sub.n (14), designated as the user interface I.sub.n (14), the corresponding particular one of the clients C . . . C.sub.n (16), designated as the client C.sub.n (16), the server PS (18), the servers S.sub.1 . . . S.sub.z (20), and the optional servers SO.sub.1 . . . SO.sub.p (22), which reside on the network 24.

(440) The client-server multitasking process 99 starts at step 101. The user U.sub.n (12) enters the user input UI.sub.n (25) into the user interface I.sub.n (14) (step 102). The user input UI.sub.n (25) is formulated into the user service and/or information request iq.sub.n (27) at the user interface I.sub.n (14) and communicated to the client C.sub.n (16) (step 103). The user service and/or information request iq.sub.n (27) may be formulated into the service and/or information request IQ.sub.n (28) at the client C.sub.n (16) and communicated to the server PS (18) (also step 103).

(441) The service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36) are derived at the server PS (18) and/or the client C.sub.n (16), respectively, at step 104, which in itself is a process, and may hereinafter be referred to as the multitasking process 104. The multitasking process 104 will be discussed in more detail later with reference to FIGS. 71 and 72.

(442) Now, continuing with FIG. 70, the user service and/or information response ir.sub.n (36) may be derived at the client C.sub.n (16) (step 104) from the service and/or information response IR.sub.n (34), which may be communicated to the client C.sub.n (16) from the server PS (18) (also step 104), and/or alternatively and/or additionally from the responses R.sub.n1 . . . R.sub.nm (32), which may be communicated to the client C.sub.n (16) (step 104).

(443) Now, the client C.sub.n (16) may communicate the service and/or information request IQ.sub.n (28) to the server PS (18) (step 103). The service and/or information response IR.sub.n (34) is then derived at the server PS (18) (step 104) and communicated to the client C.sub.n (16) (also step 104). The user service and/or information response ir.sub.n (36) may be derived from the service and/or information response IR.sub.n (34) (also step 104).

(444) Now, in more detail, if the service and/or information request IQ.sub.n (28) is communicated to the server PS (18) (step 103), then the server PS (18) makes the requests Q.sub.n1 . . . Q.sub.nm (29) and/or certain ones of the requests Q.sub.n1 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) as the corresponding server designations S.sub.n1 . . . S.sub.nm (30), utilizing information from the service and/or information request IQ.sub.n (28). The service and/or information response IR.sub.n (34) is then derived at the server PS (18) (step 104) from the responses R.sub.n1 . . . R.sub.nm (32) received from the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.n1 . . . S.sub.nm (30), and communicated to the client C.sub.n (16). Now, again, the user service and/or information response ir.sub.n (36) may be derived from the service and/or information response IR.sub.n (34) (also step 104).

(445) Now, also in more detail, alternatively and/or additionally, the client C.sub.n (16) may make the requests Q.sub.n1 . . . Q.sub.nm (29) and/or certain other ones of the requests Q.sub.n1 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) as the corresponding server designations S.sub.n1 . . . S.sub.nm (30), utilizing information from the user service and/or information request iq.sub.n (27). Now, again, the user service and/or information response ir.sub.n (36) may also be derived at the client C.sub.n (16) (step 104) from the responses R.sub.n1 . . . R.sub.nm (32) communicated to the client C.sub.n (16) (step 104) and/or alternatively and/or additionally from the service and/or information response IR.sub.n (34) communicated to the client C.sub.n (16) from the server PS (18) (also step 104).

(446) The user service and/or information response ir.sub.n (36), thus, may be derived from the service and/or information response IR.sub.n (34) communicated from the server PS (18) to the client C.sub.n (16) and/or alternatively and/or additionally from the responses R.sub.n1 . . . R.sub.nm (32) communicated to the client C.sub.n (16) (step 104).

(447) The user service and/or information response ir.sub.n (36) is communicated to the user interface I.sub.n (14) (step 105) and incorporated into the user response UR.sub.n (37).

(448) The user U.sub.n (12) reviews the user response UR.sub.n (37) and/or selects additional services and/or information (step 106). Step 106 will be discussed in more detail later with reference to FIG. 76.

(449) The process 99 ends at step 107. The process 99 will be described in more detail with reference to FIGS. 1-147 of the drawings.

(450) The service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36) are derived at the server PS (18) and/or the client C.sub.n (16), respectively, at step 104 in FIG. 70, and shown in more detail in FIGS. 71 and 72.

(451) FIG. 71 shows the multitasking process 104 of deriving the service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36), with reference to FIGS. 59 and 63. FIG. 72 shows the multitasking process 104 of deriving the service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36) having other grouping/sorting that may be used additionally and/or alternatively to that of FIGS. 59 and 63, as shown with reference to FIGS. 60 and 64. The multitasking process 104 will also be described in more detail with reference to FIGS. 1-147 of the drawings.

(452) The server PS (18) and/or the client C.sub.n (16) parse, process, and/or format the service and/or information request IQ.sub.n (28) and/or the user service and/or information request iq.sub.n (27) into the current request group QA.sub.nc (50), the request groups QA.sub.n1 . . . QA.sub.nz (51), and the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) (step 104-1), as shown in FIGS. 71 and 72.

(453) Information from the current request group QA.sub.nc (50) and the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) may be used to make the requests Q.sub.n1 . . . Q.sub.nm (29), obtain the responses R.sub.n1 . . . R.sub.nm (32), and incorporate information therefrom into the service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36), as shown in FIGS. 71 and 72 with reference to FIGS. 59, 60, 63, and 64. The current request group QA.sub.nc (50) may be any particular one the request groups QA.sub.n1 . . . QA.sub.nz (51), which may be selected by the user U.sub.n (12).

(454) The current request group QA.sub.nc (50) has the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) to open connections with and make the requests Q.sub.n1 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) as the corresponding server designations S.sub.n1 . . . S.sub.nm (30), shown for the particular service and/or information request IQ.sub.n (28) and/or the particular user service and/or information request iq.sub.n (27).

(455) The server PS (18) and/or the client C.sub.n (16) open connections with and make the requests Q.sub.n1 . . . Q.sub.nm (29) having the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) in the current request group QA.sub.nc (50) of the servers S.sub.1 . . . S.sub.z (20) (step 104-2) as shown in FIGS. 71 and 72, in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) as the corresponding server designations S.sub.n1 . . . S.sub.nm (30).

(456) The servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.n1 . . . S.sub.nm (30), designated in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) as the corresponding server designations S.sub.11 . . . S.sub.nm (30), respond to the requests Q.sub.n1 . . . Q.sub.nm (29) with the corresponding responses R.sub.n1 . . . R.sub.nm (32).

(457) The server PS (18) and/or the client C.sub.n (16) parse, and/or process, and/or format, and/or group, and/or organize each of the responses R.sub.n1 . . . R.sub.nm (32) received from the servers S.sub.1 . . . S.sub.z (20) (step 104-3), as shown in FIGS. 71 and 72 with reference to FIGS. 105-107, corresponding to the server designations S.sub.n1 . . . S.sub.nm (30) into the corresponding addressable response information groups RG.sub.n1 . . . RG.sub.nm (57).

(458) The server PS (18) and/or the client C.sub.n (16) may also make additional optional requests QP.sub.n1 . . . QP.sub.nm (58) of the optional databases 41 and/or 42 (also step 104-2 of FIGS. 71 and 72), which may be optionally resident within the server PS (18) and/or the client C.sub.n (16), and which may reply with the corresponding additional optional responses RA.sub.n1 . . . RA.sub.nm (40). The server PS (18) and/or the client C.sub.n (16) parse, and/or process, and/or format, and/or group, and/or organize each of the additional optional responses RA.sub.n1 . . . RA.sub.nm (40) into the corresponding response information groups RC.sub.n1 . . . RC.sub.nm (59) (also step 104-3 of FIGS. 71 and 72).

(459) Now, step 104-3 of FIGS. 71 and 72 is shown in more detail in FIG. 73.

(460) As discussed later, and shown in FIGS. 105-107, entity body RH.sub.nm (353) of the response R.sub.nm (32) has optional response individual information groups LS.sub.nm1 . . . LS.sub.nmr (360).

(461) Each of the optional response individual information groups LS.sub.n11 . . . LS.sub.nmr (360) and/or portions thereof from the entity bodies RH.sub.n1 . . . RH.sub.nm (353) of the responses R.sub.n1 . . . R.sub.nm (32) may be optionally compared one with the other, and duplicate ones of the optional response individual information groups LS.sub.n11 . . . LS.sub.nmr (360) may be optionally discarded (step 104-3-1), as shown in FIG. 73. The remaining optional response individual information groups LS.sub.n11 . . . LS.sub.nmr (360) are parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into corresponding ones of the addressable individual information groups LG.sub.n11 . . . LG.sub.nmr (80) as the addressable individual information groups LG.sub.n11 . . . LG.sub.nmr (80) are incorporated into the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) from the responses R.sub.n1 . . . R.sub.nm (32) (step 104-3-2), as shown in FIG. 73.

(462) The addressable individual information groups LG.sub.n11 . . . LG.sub.nmr (80) are typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other, as the addressable individual information groups LG.sub.n11 . . . LG.sub.nmr (80) are incorporated into the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) from the responses R.sub.n1 . . . R.sub.nm (32).

(463) The server PS (18) and/or the client C.sub.n (16) may formulate information from the current request group QA.sub.nc (50) having the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) into the corresponding request pointer/address group QZ.sub.n (60) having the pointers/addresses PG.sub.n1 . . . PG.sub.nz (61) associated therewith (step 104-4 of FIG. 71 with reference to FIGS. 59, 63, and 97). Alternatively and/or additionally, the server PS (18) and/or the client C.sub.n (16) may formulate information from the current request group QA.sub.nc (50) having the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) into a corresponding request pointer/address group QY.sub.n (68) having the pointers/addresses PF.sub.n11 . . . PF.sub.nmr (69) associated therewith (step 104-4 of FIG. 72 with reference to FIGS. 60 and 64).

(464) The server PS (18) and/or the client C.sub.n (16) may formulate the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) (step 104-5 of FIG. 71 with reference to FIGS. 59, 63, 97, and 102, and typical ones of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) in FIGS. 98 and 99), depending upon the grouping and/or sorting criteria used. Each of the pointers/addresses PG.sub.n1 . . . PG.sub.nz (61) may be directed to point/address the corresponding addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) associated therewith, which aid in obtaining information and/or services from certain ones of addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) to be incorporated into addressable query information groups GI.sub.n1 . . . GI.sub.nz (63).

(465) Each of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) has the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) directed to address/point information in the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) based upon the grouping and/or sorting criteria.

(466) The grouping and/or sorting criteria may be incorporated into the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), which may be entered into the user interface I.sub.n (14) through the user input UI.sub.n (25) by the user U.sub.n (12). Grouping and/or sorting criteria may additionally and/or alternatively optionally resident within the server PS (18) and/or the client C.sub.n (16).

(467) The grouping and/or sorting criteria gives the user U.sub.n (12) the ability to formulate the query information groups GI.sub.n1 . . . GI.sub.nz (63) and the way in which information and/or services from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is presented to the user U.sub.n (12) through the user interface I.sub.n (14).

(468) Information and/or services within each of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is addressed with the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) from the query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), and information and/or services from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is incorporated into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) corresponding to the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) (step 104-6 of FIG. 71), which are formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), in accordance with the grouping and/or sorting criteria, as shown in FIG. 71 with reference to FIGS. 59, 63, 66A, 66B, 66C, 67-69, 97, and 102, typical ones of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) in FIGS. 98 and 99, and a typical one of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), designated as the addressable query information group GI.sub.nz (63), in FIG. 109.

(469) Alternatively and/or additionally, each of the pointers/addresses PF.sub.n11 . . . PF.sub.nmr (69) may directed to point/address the corresponding addressable response information groups RG.sub.n1 . . . RG.sub.nm (57), and aid in obtaining information and/or services from the corresponding addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) to be incorporated into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) (step 104-6) as shown FIG. 72 with reference to FIGS. 60, 64, 66A, 66B, 66C, and 67-69, and another typical one of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), designated as the addressable query information group GI.sub.nz (63), in FIG. 110.

(470) Now, step 104-6 of FIG. 71 is shown in more detail in FIG. 74 with reference to FIGS. 59, 63, 66A, 66B, 66C, 67-69, 97, and 102, typical ones of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) in FIGS. 98 and 99, and a typical one of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), designated as the addressable query information group GI.sub.nz (63), in FIG. 109. Step 104-6 of FIG. 72 is shown in more detail in FIG. 75 with reference to FIGS. 60, 64, 66A, 66B, 66C, and 67-69, and another typical one of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), designated as the addressable query information group GI.sub.nz (63), in FIG. 110.

(471) The optional addressable individual information groups LG.sub.n11 . . . LG.sub.nmr (80) in each of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) may be addressed with the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) (step 104-6-1) as shown FIG. 74 with reference to FIGS. 59 and 63 and FIG. 71.

(472) The optional addressable individual information groups LG.sub.n11 . . . LG.sub.nmr (80) in each of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) may alternatively and/or additionally be addressed with the pointers/addresses PF.sub.n11 . . . PF.sub.nmr (69) (step 104-6-1) as shown FIG. 75 with reference to FIGS. 60 and 64 and FIG. 72.

(473) The addressed optional addressable individual information groups LG.sub.n11 . . . LG.sub.nmr (80) and/or portions thereof may be optionally labelled with labels and/or identifiers and incorporated into the labelled individual information groups LL.sub.nz1 . . . LL.sub.nzu (86) (step 104-6-2), as shown in FIGS. 74 and 75.

(474) The labelled individual information groups LI.sub.nz1 . . . LL.sub.nzu (86) may be incorporated into certain ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63), depending upon the grouping and/or sorting criteria (step 104-6-3), as shown in FIGS. 74 and 75.

(475) The addressed optional addressable individual information groups LG.sub.n11 . . . LG.sub.nmr (80) and/or portions thereof are typically appended with the labels and/or identifiers, thus creating the labelled individual information groups LL.sub.nz1 . . . LL.sub.nzu (86), as each of the labelled individual information groups LL.sub.nz1 . . . LL.sub.nzu (86) are incorporated into the certain ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63). The steps 104-6-2 and 104-6-3 are thus typically consolidated into a single step.

(476) The addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) may then be incorporated into the service and/or information response IR.sub.n (34) (step 104-7), as shown in FIGS. 71 and 72 with reference to FIG. 61, and/or the user service and/or information response ir.sub.n (36) (also step 104-7), as also shown in FIGS. 71 and 72 but with reference to FIG. 65.

(477) The user U.sub.n (12) reviews the user response UR.sub.n (37) the user interface I.sub.n (14) and/or selects additional services and/or information at step 106 in FIG. 70, and shown in more detail in FIG. 76. The step 106 will also be described in more detail with reference to FIGS. 1-147 of the drawings.

(478) The user U.sub.n (12) selects additional services and/or information through the user interface I.sub.n (14) (step 106-1) or exits to the end of the process 99 at step 107. If the user U.sub.n (12) selects additional services and/or information through the user interface I.sub.n (14) (step 106-1), the user U.sub.n (12) may optionally enter one or more orders into an order form and/or order forms at and through the user interface I.sub.n (14) (step 106-2). The order and/or orders may be, for example, for purchases, and/or instructions, and/or payment, and/or other information and/or services to be directed to and/or requested of third parties, and/or combinations thereof, of the optional servers SO.sub.1 . . . SO.sub.p (22), and/or the servers S.sub.1 . . . S.sub.z (20), and/or other ones of the clients C.sub.1 . . . C.sub.n (16) through the server PS (18) and/or the client C.sub.n (16). The order and/or orders may, thus, be placed through and by the server PS (18) and/or the client C.sub.n (16), eliminating the need for the user U.sub.n (12) to place separate ones of the orders with the third parties, the optional servers SO.sub.1 . . . SO.sub.p (22), and/or the servers S.sub.1 . . . S.sub.z (20) separately and/or individually.

(479) The server PS (18) and/or the client C.sub.n (16) process the orders and/or communicate the orders to the third parties, the optional servers SO.sub.1 . . . SO.sub.p (22), and/or the servers S.sub.1 . . . S.sub.z (20), and/or other ones of the clients C.sub.1 . . . C.sub.n (16) (step 106-3). The server PS (18) and/or the client C.sub.n (16) confirm the order (step 106-4). The user U.sub.n (12) may select additional services and/or information through the user interface I.sub.n (14) (step 106-1) or exit to the end of the process 99 at step 107.

(480) If the user U.sub.n (12) selects additional services and/or information through the user interface I.sub.n (14) (step 106-1), the user U.sub.n (12) may alternatively and/or additionally optionally enter information and/or service requests of the optional servers SO.sub.1 . . . SO.sub.p (22), and/or the servers S.sub.1 . . . S.sub.z (20) through the user interface I.sub.n (14) (step 106-5) and/or exit to the end of the process 99 at step 107.

(481) If the user U.sub.n (12) selects additional services and/or information through the user interface I.sub.n (14) (step 106-1), the user U.sub.n (12) may alternatively and/or additionally optionally enter additional requests as the user input UI.sub.n (25) at and through the user interface I.sub.n (14) (step 106-6) and enter the process 99 at step 102.

(482) V. Additional Details

(483) A. User Input

(484) The user input UI.sub.n (25), which the user U.sub.n (12) makes through the user interface I.sub.n (14), may have one or a plurality of the same and/or different ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) to be made by the server PS (18) and/or the client C.sub.n (16) of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) as the corresponding server designations S.sub.n1 . . . S.sub.nm (30) at the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54).

(485) The server PS (18) and/or the client C.sub.n (16) parse, process, format, sort, group, and/or organize each of the responses R.sub.n1 . . . R.sub.nm (32) to the corresponding requests Q.sub.n1 . . . Q.sub.nm (29), received from the servers S.sub.1 . . . S.sub.z (20) designated by the server designations S.sub.n1 . . . S.sub.nm (30), and/or each of the additional optional responses RA.sub.n1 . . . RA.sub.nm (40) from the server PS (18) and/or the client C.sub.n (16). The parsed, processed, formatted, sorted, grouped, and/or organized results from the server PS (18) and/or the client C.sub.n (16) are communicated to the user U.sub.n (12) through the user interface I.sub.n (14) as the user response UR.sub.n (37), which the user U.sub.n (12) may review, interact with, and/or select additional services and/or information therefrom.

(486) The user U.sub.n (12) enters the user input UI.sub.n (25) having one or more of the same and/or different user requests qu.sub.n1 . . . qu.sub.nu (26) into the user interface I.sub.n (14), as shown in FIG. 3. The user requests qu.sub.n1 . . . qu.sub.nu (26) are communicated from the user interface I.sub.n (14) to the client C.sub.n (16) within the user service and/or information request iq.sub.n (27), having the user requests qu.sub.n1 . . . qu.sub.nu (26) and other optional information.

(487) The user U.sub.n (12) may enter the user input UI.sub.n (25) having one or more of the same and/or different user requests qu.sub.n1 . . . qu.sub.nu (26) into the service and/or information entry request form IE.sub.n (38) at the user interface I.sub.n (14), or into the user interface I.sub.n (14) through other suitable means.

(488) The user interfaces I.sub.1 . . . I.sub.n (14) have suitable input means and/or suitable presentation and/or display means, which allow the corresponding users U.sub.1 . . . U.sub.n (12) to communicate with the corresponding clients C.sub.1 . . . C.sub.n (16). FIGS. 5A, 5B, and 6-10 show 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), as graphical user interfaces (GUI's), which the users U.sub.1 . . . U.sub.n (12) may enter the corresponding user inputs UI.sub.1 . . . UI.sub.n (25) thereinto. FIGS. 77 and 78 are schematic representations of the service and/or information entry request form IE.sub.n (38) showing fields, links, and elements of the service and/or information entry request form IE.sub.n (38).

(489) The user U.sub.n (12) may enter the user input UI.sub.n (25) into the service and/or information entry request form IE.sub.n (38) at the user interface I.sub.n (14), as shown schematically in FIG. 77. The user input UI.sub.n (25) may be entered as user input values into fields or alternate request links of the service and/or information entry request form IE.sub.n (38).

(490) The user U.sub.n (12) may enter the user input UI.sub.n (25) as one or more of the same and/or different user requests qu.sub.n1 . . . qu.sub.nu (26), which may have the query values QV.sub.n1 . . . QV.sub.nz (200), server name values AV.sub.n1 . . . AV.sub.nu (201), optional instruction values VV.sub.n1 . . . VV.sub.nu (202), and/or alternate request links QL.sub.n1 . . . QL.sub.na (203), and/or server request links UL.sub.n1 . . . UL.sub.ns (204), and/or the additional request links SL.sub.n1 . . . SL.sub.nw (71) into the service and/or information entry request form IE.sub.n (38).

(491) The user input UI.sub.n (25), thus, has one or more of the same and/or different user requests qu.sub.n1 . . . qu.sub.nu (26), which may be entered as the query values QV.sub.n1 . . . QV.sub.nu (200) of the same and/or different servers S.sub.1 . . . S.sub.z (20), designated in accordance with the designation scheme corresponding to the corresponding certain ones of the server designations S.sub.11 . . . S.sub.nm (30) having the corresponding server name values AV.sub.n1 . . . AV.sub.nu (201), the optional instruction values VV.sub.n1 . . . VV.sub.nu (202), and/or the alternate request links QL.sub.n1 . . . QL.sub.na (203), and/or the server request links UL.sub.n1 . . . UL.sub.ns (204), and/or the additional request links SL.sub.n1 . . . SL.sub.nw (71) into the service and/or information entry request form IE.sub.n (38).

(492) Each of the different user requests qu.sub.n1 . . . qu.sub.nu (26) may be the same and/or different one from the other. Each of the query values QV.sub.n1 . . . QV.sub.nu (200) may be the same and/or different one from the other. The query values QV.sub.n1 . . . QV.sub.nu (200) may be entered for the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20). The optional instruction values VV.sub.n1 . . . VV.sub.nu (202) may be the same and/or different one from the other.

(493) The user U.sub.n (12) may also enter the user input UI.sub.n (25) and request services and/or information through one of the alternate request links QL.sub.n1 . . . QL.sub.na (203), or one of the server request links UL.sub.n1 . . . UL.sub.ns (204), or one of the additional request links SL.sub.n1 . . . SL.sub.nw (71) at the user interface I.sub.n (14).

(494) B. User Interface Details

(495) The client-server multitasking system 10 of the present invention may have any suitable user interface I.sub.n (14) acceptable to and/or preferred by the user U.sub.n (12), and acceptable to the client C.sub.n (16). The user interface I.sub.n (14) may be, for example, a graphical user interface, visual, aural, and/or tactile user interface, and/or combination thereof, or other suitable interface. The user interface I.sub.n (14) may be integral with the client C.sub.n (16) or separate therefrom.

(496) The user interface I.sub.n (14) may be hardware based, and/or computer based, and/or process based, and/or a combination thereof, and may be a graphical user interface, such as, for example, a browser and/or combinations thereof, varieties of which are commonly used on the internet.

(497) The service and/or information entry request form IE.sub.n (38) may be optionally available to the user U.sub.n (12) at the user interface I.sub.n (14), or the user U.sub.n (12) may optionally request the service and/or information entry request form IE.sub.n (38) through the user interface I.sub.n (14).

(498) Now, as shown in FIGS. 5A, 5B, and 6-10 and schematically in FIGS. 77 and 78, the service and/or information entry request form IE.sub.n (38) at the user interface I.sub.n (14) has user client request fields QD.sub.n1 . . . QD.sub.nu (206) accessible to the user U.sub.n (12) and hidden client request elements HU.sub.n1 . . . HU.sub.nh (207) hidden from the user U.sub.n (12). The user client request fields QD.sub.n1 . . . QD.sub.nu (206) accessible to the user U.sub.n (12) has server requests portion 208, optional instructions portion 209, an optional execute request element 210, and alternate requests portion 212. The hidden client request elements HU.sub.n1 . . . HU.sub.nh (207) hidden from the user U.sub.n (12) have optional server requests portion 214, optional instructions portion 216, and optional information element HE.sub.n (218).

(499) The server requests portion 208 of the user client request fields QD.sub.n1 . . . QD.sub.nu (206) accessible to the user U.sub.n (12) has server query fields QF.sub.n1 . . . QF.sub.nu (220), which the user U.sub.n (12) may enter corresponding server query values QV.sub.n1 . . . QV.sub.nu (200) thereinto, as a portion of the user input UI.sub.n (25).

(500) The user U.sub.n (12) may also optionally enter the server name values AV.sub.n1 . . . AV.sub.nu (201) into server name fields AF.sub.n1 . . . AF.sub.nu (224). The user U.sub.n (12) may enter the server name values AV.sub.n1 . . . AV.sub.nu (201) as another portion of the user input UI.sub.n (25).

(501) The user U.sub.n (12) may also optionally enter the optional instruction values VV.sub.n1 . . . VV.sub.nz (202) into optional instruction fields VF.sub.n1 . . . VF.sub.nz (228) of the optional instructions portion 209 of the user client request fields QD.sub.n1 . . . QD.sub.nu (206) accessible to the user U.sub.n (12). The user U.sub.n (12) may enter the optional instruction values VV.sub.n1 . . . VV.sub.nz (202) as yet another portion of the user input UI.sub.n (25).

(502) Upon the user U.sub.n (12) entering the user input UI.sub.n (25) of the server query values QV.sub.n1 . . . QV.sub.nu (200) and/or the server name values AV.sub.n1 . . . AV.sub.nu (201) and/or the optional instruction values VV.sub.n1 . . . VV.sub.nz (202) into the service and/or information entry request form IE.sub.n (38) at the user interface I.sub.n (14), the completed service and/or information request form IF.sub.n (230) results, shown schematically in FIGS. 79 and 80.

(503) The user U.sub.n (12) may instruct the user interface I.sub.n (14) to communicate the user service and/or information requests iq.sub.n (27), shown in FIG. 80, having the server query values QV.sub.n1 . . . QV.sub.nu (200) and/or the server name values AV.sub.n1 . . . AV.sub.nu (201) and/or the optional instruction values VV.sub.n1 . . . VV.sub.nv (202), from the already completed service and/or information request form IF.sub.n (230) at the user interface I.sub.n (14) to the client C.sub.n (16) by entering the optional execute request element 210, using a point and click device, such as a mouse, light pen, tactile monitor, by entering a carriage return, through other user interface controls, or through other suitable means. FIG. 81 shows a schematic representation of the user service and/or information request iq.sub.n (27).

(504) The user U.sub.n (12) may alternatively enter the alternate request links QL.sub.n1 . . . QL.sub.na (203) or the server request links UL.sub.n1 . . . UL.sub.ns (204) or the additional request links SL.sub.n1 . . . SL.sub.nw (71) into the service and/or information entry request form IE.sub.n (38) with a point and click device, such as a mouse, a light pen, tactile monitor, or with alternative and/or other user interface controls or other suitable means, and instruct the user interface I.sub.n (14) to communicate the user service and/or information request iq.sub.n (27), having information associated with the alternate request links QL.sub.n1 . . . QL.sub.na (203) or the server request links UL.sub.n1 . . . UL.sub.ns (204) or the additional request links SL.sub.n1 . . . SL.sub.nw (71), to the client C.sub.n (16).

(505) The server name fields AF.sub.n1 . . . AF.sub.nu (224) and the optional instruction fields VF.sub.n1 . . . VF.sub.nv (228) of the service and/or information entry request form IE.sub.n (38) may optionally have the server name values AV.sub.n1 . . . AV.sub.nu (201) and/or the optional instruction values VV.sub.n1 . . . VV.sub.nv (202) entered thereinto, respectively, as changeable and/or fixed pre-set or preselected values, drop down menu selections, and/or as blank fields, or a combination thereof. The preselected values may be replaced with values of the user's U.sub.n (12) choice or may remain fixed, depending upon choices offered in the service and/or information entry request form IE.sub.n (38). The drop down menu selections may be changed to ones of a number of preselected choices offered in the drop down menu selections, which the user U.sub.n (12) may optionally scroll through to determine which choice to make. Blank ones of the server name fields AF.sub.n1 . . . AF.sub.nu (224) and/or blank ones of the optional instruction fields VF.sub.n1 . . . VF.sub.nv (228) allow the user U.sub.n (12) to optionally enter the server name values AV.sub.n1 . . . AV.sub.nu (201) and/or the optional instruction values VV.sub.n1 . . . VV.sub.nv (202), respectively, therein, accordingly.

(506) The server query fields QF.sub.n1 . . . QF.sub.nu (220), which the user U.sub.n (12) enters the corresponding server query values QV.sub.n1 . . . QV.sub.nu (200) thereinto, through the user input UI.sub.n (25), may also have changeable and/or fixed preselected values, drop down menu selections, and/or blank fields, or a combination thereof. However, the server query fields QF.sub.n1 . . . QF.sub.nu (220) may generally be presented to the user U.sub.n (12) as blank fields, at least for the first user input UI.sub.n (25).

(507) The alternate requests portion 212 of the user client request fields QD.sub.n1 . . . QD.sub.nu (206) accessible to the user U.sub.n (12) has the alternate request links QL.sub.n1 . . . QL.sub.na (203), the server request links UL.sub.n1 . . . UL.sub.ns (204), and the additional request links SL.sub.n1 . . . SL.sub.nw (71). The user U.sub.n (12) may alternatively request services and/or information through one of the alternate request links QL.sub.n1 . . . QL.sub.na (203), or one of the server request links UL.sub.n1 . . . UL.sub.ns (204), or one of the additional request links SL.sub.n1 . . . SL.sub.nw (71).

(508) The alternate request links QL.sub.n1 . . . QL.sub.na (203) allow the user U.sub.n (12) to make the service and/or information request IQ.sub.1 . . . IQ.sub.n (28) with preconfigured optional default selections already placed in the service and/or information request IQ.sub.1 . . . IQ.sub.n (28) for the user U.sub.n (12). The server request links UL.sub.n1 . . . UL.sub.nw (204) may be advertisements, advertising links, and/or links to ones of the optional servers SO.sub.1 . . . SO.sub.p (22). The user U.sub.n (12) may, for example, make requests for additional services and/or information from ones of the optional servers SO.sub.1 . . . SO.sub.p (22), using the server request links UL.sub.n1 . . . UL.sub.nw (204). The additional request links SL.sub.n1 . . . SL.sub.nw (71) allow the user U.sub.n (12) to make additional optional selections, based upon information and/or services previously requested by the user U.sub.n (12).

(509) The optional server requests portion 214 of the hidden client request elements HU.sub.n1 . . . HU.sub.nh (207) hidden from the user U.sub.n (12) has hidden query elements Qh.sub.n1 . . . Qh.sub.nh (236) and corresponding associated hidden server name elements Ah.sub.n1 . . . Ah.sub.nh (238). The optional instructions portion 216 of the hidden client request elements HU.sub.n1 . . . HU.sub.nh (207) hidden from the user U.sub.n (12) may have optional hidden instruction elements Vh.sub.n1 . . . Vh.sub.ni (240). The hidden client request elements HU.sub.n1 . . . HU.sub.nh (207) hidden from the user U.sub.n (12) may also have the hidden optional information element HE.sub.n (218), which may have optional information and/or statistics.

(510) The user U.sub.n (12) may, thus, request the services and/or information by completing entry of the server requests portion 208 and the optional instructions portion 209 with the optional execute request element 210, after entering the server query values QV.sub.n1 . . . QV.sub.nu (200) and/or the server name values AV.sub.n1 . . . AV.sub.nu (201) and/or the optional instruction values VV.sub.n1 . . . VV.sub.nz (202), or by alternatively requesting the services and/or information through one of the alternate request links QL.sub.n1 . . . QL.sub.na (203), or one of the server request links UL.sub.n1 . . . UL.sub.ns (204), or one of the additional request links SL.sub.n1 . . . SL.sub.nw (71).

(511) Upon completion of the user input UI.sub.n (25), the completed service and/or information request form IF.sub.n (230), as shown in FIGS. 79 and 80, has user client request elements QM.sub.n1 . . . QM.sub.nu (246) accessible to the user U.sub.n (12) having server request elements 242 and optional instruction elements VE.sub.n1 . . . VE.sub.nz (244); and/or alternate request elements 248 of the user client request elements QM.sub.n1 . . . QM.sub.nu (246) accessible to the user U.sub.n (12); and/or optional server request elements 250, optional instruction elements 252, and/or hidden client request elements HP.sub.n1 . . . HP.sub.nh (256) hidden from the user U.sub.n (12).

(512) The user U.sub.n (12) may instruct the user interface I.sub.n (14) to communicate the user service and/or information request iq.sub.n (27) derived from the service and/or information request form IF.sub.n (230) to the client C.sub.n (16), as shown in FIG. 81, with the optional execute request element 210 or with the other suitable means; or the user U.sub.n (12) may alternatively communicate the user service and/or information request iq.sub.n (27) by entering the alternate request links QL.sub.n1 . . . QL.sub.na (203) or the server request links UL.sub.n1 . . . UL.sub.ns (204) or the additional request links SL.sub.n1 . . . SL.sub.nz (71) into the service and/or information entry request form IE.sub.n (38) or into the completed service and/or information request form IF.sub.n (230) with a point and click device, such as a mouse, a light pen, tactile monitor, or with alternative and/or other user interface controls or other suitable means, and instruct the user interface I.sub.n (14) to communicate the user service and/or information request iq.sub.n (27), having information associated with the alternate request links QL.sub.n1 . . . QL.sub.na (203) or the server request links UL.sub.n1 . . . UL.sub.ns (204) or the additional request links SL.sub.n1 . . . SL.sub.nw (71), to the client C.sub.n (16).

(513) FIGS. 79 and 80 are schematic representations of the completed service and/or information entry request form IF.sub.n (230) showing typical elements, values, field names, name-value pairs, optional instructions, and alternate requests, resulting from the user U.sub.n (12) entering the user input UI.sub.n (25) of the server query values QV.sub.n1 . . . QV.sub.nu (200) and/or the server name values AV.sub.n1 . . . AV.sub.nu (201) and/or the optional instruction values VV.sub.n1 . . . VV.sub.nz (202) into the service and/or information entry request form IE.sub.n (38) at the user interface I.sub.n (14).

(514) Now, the completed service and/or information entry request form IF.sub.n (230) has the user client request elements QM.sub.n1 . . . QM.sub.nu (246) accessible to the user U.sub.n (12) having the server request elements 242, which has query elements QE.sub.n1 . . . QE.sub.nu (258) and corresponding associated server name elements AE.sub.n1 . . . AE.sub.nu (260).

(515) Each of the query elements QE.sub.n1 . . . QE.sub.nu (258) have query field names QN.sub.n1 . . . QN.sub.nu (262) of the associated corresponding server query fields QF.sub.n1 . . . QF.sub.nu (220) and the corresponding server query values QV.sub.n1 . . . QV.sub.nu (200) associated therewith, which the requests Q.sub.11 . . . Q.sub.nm (29) may be derived therefrom.

(516) Each of the server name elements AE.sub.n1 . . . AE.sub.nu (260) have server field names AN.sub.n1 . . . AN.sub.nm (264) of the associated corresponding server name fields AF.sub.n1 . . . AF.sub.nu (224) and the corresponding server name values AV.sub.n1 . . . AV.sub.nu (201) associated therewith, which server addresses A.sub.n1 . . . A.sub.nu (265) may be derived therefrom.

(517) The user client request elements QM.sub.n1 . . . QM.sub.nu (246) accessible to the user U.sub.n (12) also have the optional instruction elements VE.sub.n1 . . . VE.sub.nv (244) having optional instruction field names VN.sub.n1 . . . VN.sub.nv (266) of the associated corresponding optional instruction fields VF.sub.n1 . . . VF.sub.nv (228) and the corresponding optional instruction values VV.sub.n1 . . . VV.sub.nu (202) associated therewith.

(518) The user client request elements QM.sub.n1 . . . QM.sub.nu (246) accessible to the user U.sub.n (12) also have the alternate request elements 246 having the alternate request links QL.sub.n1 . . . QL.sub.na (203), or the server request links UL.sub.n1 . . . UL.sub.ns (204), or the additional request links SL.sub.n1 . . . SL.sub.nw (71).

(519) The hidden client request elements HP.sub.n1 . . . HP.sub.nh (256) hidden from the user U.sub.n (12) have the hidden query elements Qh.sub.n1 . . . Qh.sub.nh (236), which may have hidden query field names Qn.sub.n1 . . . Qn.sub.nh (268) and corresponding hidden query values Qv.sub.n1 . . . Qv.sub.nh (270) associated therewith. The hidden server name elements Ah.sub.n1 . . . Ah.sub.nh (238) may have hidden server field names An.sub.n1 . . . An.sub.nh (272) and corresponding server hidden request name values Av.sub.n1 . . . Av.sub.nh (274) associated therewith.

(520) The hidden client request elements HP.sub.n1 . . . HP.sub.nh (256) hidden from the user U.sub.n (12) may also have the optional hidden instruction elements Vh.sub.n1 . . . Vh.sub.ni (240), which may have optional hidden instruction field names Vn.sub.n1 . . . Vn.sub.ni (275) and corresponding optional hidden instruction values Vv.sub.n1 . . . Vv.sub.ni (276) associated therewith. The hidden client request elements HP.sub.n1 . . . HP.sub.nh (256) hidden from the user U.sub.n (12) may also have the hidden optional information element HE.sub.n (218), which may have optional hidden information element field name Jn.sub.n (277) and optional hidden information element value Jv.sub.n (278) associated therewith.

(521) Now again, the user interfaces I.sub.1 . . . I.sub.n (14) may each be different, one from the other, or the same, and may change characteristics over time. Each of the user interfaces I.sub.1 . . . I.sub.n (14) may change characteristics as a function of time, information, and/or instructions, and/or other means, which may be derived by the users U.sub.1 . . . U.sub.n (12) and/or the clients C.sub.1 . . . C.sub.n (16) and/or the servers S.sub.1 . . . S.sub.z (20), and/or the server PS (18), and/or the optional servers SO.sub.1 . . . SO.sub.p (22), and/or derived within the user interfaces I.sub.1 . . . I.sub.n (14). The user interface I.sub.1 . . . I.sub.n (14) may change state.

(522) The user interface I.sub.1 . . . I.sub.n (14) may also change as a function of optional timers and/or timed instructions associated with the user interfaces I.sub.1 . . . I.sub.n (14), and/or associated with the clients C.sub.1 . . . C.sub.n (16) and/or associated with the servers S.sub.1 . . . S.sub.z (20), and/or associated with the server PS (18), and/or associated with the optional servers SO.sub.1 . . . SO.sub.p (22), and/or instructions from the user U.sub.1 . . . U.sub.n (12). Changes in the user interface I.sub.n (14) may appear continuous to the user U.sub.n (12), spaced in time, staccato, or static depending upon the optional timers and/or the timed instructions. Other conditions may change the user interface I.sub.1 . . . I.sub.n (14), as well.

(523) The user interfaces I.sub.1 . . . I.sub.n (14) may be updated continuously, intermittently, manually, randomly, semi-automatically, automatically, repetitively, non-repetitively, singly, plurally, multiplexed, and/or a combination thereof or other suitable manner.

(524) The user interfaces I.sub.1 . . . I.sub.n (14) may be visual, such as graphical user interfaces, aural, and/or tactile, a combination thereof, and/or other suitable means. The user interfaces I.sub.1 . . . I.sub.n (14) may be integral with the clients C.sub.1 . . . C.sub.n (16) or separate therefrom.

(525) The user interfaces I.sub.1 . . . I.sub.n (14) may change in response to the user inputs UI.sub.1 . . . UI.sub.n (25), 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), the completed service and/or information request forms IF.sub.n (230), the user service and/or information requests iq.sub.1 . . . iq.sub.n (27), the optional execute request elements 210, accessing the alternate request links QL.sub.11 . . . QL.sub.1a (203), accessing the server request links UL.sub.11 . . . UL.sub.1s (204), accessing the additional request links SL.sub.11 . . . SL.sub.1w (71), the service and/or information responses IR.sub.1 . . . IR.sub.n (34), the service and/or information response forms IS.sub.1 . . . IS.sub.n (39). Other conditions may change the user interface I.sub.1 . . . I.sub.n (14), as well.

(526) Portions of the user responses UR.sub.1 . . . UR.sub.n (37) may be mapped into and/or onto different portions of the user interfaces I.sub.1 . . . I.sub.n (14) to facilitate interaction with and the needs of each of the users U.sub.1 . . . U.sub.n (12). Such mappings may be optionally customized by the users U.sub.1 . . . U.sub.n (12).

(527) C. Service and/or Information Request Details

(528) Each of the users U.sub.1 . . . U.sub.n (12) communicate the corresponding user service and/or information requests iq.sub.1 . . . iq.sub.n (27) through the corresponding user interfaces I.sub.1 . . . I.sub.n (14) to 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 the corresponding service and/or information requests IQ.sub.1 . . . IQ.sub.n (28), as required.

(529) Now, again, the user U.sub.n (12) may instruct the user interface I.sub.n (14) to communicate the user service and/or information requests iq.sub.n (27), having the server query values QV.sub.n1 . . . QV.sub.nu (200) and/or the server name values AV.sub.n1 . . . AV.sub.nu (201) and/or the optional instruction values VV.sub.n1 . . . VV.sub.nv (202), from the already completed service and/or information request form IF.sub.n (230) at the user interface I.sub.n (14) to the client C.sub.n (16) by entering the optional execute request element 210, using a point and click device, such as a mouse, light pen, tactile monitor, by entering a carriage return, through other user interface controls, or through other suitable means. FIG. 81 shows a schematic representation of the user service and/or information request iq.sub.n (27).

(530) The user U.sub.n (12) may alternatively enter the alternate request links QL.sub.n1 . . . QL.sub.na (203) or the server request links UL.sub.n1 . . . UL.sub.ns (204) or the additional request links SL.sub.n1 . . . SL.sub.nw (71) into the service and/or information entry request form IE.sub.n (38) with a point and click device, such as a mouse, a light pen, tactile monitor, or with alternative and/or other user interface controls or other suitable means, and instruct the user interface I.sub.n (14) to communicate the user service and/or information request iq.sub.n (27), having information associated with the alternate request links QL.sub.n1 . . . QL.sub.na (203) or the server request links UL.sub.n1 . . . UL.sub.ns (204) or the additional request links SL.sub.n1 . . . SL.sub.nw (71), to the client C.sub.n (16).

(531) The user service and/or information request iq.sub.n (27) is communicated from the user interface I.sub.n (14) to the client C.sub.n (16), which acts upon the user service and/or information request iq.sub.n (27) to derive the service and/or information request IQ.sub.n (28) therefrom. FIGS. 81-86 are schematic representations of the service and/or information request IQ.sub.n (28) and/or the user service and/or information request iq.sub.n (27).

(532) The service and/or information request IQ.sub.n (28) has information and/or elements, which may be used by the server PS (18) to make the requests Q.sub.n1 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the ones of 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). The client C.sub.n (16) may additionally and/or alternatively make the requests Q.sub.n1 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), using information and/or elements within the user service and/or information request iq.sub.n (27).

(533) The service and/or information request IQ.sub.n (28) has user client requests QC.sub.n1 . . . QC.sub.nu (280) accessible to the user U.sub.n (12) and hidden client requests HC.sub.n1 . . . HC.sub.nh (281) hidden from the user U.sub.n (12).

(534) The user client requests QC.sub.n1 . . . QC.sub.nu (280) accessible to the user U.sub.n (12) and/or the hidden client requests HC.sub.n1 . . . HC.sub.nh (281) hidden from the user U.sub.n (12) have address and/or location information and/or instructions, and/or other information corresponding to information and/or services to be requested of the servers S.sub.1 . . . S.sub.z (20), and/or information and/or instructions to be utilized by the server PS (18) and/or ones of the clients C.sub.1 . . . C.sub.n (16).

(535) The user client requests QC.sub.n1 . . . QC.sub.nu (280) accessible to the user U.sub.n (12) have server requests portion SQ.sub.n (282), optional instructions portion V.sub.n (283), and alternate request portion AL.sub.n (284).

(536) The hidden client requests HC.sub.n1 . . . HC.sub.nh (281) hidden from the user U.sub.n (12) has optional hidden server requests portion HQ.sub.n (285), optional hidden instructions portion HO.sub.n (286), and optional hidden information portion J.sub.n (287).

(537) The server requests portion SQ.sub.n (282) of the service and/or information request IQ.sub.n (28) has queries QS.sub.n1 . . . QS.sub.nu (288), which may be derived from the query field names QN.sub.n1 . . . QN.sub.nu (262) and the corresponding server query values QV.sub.n1 . . . QV.sub.nu (200) of the query elements QE.sub.n1 . . . QE.sub.nu (258).

(538) The server requests portion SQ.sub.n (282) of the service and/or information request IQ.sub.n (28) may also have the server addresses A.sub.n1 . . . A.sub.nu (265), which may be derived from the server field names AN.sub.n1 . . . AN.sub.nm (264) and the corresponding server name values AV.sub.n1 . . . AV.sub.nu (201) of the server name elements AE.sub.n1 . . . AE.sub.nu (260).

(539) The optional instructions portion VO.sub.n (283) of the user client requests QC.sub.n1 . . . QC.sub.nu (280) accessible to the user U.sub.n (12) of the service and/or information request IQ.sub.n (28) may have optional instructions V.sub.n1 . . . V.sub.nv (289), which may be derived from the optional instruction field names VN.sub.n1 . . . VN.sub.nv (266) and the corresponding optional instruction values VV.sub.n1 . . . VV.sub.nu (202). The optional instructions V.sub.n1 . . . V.sub.nv (289) may optionally be used by the client C.sub.n (16) and/or the server PS (18), and/or incorporated into the requests Q.sub.n1 . . . Q.sub.nm (29) to be made of the servers S.sub.1 . . . S.sub.z (20) designated by the server designations S.sub.n1 . . . S.sub.nm (30), corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) associated with the user U.sub.n (12).

(540) The alternate request portion AL.sub.n (284) of the user client requests QC.sub.n1 . . . QC.sub.nu (280) accessible to the user U.sub.n (12) of the service and/or information request IQ.sub.n (28) may be derived from one of the alternate request links QL.sub.n1 . . . QL.sub.na (203), or one of the server request links UL.sub.n1 . . . UL.sub.ns (204), or one of the additional request links SL.sub.n1 . . . SL.sub.nw (71).

(541) The optional hidden server requests portion HQ.sub.n1 . . . HQ.sub.nh (281) of the hidden client requests HC.sub.n1 . . . HC.sub.nh (281) hidden from the user U.sub.n (12) may have hidden queries QH.sub.n1 . . . QH.sub.nh (290) and corresponding hidden server addresses AH.sub.n1 . . . AH.sub.nh (291).

(542) The hidden queries QH.sub.n1 . . . QH.sub.nh (290) of the optional hidden server requests portion HQ.sub.n1 . . . HQ.sub.nh (281) of the service and/or information request IQ.sub.n (28) may be derived from the hidden query field names Qn.sub.n1 . . . Qn.sub.nh (268) and the corresponding hidden query values Qv.sub.n1 . . . Qv.sub.nh (270).

(543) The hidden server addresses AH.sub.n1 . . . AH.sub.nh (291) of the optional hidden server requests portion HQ.sub.n1 . . . HQ.sub.nh (281) of the service and/or information request IQ.sub.n (28) may be derived from the hidden server field names An.sub.n1 . . . An.sub.nh (272) and the corresponding server hidden server name values Av.sub.n1 . . . Av.sub.nh (274).

(544) The hidden queries QH.sub.n1 . . . QH.sub.nh (290) may optionally be appended to the queries QS.sub.n1 . . . QS.sub.nu (288) to be made of the servers S.sub.1 . . . S.sub.z (20). The hidden server addresses AH.sub.n1 . . . AH.sub.nh (291) may optionally be appended to the server addresses A.sub.n1 . . . A.sub.nu (265). The appended queries QS.sub.n1 . . . QS.sub.nu (288) may then be made of the servers S.sub.1 . . . S.sub.z (20) designated by the server designations S.sub.n1 . . . S.sub.nm (30), corresponding to the resulting appended requests Q.sub.n1 . . . Q.sub.nm (29) associated with the user U.sub.n (12), in accordance with the appended server addresses A.sub.n1 . . . A.sub.nu (265).

(545) The appended requests Q.sub.n1 . . . Q.sub.nm (29) will hereinafter be used synonymously with the requests Q.sub.n1 . . . Q.sub.nm (29), the appended queries QS.sub.n1 . . . QS.sub.nu (288) will hereinafter be used synonymously with the queries QS.sub.n1 . . . QS.sub.nu (288), and the appended server addresses A.sub.n1 . . . A.sub.nu (265) will hereinafter be used synonymously with the server addresses A.sub.n1 . . . A.sub.nu (265).

(546) The optional hidden instructions portion HO.sub.n (286) of the hidden client requests HC.sub.n1 . . . HC.sub.nh (281) hidden from the user U.sub.n (12) of the service and/or information request IQ.sub.n (28) have optional hidden instructions H.sub.n1 . . . H.sub.ni (292), which may be derived from the hidden instruction field names Vn.sub.n1 . . . Vn.sub.ni (275) and the corresponding optional hidden instruction values Vv.sub.n1 . . . Vv.sub.ni (276). The optional hidden instructions H.sub.n1 . . . H.sub.ni (292) may optionally be appended to the optional instructions V.sub.n1 . . . V.sub.nv (289) and/or may optionally be used by the client C.sub.n (16) and/or the server PS (18), and/or incorporated into the requests Q.sub.n1 . . . Q.sub.nm (29) to be made of the servers S.sub.1 . . . S.sub.z (20) designated by the server designations S.sub.n1 . . . S.sub.nm (30), corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) associated with the user U.sub.n (12). The appended instructions V.sub.n1 . . . V.sub.nv (289) will hereinafter be used synonymously with the instructions V.sub.n1 . . . V.sub.nv (289).

(547) The optional hidden information portion J.sub.n (287) of the hidden client requests HC.sub.n1 . . . HC.sub.nh (281) hidden from the user U.sub.n (12) of the service and/or information request IQ.sub.n (28) may be derived from the optional hidden information element field name Jn.sub.n (277) and the optional hidden information element value Jv.sub.n (278), and may optionally be used by the client C.sub.n (16) and/or the server PS (18), and/or incorporated into the requests Q.sub.n1 . . . Q.sub.nm (29) to be made of the servers S.sub.1 . . . S.sub.z (20) designated by the server designations S.sub.n1 . . . S.sub.nm (30), corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) associated with the user U.sub.n (12).

(548) Now, again, each of the users U.sub.1 . . . U.sub.n (12) communicate the corresponding user service and/or information requests iq.sub.1 . . . iq.sub.n (27) through the corresponding user interfaces I.sub.1 . . . I.sub.n (14) to 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 the corresponding service and/or information requests IQ.sub.1 . . . IQ.sub.n (28), as required.

(549) The user service and/or information requests iq.sub.1 . . . iq.sub.n (27) may be communicated from the 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) to the clients C.sub.1 . . . C.sub.n (16) or alternatively from the service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38) at the corresponding user interfaces I.sub.1 . . . I.sub.n (14) through the alternate request links QL.sub.11 . . . QL.sub.na (203) or the server request links UL.sub.11 . . . UL.sub.ns (204) or the additional request links SL.sub.11 . . . SL.sub.nz (71).

(550) The user service and/or information requests iq.sub.1 . . . iq.sub.n (27) may be communicated as the elements, values, field names, optional instructions, and/or alternate requests entered into the completed service and/or information entry request form IF.sub.n (230) from the corresponding user interfaces I.sub.1 . . . I.sub.n (14) to the corresponding clients C.sub.1 . . . C.sub.n (16).

(551) The users U.sub.1 . . . U.sub.n (12) may, thus, communicate the corresponding user service and/or information requests iq.sub.1 . . . iq.sub.n (27) to the clients C.sub.1 . . . C.sub.n (16) through the user interfaces I.sub.1 . . . I.sub.n (14), upon entering the corresponding user inputs UI.sub.1 . . . UI.sub.n (25) into the corresponding service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38) at the corresponding user interfaces I.sub.1 . . . I.sub.n (14). The completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230) are derived from the user inputs UI.sub.1 . . . UI.sub.n (25) having the corresponding user service and/or information requests iq.sub.1 . . . iq.sub.n (27), which may be entered as values or alternate requests thereinto the corresponding service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38).

(552) The user U.sub.1 . . . U.sub.n (12) may alternatively communicate the user service and/or information requests iq.sub.1 . . . iq.sub.n (27) by entering the alternate request links QL.sub.11 . . . QL.sub.na (203) or the server request links UL.sub.11 . . . UL.sub.ns (204) or the additional request links SL.sub.11 . . . SL.sub.nw (71) into the service and/or information entry request form IE.sub.1 . . . IE.sub.n (38) or into the completed service and/or information request form IF.sub.1 . . . IF.sub.n (230).

(553) The server PS (18) and/or the C.sub.n (16) may alternatively and/or additionally use information resident within the server PS (18) and/or the client C.sub.n (16), such as default information, and/or information communicated from the user U.sub.n (12) through the user interface I.sub.n (14) to the client C.sub.n (16) to make the requests Q.sub.n1 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the ones of 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).

(554) FIG. 87 is a schematic representation showing queries QQ.sub.n1 . . . QQ.sub.nm (53) and corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54). FIGS. 88-91 show the schematic representation of FIG. 87 having typical values.

(555) D. Optional Instructions

(556) Typically, information within the optional instructions V.sub.11 . . . V.sub.nv (289), and/or the optional hidden instructions H.sub.11 . . . H.sub.ni (292), and/or the optional hidden information portion J.sub.n (287) are used by the server PS (18) and/or specific ones of the clients C.sub.1 . . . C.sub.n (16), but may also be used by the servers S.sub.1 . . . S.sub.z (20).

(557) Now, in yet more detail, the user inputs UI.sub.1 . . . UI.sub.n (25) may have one or more of the same and/or different optional instruction values VV.sub.11 . . . VV.sub.nv (202). The optional instruction values VV.sub.11 . . . VV.sub.nv (202) may typically have instructions, which may be used by the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), such as, for example, as instructions on how to request, organize, present and/or display, and/or retrieve services and/or information from the servers S.sub.1 . . . S.sub.z (20) and/or other suitable instructions.

(558) Typical information that may be incorporated into the optional instruction values VV.sub.n1 . . . VV.sub.nv (202) may include, for example, Searches per Group 311 and Group 312, shown in FIGS. 5A, 5B, and 6-10 for a particular one of the service and/or information entry request forms IE.sub.n (38) at the user interface I.sub.n (14) shown in FIGS. 81-86.

(559) The Searches per Group 311 is considered to be the number of the server query values QV.sub.n1 . . . QV.sub.nu (200), associated with corresponding ones of the server name values AV.sub.n1 . . . AV.sub.nu (201), corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) to make of the servers S.sub.1 . . . S.sub.z (20). The Group 312 is considered to be the group of the server query values QV.sub.n1 . . . QV.sub.nu (200) to communicate to ones of the servers S.sub.1 . . . S.sub.z (20) associated with the corresponding ones of the server name values AV.sub.n1 . . . AV.sub.nu (201), in accordance with the designation scheme corresponding to the corresponding ones of the server designations S.sub.n1 . . . S.sub.nm (30), corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29).

(560) Page 313, which includes certain service and/or information location information, which may be incorporated into the requests Q.sub.n1 . . . Q.sub.nm (29) to be made of the associated corresponding 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.n1 . . . S.sub.nm (30), may also be typically incorporated into the optional instruction values VV.sub.n1 . . . VV.sub.nv (202).

(561) Timeout per Search Engine 314, which is substantially the maximum time for the server PS (18) and/or the particular client C.sub.n (16) making the requests Q.sub.n1 . . . Q.sub.nm (29) to wait for each of the responses R.sub.n1 . . . R.sub.nm (32) from certain ones of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) as the corresponding server designations S.sub.n1 . . . S.sub.nm (30), may also be typically incorporated into the optional instruction values VV.sub.n1 . . . VV.sub.nv (202).

(562) URL's per Search Engine 315, which is the number of links and/or descriptions to be returned to the user interface I.sub.n (14) from each of the responses R.sub.n1 . . . R.sub.nm (32), may also be typically incorporated into the optional instruction values VV.sub.n1 . . . VV.sub.nv (202). Search Engine Results 316 and URL Details 317, each of which designate different presentation and/or display schemes to be presented at the user interface I.sub.n (14), may also be typically incorporated into the optional instruction values VV.sub.n1 . . . VV.sub.nv (202).

(563) In those instance in which, for example, the service and/or information entry request form IE.sub.n (38) at the user interface I.sub.n (14) has only one entry field for one of the requests Q.sub.n1 (29), as in FIGS. 6, 8, and 10, and the optional instruction values VV.sub.11 . . . VV.sub.nv (202) are not visible, the server PS (18) and/or the particular client C.sub.n (16) may then have default values resident therein for the Searches per Group 311, and/or the Group 312, and/or the Page 313, and/or the Timeout per Search Engine 314, and/or the URL's per Search Engine 315, and/or the Search Engine Results 316, and/or the URL Details 317, and/or other suitable ones of the optional instruction values VV.sub.11 . . . VV.sub.nv (202), and/or the server PS (18) and/or the particular client C.sub.n (16) may establish the default values, and/or the default values may be incorporated into the optional hidden instruction values Vv.sub.n1 . . . Vv.sub.ni (276).

(564) The server PS (18) and/or the particular client C.sub.n (16) may make the requests Q.sub.n1 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), according to the designation scheme corresponding to the corresponding ones of the server designations S.sub.n1 . . . S.sub.nm (30), and the optional instruction values VV.sub.n1 . . . VV.sub.nv (202), typically having the Searches per Group 311, and/or the Group 312, and/or the Page 313, and/or the Timeout per Search Engine 314, and/or the URL's per Search Engine 315, and/or the Search Engine Results 316, and/or the URL Details 317, and/or the default values which may be established or be resident within the server PS (18) and/or the particular client C.sub.n (16), and/or the optional hidden instruction values Vv.sub.n1 . . . Vv.sub.ni (276), and/or other information incorporated into the hidden client request elements HP.sub.n1 . . . HP.sub.nh (256) hidden from the user U.sub.n (12).

(565) E. Communicating the Service and/or Information Requests

(566) Now, each of the users U.sub.1 . . . U.sub.n (12) communicate the corresponding user service and/or information requests iq.sub.1 . . . iq.sub.n (27) through the corresponding user interfaces I.sub.1 . . . I.sub.n (14) to 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 the corresponding service and/or information requests IQ.sub.1 . . . IQ.sub.n (28). The clients C.sub.1 . . . C.sub.n (16) communicate the corresponding service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) to the server PS (18) and/or use the corresponding user service and/or information requests iq.sub.1 . . . iq.sub.n (27) internally to formulate the requests Q.sub.11 . . . Q.sub.nm (29).

(567) F. Parsing, Processing, and/or Formatting the Service and/or Information Requests

(568) The server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) parse, process, and/or format the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) into the requests Q.sub.11 . . . Q.sub.nm (29), the optional instructions VJ.sub.11 . . . VJ.sub.nk (52), and information to open connections OC.sub.11 . . . OC.sub.nm (323). FIG. 92 shows a particular one of the requests Q.sub.nm (29), the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and the information to open connections OC.sub.11 . . . OC.sub.nm (323), which may be parsed, processed, and/or formatted from a particular one of the service and/or information requests IQ.sub.n (28). The clients C.sub.1 . . . C.sub.n (16) may alternatively and/or additionally parse, process, and/or format the user service and/or information requests iq.sub.1 . . . iq.sub.n (27) directly into the requests Q.sub.11 . . . Q.sub.nm (29), and/or the optional instructions VJ.sub.11 . . . VJ.sub.nk (52) and the information required to open the connections OC.sub.11 . . . OC.sub.nm (323), as required.

(569) Upon receipt of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) at the server PS (18), communicated from the clients C.sub.1 . . . C.sub.n (16), the server PS (18) parses, processes, and/or formats each of the corresponding service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) into the corresponding queries QQ.sub.11 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54) to open connections OC.sub.11 . . . OC.sub.nm (323) with and make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), and/or the optional instructions VJ.sub.11 . . . VJ.sub.nk (52) to be used by the server PS (18) in making the requests Q.sub.11 . . . Q.sub.nm (29) and/or in processing, formatting, grouping, and organizing the responses R.sub.11 . . . R.sub.nm (32) from the ones of the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.11 . . . S.sub.nm (30), and/or the additional optional responses RA.sub.11 . . . RA.sub.nm (40), into the corresponding service and/or information responses IR.sub.1 . . . IR.sub.n (34), as shown in FIG. 92.

(570) Alternatively and/or additionally, upon receipt of the user service and/or information requests iq.sub.1 . . . iq.sub.n (27) at the corresponding clients C.sub.1 . . . C.sub.n (16), the corresponding clients C.sub.1 . . . C.sub.n (16) may parse, process, and/or format each of the user service and/or information requests iq.sub.1 . . . iq.sub.n (27) into corresponding queries QQ.sub.11 . . . QQ.sub.nm (53) and corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54) to open connections OC.sub.11 . . . OC.sub.nm (323) with and make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), and/or the optional instructions VJ.sub.11 . . . VJ.sub.nk (52) to be used by the corresponding clients C.sub.1 . . . C.sub.n (16) in making the requests Q.sub.11 . . . Q.sub.nm (29) and/or in processing, formatting, grouping, and organizing the responses R.sub.11 . . . R.sub.nm (32) from the ones of the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.11 . . . S.sub.nm (30), and/or the additional optional responses RA.sub.11 . . . RA.sub.nm (40), into the corresponding user service and/or information responses ir.sub.1 . . . ir.sub.n (36).

(571) The server PS (18) parses, processes, and/or formats each of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) into queries, server addresses to make the queries of, query groups and/or server groups, and instructions to be used by the server PS (18), typically when the server PS (18) makes the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.11 . . . S.sub.nm (30) and/or the server PS (18) processes, formats, groups, and organizes the responses R.sub.11 . . . R.sub.nm (32) from the ones of the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.11 . . . S.sub.nm (30) at the server PS (18). Otherwise, the clients C.sub.1 . . . C.sub.n (16) may parse, process, and/or format each of the user service and/or information requests iq.sub.1 . . . iq.sub.n (27) into queries, server addresses to make the queries of, query groups and/or server groups, and instructions, typically when the clients C.sub.1 . . . C.sub.n (16) make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.11 . . . S.sub.nm (30) and/or the clients C.sub.1 . . . C.sub.n (16) process, format, group, and organize the responses R.sub.11 . . . R.sub.nm (32) from the ones of the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.11 . . . S.sub.nm (30) at the corresponding clients C.sub.1 . . . C.sub.n (16). Choice as to whether the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) makes the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20) corresponding to the server designations S.sub.11 . . . S.sub.nm (30) and/or process, format, group, and organize the responses R.sub.11 . . . R.sub.nm (32) are dependent on processing capabilities of the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) and other factors.

(572) Ones of the requests Q.sub.11 . . . Q.sub.nm (29) may require further formatting and/or processing by the server PS (18) and/or the corresponding clients C.sub.1 . . . C.sub.n (16), and/or other ones of the requests Q.sub.11 . . . Q.sub.nm (29) may already be formatted in accordance with requirements with respect to communications protocols, the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28), the servers S.sub.1 . . . S.sub.z (20), and/or the optional servers SO.sub.1 . . . SO.sub.p (22), and/or the server PS (18), and/or other requirements of the network 24 of the client-server multitasking system 10. The server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) parse, process, and/or format the requests Q.sub.11 . . . Q.sub.nm (29), as required.

(573) G. Formulating the Requests

(574) Each of the optional instructions VJ.sub.11 . . . VJ.sub.nk (52) is typically parsed, and/or processed, and/or formatted, and/or grouped, and/or organized into particular ones of the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) for use by the server PS (18) and/or particular ones of the clients C.sub.1 . . . C.sub.n (16), a particular one of the clients C.sub.1 . . . C.sub.n (16) being designated as the client C.sub.n (16).

(575) Each of the alternate request links QL.sub.n1 . . . QL.sub.na (203) and the additional request links SL.sub.11 . . . SL.sub.nw (71) are also typically parsed, and/or processed, and/or formatted, and/or grouped, and/or organized for use by the server PS (18) and/or particular ones of the clients C.sub.1 . . . C.sub.n (16), a particular one of the clients C.sub.1 . . . C.sub.n (16) being designated as the client C.sub.n (16).

(576) The alternate request links QL.sub.n1 . . . QL.sub.na (203) allow the user U.sub.n (12) to make the service and/or information request IQ.sub.1 . . . IQ.sub.n (28) with preconfigured optional default selections already placed in the service and/or information request IQ.sub.1 . . . IQ.sub.n (28) for the user U.sub.n (12). The additional request links SL.sub.n1 . . . SL.sub.nw (71) allow the user U.sub.n (12) to make additional optional selections, based upon information and/or services previously requested by the user U.sub.n (12).

(577) Typical ones of the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) and the additional request links SL.sub.n1 . . . SL.sub.nw (71) that may be parsed, processed, and/or formatted from the service and/or information request IQ.sub.n (28) and/or the user service and/or information request iq.sub.n (27) are shown in FIG. 96.

(578) The requests Q.sub.11 . . . Q.sub.nm (29) may be made by the server PS (18) and/or the corresponding clients C.sub.1 . . . C.sub.n (16) of the associated corresponding ones of the servers S.sub.1 . . . S.sub.z (20), according to the designation scheme corresponding to the corresponding ones of the server designations S.sub.11 . . . S.sub.nm (30), in accordance with the optional instructions VJ.sub.11 . . . VJ.sub.nk (52) and/or default values for the optional instructions VJ.sub.11 . . . VJ.sub.nk (52) resident within the server PS (18) and/or the corresponding clients C.sub.1 . . . C.sub.n (16).

(579) The service and/or information responses IR.sub.1 . . . IR.sub.n (34) and/or the corresponding user service and/or information responses ir.sub.1 . . . ir.sub.n (36) may be formulated by the server PS (18) and/or the corresponding clients C.sub.1 . . . C.sub.n (16), in accordance with the optional instructions VJ.sub.11 . . . VJ.sub.nk (52) and/or default values for the optional instructions VJ.sub.11 . . . VJ.sub.nk (52) resident within the server PS (18) and/or the corresponding clients C.sub.1 . . . C.sub.n (16).

(580) The optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) and the additional request links SL.sub.11 . . . SL.sub.nw (71) for a particular one of the service and/or information requests IQ.sub.n (28) may typically have Searches per Group 326, and/or Group 327, and/or Page 328A and/or Page 328B, and/or Timeout per Search Engine 329, and/or URL's per Search Engine 330, and/or Search Engine Results 331A and/or Search Display 331B, and/or URL Details 332A and/or Description and/or List 332B, as shown in FIG. 96. Default values may additionally and/or alternatively be established or be resident for any and/or all of the optional instructions VJ.sub.11 . . . VJ.sub.nk (52) within the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16).

(581) The Searches per Group 326 are typically considered to be the number of the queries QQ.sub.n1 . . . QQ.sub.nm (53) to make of the servers S.sub.1 . . . S.sub.z (20) at the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to make the requests Q.sub.n1 . . . Q.sub.nm (29) of as the corresponding ones of the server designations S.sub.n1 . . . S.sub.nm (30).

(582) The Group 327 is considered to be the group of the queries QQ.sub.n1 . . . QQ.sub.nm (53) to make of the servers S.sub.1 . . . S.sub.z (20) at the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to make the requests Q.sub.n1 . . . Q.sub.nm (29) of as the corresponding ones of the server designations S.sub.n1 . . . S.sub.nm (30).

(583) The Page 328A and the Page 328B have certain service and/or information location information, which may be incorporated into the requests Q.sub.n1 . . . Q.sub.nm (29) to be made of the associated corresponding ones of the servers S.sub.1 . . . S.sub.z (20), at the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54), in accordance with the designation scheme corresponding to the corresponding ones of the server designations S.sub.n1 . . . S.sub.nm (30).

(584) The Timeout per Search Engine 329 is considered to be substantially the maximum time for the server PS (18) and/or the particular client C.sub.n (16) making the requests Q.sub.n1 . . . Q.sub.nm (29) to wait for each of the responses R.sub.n1 . . . R.sub.nm (32) from certain ones of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) as the corresponding server designations S.sub.n1 . . . S.sub.nm (30).

(585) The URL's per Search Engine 330, is considered to be the number of links, and/or descriptions, and/or prices/values, and/or images to be returned to the user interface I.sub.n (14) from each of the responses R.sub.n1 . . . R.sub.nm (32).

(586) The Search Engine Results 331A and the Search Display 331B each designate presentation and/or display schemes to be presented at the user interface I.sub.n (14). The URL Details 332A and the Description and/or List 332B each also designate presentation and/or display schemes to be presented at the user interface I.sub.n (14).

(587) FIG. 133 is a schematic representation of certain typical optional instructions VJ.sub.nm1 . . . VJ.sub.nk (52) and/or certain additional request links SL.sub.n1 . . . SL.sub.nz (71), referred to as the Search Engine Results 331A, which are shown to be Interleave 331A-1, Separate 331A-2, Combine $[a-z] 331A-3, Combine $[z-a] 331A-4, Separate $[a-z] 331A-5, Separate $[z-a] 331A-6, which are instructions for parsing, processing, sorting, and/or formatting the service and/or information response IR.sub.n (34).

(588) FIG. 134 is a schematic representation of other certain typical optional instructions VJ.sub.nm1 . . . VJ.sub.nk (52) and/or other certain additional request links SL.sub.n1 . . . SL.sub.nz (71), referred to as the URL Details 332A, which are other instructions for parsing, processing, sorting, and/or formatting the service and/or information response IR.sub.n (34) in Summary 332A-1 or List 332A-2 formats.

(589) FIG. 135 depicts certain typical additional request links SL.sub.n1 . . . SL.sub.nw (71), and also shows the Search Display 331B, which are shown to be Interleave 331B-1, Separate 331B-2, Combine $[a-z] 331B-3, Combine $[z-a] 331B-4, Separate $[a-z] 331B-5, Separate $[z-a] 331B-6, which are instructions for parsing, processing, sorting, and/or formatting the service and/or information response IR.sub.n (34) and the Description and/or List 332B, which are other instructions for parsing, processing, sorting, and/or formatting the service and/or information response IR.sub.n (34) in Summary or List formats.

(590) The optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) may also typically have Next Group 333 and Previous Group 334, which are considered to be the next group and the previous group, respectively, to make the queries QQ.sub.n1 . . . QQ.sub.nm (53) thereof at the next and previous ones of the corresponding groups of the queries QQ.sub.n1 . . . QQ.sub.nm (53) to make of the servers S.sub.1 . . . S.sub.z (20) thereof at the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to make the requests Q.sub.n1 . . . Q.sub.nm (29) thereof as the corresponding ones of the server designations S.sub.n1 . . . S.sub.nm (30). Information about Current Group 337 having the queries QQ.sub.n1 . . . QQ.sub.nm (53) and the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) is also shown. Current Page Number 338 is also indicated.

(591) The optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) for a particular one of the service and/or information requests IQ.sub.n (28) may also typically have Next Page 335 and Previous Page 336, each of which has certain different service and/or information location information, which may be incorporated into the requests Q.sub.n1 . . . Q.sub.nm (29) to be made of the associated corresponding 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.n1 . . . S.sub.nm (30).

(592) H. Determining Queries and Servers to Make the Requests Thereof

(593) The server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) evaluate the optional instructions VJ.sub.11 . . . VJ.sub.nk (52), determine the queries QQ.sub.11 . . . QQ.sub.nm (53) and the servers S.sub.1 . . . S.sub.z (20) to make the requests Q.sub.11 . . . Q.sub.nm (29) thereof at the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with as the server designations S.sub.11 . . . S.sub.nm (30), corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), and group the queries QQ.sub.11 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54) associated therewith.

(594) FIG. 96 shows typical ones of the queries QQ.sub.11 . . . QQ.sub.nm (53), the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54), and the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) that may be parsed, processed, and/or formatted from the service and/or information request IQ.sub.n (28) and/or the user service and/or information request iq.sub.n (27).

(595) The queries QQ.sub.11 . . . QQ.sub.nm (53) and the servers S.sub.1 . . . S.sub.z (20) to make the requests Q.sub.11 . . . Q.sub.nm (29) thereof are typically based upon the values designated in and parsed from the queries QQ.sub.11 . . . QQ.sub.nm (53) and the values designated in and parsed from the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with as the server designations S.sub.11 . . . S.sub.nm (30), corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), and the Searches per Group 326, the Group 327, the Page 328A and/or the Page 328B within the optional instructions VJ.sub.11 . . . VJ.sub.nk (52).

(596) The server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) evaluate the values in the Group 327, the Searches per Group 326, the queries QQ.sub.11 . . . QQ.sub.nm (53), and the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54), and determine the servers S.sub.1 . . . S.sub.z (20) corresponding to the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54) within the Group 327, in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with as the server designations S.sub.11 . . . S.sub.nm (30) to make the requests Q.sub.11 . . . Q.sub.nm (29) thereof, and the Page 328A and/or the Page 328B.

(597) The Group 327 and the Searches per Group 326 are used to determine which of the servers S.sub.1 . . . S.sub.z (20) to make the requests Q.sub.11 . . . Q.sub.nm (29) thereof.

(598) The server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) determine the size of the Group 327 from the Searches per Group 326 and the Group 327, and the servers S.sub.1 . . . S.sub.z (20) associated with the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54) within the Group 327, in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with as the server designations S.sub.11 . . . S.sub.nm (30).

(599) The Searches per Group 326 and the Group 327 are used to formulate the current request groups QA.sub.1c . . . QA.sub.nc (50) having the corresponding queries QQ.sub.11 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54) to open connections with and make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.11 . . . Q.sub.nm (29) thereof as the server designations S.sub.11 . . . S.sub.nm (30), corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), for corresponding ones of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) and/or the user service and/or information requests iq.sub.1 . . . iq.sub.n (27).

(600) The queries QQ.sub.11 . . . QQ.sub.nm (53), the server addresses AQ.sub.11 . . . AQ.sub.nm (54), and the Page 328A and/or the Page 328B provide the location of information and/or services to the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) within the Group 327, in accordance with the Searches per Group 326, to make the requests Q.sub.11 . . . Q.sub.nm (29) thereof, in accordance with the designation scheme which designates the ones of the servers S.sub.1 . . . S.sub.z (20) to make the requests Q.sub.11 . . . Q.sub.nm (29) thereof as the server designations S.sub.11 . . . S.sub.nm (30), corresponding to the requests Q.sub.11 . . . Q.sub.nm (29).

(601) The URL's per Search Engine 330 determine whether the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) communicate additional ones of the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), depending upon the number of the links, and/or descriptions, and/or prices/values, and/or images requested by ones of the user U.sub.1 . . . U.sub.n (12) to be returned to the user interfaces I.sub.1 . . . I.sub.n (14), and the number of links, and/or descriptions, and/or prices/values, and/or images available within each of the corresponding ones of the responses R.sub.11 . . . R.sub.nm (32). If insufficient ones of the links, and/or descriptions, and/or prices/values, and/or images are not available within the responses R.sub.11 . . . R.sub.nm (32) to satisfy delivery of the number of the URL's per Search Engine 330 requested by certain ones the users U.sub.1 . . . U.sub.n (12), the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) may yet make additional ones of the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in order deliver the number of the links, and/or descriptions, and/or prices/values, and/or images requested in the number of the URL's per Search Engine 330 to the user interfaces I.sub.1 . . . I.sub.n (14) requested by certain ones of the user U.sub.1 . . . U.sub.n (12).

(602) If the optional instructions do not indicate which ones of the servers S.sub.1 . . . S.sub.z (20) to make the requests Q.sub.11 . . . Q.sub.nm (29) thereof, in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with as the server designations S.sub.11 . . . S.sub.nm (30), corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), default values may be used. The default values may be resident within the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16).

(603) If all and/or a portion of the optional instructions VJ.sub.11 . . . VJ.sub.nk (52) are absent and/or are not communicated to the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), default values may be used. The default values may be resident within the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16).

(604) I. Grouping the Queries and Sorting/Grouping Criteria

(605) Upon receipt of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) at the server PS (18), communicated from the corresponding clients C.sub.1 . . . C.sub.n (16), the server PS (18) parses, processes, and/or formats each of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) into the corresponding current request groups QA.sub.1, . . . QA.sub.nc (50) having the corresponding queries QQ.sub.11 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54) to open connections with and make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of 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), shown for a particular one of the service and/or information requests IQ.sub.n (28) in FIG. 59. The process 104 of deriving the service and/or information response IR.sub.n (34) for the grouping and/or sorting criteria of FIG. 59 is shown in FIG. 71.

(606) The server PS (18) also parses, processes, and/or formats each of the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) into the corresponding request groups QA.sub.11 . . . QA.sub.nz (51) having the corresponding other queries QQ.sub.1a . . . QQ.sub.nz (55) and the corresponding other server addresses AQ.sub.1a . . . AQ.sub.nz (56), and the corresponding optional instructions VJ.sub.11 . . . VJ.sub.nk (52), also shown for a particular one of the service and/or information requests IQ.sub.n (28) in FIG. 59.

(607) Certain ones of the clients C.sub.1 . . . C.sub.n (16) may alternatively and/or additionally make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of 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), and formulate the corresponding user service and/or information response ir.sub.1 . . . ir.sub.n (36), as previously described, as shown in FIG. 63. The process 104 of deriving the user service and/or information response ir.sub.n (36) for the grouping and/or sorting criteria of FIG. 59 is shown in FIG. 71.

(608) Upon receipt of the user service and/or information requests iq.sub.1 . . . iq.sub.n (27) at the corresponding clients C.sub.1 . . . C.sub.n (16), certain ones of the corresponding clients C.sub.1 . . . C.sub.n (16) may parse, process, and/or format the corresponding user service and/or information requests iq.sub.1 . . . iq.sub.n (27) into the corresponding current request groups QA.sub.1, . . . QA.sub.nc (50) having the corresponding queries QQ.sub.11 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.11 . . . AQ.sub.nm (54) to open connections with and make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), shown for a particular one of the user service and/or information requests iq.sub.n (27) in FIG. 63. The corresponding clients C.sub.1 . . . C.sub.n (16) may also parse, process, and/or format the corresponding user service and/or information response ir.sub.1 . . . ir.sub.n (36) into the corresponding request groups QA.sub.11 . . . QA.sub.nz (51) having the corresponding other queries QQ.sub.1a . . . QQ.sub.nz (55) and the corresponding other server addresses AQ.sub.1n . . . AQ.sub.nz (56), and the corresponding optional instructions VJ.sub.11 . . . VJ.sub.nk (52), also shown for a particular one of the user service and/or information requests iq.sub.n (27) in FIG. 63.

(609) The server PS (18) makes the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of 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 FIG. 59, and certain ones of the clients C.sub.1 . . . C.sub.n (16) may additionally and/or alternatively make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of 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 FIG. 63.

(610) The Searches per Group 326 and the Group 327 are used to formulate the current request group QA.sub.nc (50) having the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) to open connections with and make the requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of the servers S.sub.1 . . . S.sub.z (20) to be communicated with corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) thereof as the server designations S.sub.11 . . . S.sub.nm (30), corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), for the service and/or information request IQ.sub.n (28) and/or the user service and/or information request iq.sub.1n (27).

(611) Information from the current request group QA.sub.nc (50) having the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) is formulated into the corresponding request pointer/address group QZ.sub.n (60) having the pointers/addresses PG.sub.n1 . . . PG.sub.nz (61) associated therewith, as shown in FIGS. 59 and 63.

(612) Each of the pointers/addresses PG.sub.n1 . . . PG.sub.nz (61) are directed to point/address the corresponding addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) associated therewith, which aid in obtaining services and/or information from the certain ones of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) to be incorporated into the query information groups GI.sub.n1 . . . GI.sub.nz (63).

(613) Ones of the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) may be associated with corresponding ones of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62).

(614) Each of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) associated with the service and/or information request IQ.sub.n has the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) directed to address/point services and/or information in the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57), based upon the grouping and/or sorting criteria.

(615) Information and/or services in the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is addressed with the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) from the query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), and information and/or services from the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) is incorporated into the addressable query information groups GI.sub.n1 . . . GI.sub.nz (63) corresponding to the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64), which are formulated by the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), in accordance with the grouping and/or sorting criteria.

(616) FIGS. 59 and 63 show the request pointer/address group QZ.sub.n (60), the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64), associated ones of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57), and the query information group GI.sub.nz (63) associated with the query pointer/address group QG.sub.nz (62). FIGS. 59 and 63 show the rth pointers/addresses PP.sub.n1r . . . PP.sub.nmr (64), which point to the rth optional addressable pointer/address indices IN.sub.nmr . . . IN.sub.nmr (81) of the corresponding rth individual information groups LG.sub.n1, . . . LG.sub.nmr (80) of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) associated with the query pointer/address group QG.sub.nz (62) and the associated query information group GI.sub.nz (63).

(617) FIG. 97 shows the request pointer/address group QZ.sub.n (60), a particular one of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), designated as the query pointer/address group QG.sub.nz (62), the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64), associated ones of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57), and the query information group GI.sub.nz (63) associated with the query pointer/address group QG.sub.nz (62).

(618) The addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) each have corresponding ones of query information groups GI.sub.n1 . . . GI.sub.nz (63) associated therewith. Each of the query information groups GI.sub.n1 . . . GI.sub.nz (63) have information and/or services therein, which are derived from information and/or services obtained from the certain ones of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57), which are addressed to provide such information with the aid of the corresponding pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64). Each of the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) are directed to point/address information and/or services in the corresponding response information groups RG.sub.n1 . . . RG.sub.nm (57) associated therewith, which the information and/or services incorporated into the ones of the query information groups GI.sub.n1 . . . GI.sub.nz (63) associated with the corresponding addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) is obtained therefrom.

(619) The addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) may be used to aid in formulating the query information groups GI.sub.n1 . . . GI.sub.nz (63), having information obtained from the addressable response information groups RG.sub.nm (57), resulting from certain ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) grouped one with the other and/or the associated ones of the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54). The query information groups GI.sub.n1 . . . GI.sub.nm (63) may be presented to the user U.sub.n (12) through the user interface I.sub.n (14). The addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) may be derived from query criteria in the optional instructions VJ.sub.11 . . . VJ.sub.nk (52) and/or using default criteria resident within the server PS (18) and/or the client C.sub.n (16).

(620) Query grouping criteria giving the user U.sub.n (12) the ability to formulate the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) may be incorporated into the optional instructions VJ.sub.11 . . . VJ.sub.nk (52), which may be entered into the user interface I.sub.n (14) through the user input UI.sub.n (25) by the user U.sub.n (12). Typically, however, the queries QQ.sub.n1 . . . QQ.sub.nm (53) having the same and/or substantially the same values are grouped one with the other in individual ones of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62). Default criteria may be resident within the server PS (18) and/or the client C.sub.n (16).

(621) The size of the request pointer/address group QZ.sub.n (60) and which particular ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) to use in the requests Q.sub.n1 . . . Q.sub.nm (29), and thus construction and/or formulation of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) to incorporate into the particular request pointer/address group QZ.sub.n (60), and, thus, delivery of information in the query information groups GI.sub.n1 . . . GI.sub.nz (63) is determined by the current request groups QA.sub.1, . . . QA.sub.m (50), which may be determined from the Group 327 and the Searches per Group 326, the queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) therein.

(622) Certain ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) may be grouped one with the other in the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), which have the certain ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) and the corresponding ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) associated therewith, and the corresponding pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) associated with the certain ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53), the corresponding ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and certain ones of response information groups RG.sub.n1 . . . RG.sub.nm (57).

(623) Typical sorting and/or grouping criteria, for example, may group certain ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) having the same and/or substantially the same values grouped in a particular one of the query information groups GI.sub.nz . . . GI.sub.nz (63), designated as the query information group GI.sub.nz (63), as shown in FIG. 98 and in certain ones of FIGS. 27A-52C, inclusive.

(624) Alternatively and/or additionally, other typical sorting and/or grouping criteria, for example, may group certain ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), having the same and/or substantially the same values grouped in a particular one of the query information groups GI.sub.nz . . . GI.sub.nz (63), designated as the query information group GI.sub.nz (63), as shown in FIG. 99.

(625) FIGS. 97-99 show the rth pointers/addresses PP.sub.ner (64), PP.sub.nrr (64), and PP.sub.nwr (64), which point to the rth optional addressable pointer/address indices IN.sub.ner (81), IN.sub.nrr (81), and IN.sub.nwr (81) of the corresponding rth individual information groups LG.sub.nmr (80), LG.sub.nrr (80), and LG.sub.nwr (80) of the addressable response information groups RG.sub.ne (57), RG.sub.nr (57), and RG.sub.nw (57) associated with the query pointer/address group QG.sub.nz (62) and the associated query information group GI.sub.nz (63).

(626) Alternatively and/or additionally, the user U.sub.n (12) may select query grouping criteria, which simply provides information to the user interface I.sub.n (14), separately with respect to the individual server addresses AQ.sub.n1 . . . AQ.sub.nm (54), as shown in FIGS. 60 and 64 and in certain ones of FIGS. 27A-52C, inclusive. For example, the query information groups GI.sub.n1 . . . GI.sub.nz (63), may alternatively and/or additionally be correspondingly associated with the server address AQ.sub.n1 . . . AQ.sub.nm (54), and, thus, may be correspondingly associated with the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57). The query information group GI.sub.n1 (63) may, thus, be associated with the server address AQ.sub.n1 (54), the addressable response information group RG.sub.n1 (57), and the query information group GI.sub.n1 (63); the query information group GI.sub.n2 (63) may, thus, be associated with the server address AQ.sub.n2 (54), the addressable response information group RG.sub.n2 (57), and the query information group GI.sub.n2 (63), and so on; and the query information group GI.sub.nz (63) may, thus, be associated with the server address AQ.sub.nz (54), the addressable response information group RG.sub.n2 (57), and the query information group GI.sub.nz (63), as shown in FIGS. 60 and 64. The process 104 of deriving the service and/or information response IR.sub.n (34) and/or the user service and/or information response ir.sub.n (36) for the grouping and/or sorting criteria of FIGS. 60 and 64 is shown in FIG. 72.

(627) The pointing/addressing scheme of FIGS. 60 and 64 is, of course, a much simpler pointing/addressing scheme than the pointing/addressing scheme of FIGS. 59 and 63, and does not require incorporating the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) into the request pointer/address group QZ.sub.n (60). Each of the pointers/addresses PF.sub.n11 . . . PF.sub.nmr (69), of FIGS. 60 and 64, may then be directed to point/address the corresponding response information groups RG.sub.n1 . . . RG.sub.nm (57) directly from the request pointer/address group QY.sub.ns (68), to obtain information from the corresponding response information groups RG.sub.n1 . . . RG.sub.nm (57) and incorporation into corresponding ones of the corresponding query information groups GI.sub.n1 . . . GI.sub.nz (63), as shown in FIGS. 60 and 64. In this case, the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) may be bypassed and/or eliminated completely, thus simplifying the process. Of course, then, in this case, the resulting sorting and grouping is not as sophisticated, and allows for such simplification.

(628) The above sorting criteria addressing schemes are meant only as typical examples of sorting criteria addressing schemes that may be used. Yet other sorting criteria addressing schemes and/or combinations thereof may be used.

(629) FIG. 100 shows typical ones of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) having the typical ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53), the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the corresponding ones of typical ones of the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) having the same ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) grouped one with the other in individual ones of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62).

(630) More particularly, FIG. 100 shows the query pointer/address group QG.sub.n1 (62), the query pointer/address group QG.sub.n2 (62), and the query pointer/address group QG.sub.n3 (62). The query pointer/address group QG.sub.n1 (62) of FIG. 100 has the same ones of the queries QQ.sub.n1 (53), QQ.sub.n2 (53), QQ.sub.n3 (53), and QQ.sub.n9 (53), the ones of the server addresses AQ.sub.n1 (54), AQ.sub.n2 (54), AQ.sub.n3 (54), and AQ.sub.n9 (54), and the ones of the pointers/addresses PP.sub.n1r (64), PP.sub.n2r (64), PP.sub.n3r (64), and PP.sub.n9r (64) associated therewith. The query pointer/address group QG.sub.n2 (62) of FIG. 100 has the same ones of the queries QQ.sub.n4 (53) and QQ.sub.n7 (53), the ones of the server addresses AQ.sub.n4 (54) and AQ.sub.n7 (54) the ones of the pointer/addresses PP.sub.n4r (64) and PP.sub.n1r (64) associated therewith. The query pointer/address group QG.sub.n3 (62) of FIG. 100 has the same ones of the query values QQ.sub.n5 (53), QQ.sub.n6 (53), and QQ.sub.n8 (53), the ones of the server addresses AQ.sub.n5 (54), AQ.sub.n6 (54), and AQ.sub.n8 (54) and the ones of the pointers/addresses PP.sub.n5r (64), PP.sub.n6r (64), and PP.sub.n8r (64) associated therewith.

(631) The addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62), however, may alternatively and/or additionally be grouped, for example, by the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) and have the corresponding query values QQ.sub.n1 . . . QQ.sub.nm (53) associated therewith. Ones of the same and/or substantially the same ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), for example, having the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) associated therewith may be used as the grouping criteria.

(632) FIG. 101 shows another schematic representation of the typical ones of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) having the typical ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53), the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical the ones of the pointer/addresses PP.sub.n11 . . . PP.sub.nmr (64) of FIG. 100 associated therewith.

(633) FIG. 102 is a generic schematic representation of the addressable query pointer/address groups QG.sub.n1 . . . QG.sub.nz (62) having the queries QQ.sub.n1 . . . QQ.sub.nm (53), the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the pointers/addresses PP.sub.n11 . . . PP.sub.nmr (64) associated therewith.

(634) Certain information in the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) may be associated with the corresponding queries QQ.sub.n1 . . . QQ.sub.nm (53) and/or the corresponding server addresses AQ.sub.n1 . . . AQ.sub.nm (54) within the current request group QA.sub.nc (50), and may optionally be used by the server PS (18) and/or the client C.sub.n (16).

(635) Certain information in the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) may also be incorporated into the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52). Such information may be incorporated into the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) and/or may also be additionally and/or alternatively optionally resident within the server PS (18) and/or the client C.sub.n (16).

(636) J. Communicating the Requests to the Servers

(637) The server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) contact and open the connections OC.sub.11 . . . OC.sub.nm (323) with ones of the servers S.sub.1 . . . S.sub.z (20), according to the server designations S.sub.11 . . . S.sub.nm (30) at the corresponding server addresses A.sub.11 . . . A.sub.nu (265) at corresponding ports W.sub.11 . . . W.sub.nm (343). The server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) communicate the requests Q.sub.11 . . . Q.sub.nm (29) of one or more of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20), designated within the Group 327 and the Searches per Group 326 to make the requests Q.sub.11 . . . Q.sub.nc (29) thereof, in accordance with the designation scheme corresponding to the corresponding ones of the server designations S.sub.11 . . . S.sub.nm (30), corresponding to the requests Q.sub.11 . . . Q.sub.nm (29). If the Group 327 is not specified and/or the Searches per Group 326 are not specified by the users U.sub.1 . . . U.sub.n (12), default values may additionally and/or alternatively values be used.

(638) A particular one of the requests Q.sub.11 . . . Q.sub.nm (29), hereinafter designated as the request Q.sub.nm (29), corresponding to one request within the requests Q.sub.n1 . . . Q.sub.nm (29) corresponding to the user U.sub.n (12), is shown schematically in FIG. 103.

(639) Information 344 that may be used for formulating a typical particular one of the requests Q.sub.nm (29) from the service and/or information request IQ.sub.n (28), and parsing, processing, and/or formatting the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and opening the connection OC.sub.nm (323) is shown in FIGS. 92-95.

(640) Now, in more detail, the request Q.sub.nm (29) may have a corresponding request line L.sub.nm (345), corresponding optional request header fields JH.sub.n1 . . . JH.sub.ns (346), and a corresponding optional entity body EH.sub.nm (347). The request line L.sub.nm (345) may have a corresponding method M.sub.nm (348), a corresponding target resource P.sub.nm (349), which may have information associated with the corresponding query QQ.sub.nm (53), and corresponding protocol B.sub.nm (350).

(641) The user U.sub.n (12), the server PS (18) and/or the client C.sub.n (16) may optionally specify the port W.sub.nm (343) to communicate the request Q.sub.nm (29) therethrough, and/or the method M.sub.nm (348), and/or the protocol B.sub.nm (350). The port W.sub.nm (343), and/or the method M.sub.nm (348), and/or the protocol B.sub.nm (350) may optionally be resident within the server PS (18) and/or the client C.sub.n (16). Default values may also be used for the port W.sub.nm (343) and/or the protocol B.sub.nm (350).

(642) Typically, information within or from any and/or all or a portion of the queries QQ.sub.nm (53) may be incorporated into the corresponding ones of the target resources P.sub.11 . . . P.sub.nm (349) and/or the corresponding ones of the optional entity bodies EH.sub.11 . . . EH.sub.nm (347), and may in certain instances depend upon the method M.sub.11 . . . M.sub.nm (348).

(643) However, information that may be used for opening the connections OC.sub.11 . . . OC.sub.nm (323) and formulating the requests Q.sub.11 . . . Q.sub.nm (29) from the service and/or information requests IQ.sub.1 . . . IQ.sub.n (28) may be derived from any and/or all or a portion of the user client requests QC.sub.11 . . . QC.sub.nu (280) accessible to the users U.sub.1 . . . U.sub.n (12) and/or the hidden client requests HC.sub.n1 . . . HC.sub.nh (281) hidden from the users U.sub.1 . . . U.sub.n (12), and/or a combination thereof, and/or may also have information and/or instructions to be utilized by the server PS (18) and/or ones of the clients C.sub.1 . . . C.sub.n (16).

(644) Alternatively information from the alternate request links QL.sub.11 . . . QL.sub.na (203), and/or the server request links UL.sub.11 . . . UL.sub.ns (204), and/or the additional request links SL.sub.11 . . . SL.sub.nw (71), and/or a combination thereof, may be used by the server PS (18) and/or ones of the clients C.sub.1 . . . C.sub.n (16) to formulate the requests Q.sub.11 . . . Q.sub.nm (29).

(645) There may be m different or same ones of the requests Q.sub.n1 . . . Q.sub.nm (29) from the client C.sub.n (16) at any time, and n×m different and/or same ones of the requests Q.sub.11 . . . Q.sub.nm (29) of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20) present on the network 24 at any time.

(646) The queries QQ.sub.n1 . . . QQ.sub.nm (53) may each be different, one from the other, or the same. The queries QS.sub.n1 . . . QS.sub.nu (288) accessible to the user U.sub.n (12) may each be different, one from the other, or the same. The hidden queries QH.sub.n1 . . . QH.sub.nh (290) may each be different, one from the other, or the same. The number of the queries QQ.sub.n1 . . . QQ.sub.nm (53) “m” may be substantially the sum of the queries QS.sub.n1 . . . QS.sub.nu (288) accessible to the user U.sub.n (12) and the hidden queries QH.sub.n1 . . . QH.sub.nh (290), i.e., m=u+h.

(647) There may be m different or same ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) from the client C.sub.n (16) at any time, and n×m different and/or same ones of the queries QQ.sub.n1 . . . QQ.sub.nm (53) corresponding to the requests Q.sub.11 . . . Q.sub.nm (29) of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20) present on the network 24 at any time.

(648) The server addresses AQ.sub.n1 . . . AQ.sub.nm (54) may each be different, one from the other, or the same. The server addresses A.sub.n1 . . . A.sub.nu (265) accessible to the user U.sub.n (12) may each be different, one from the other, or the same. The hidden server addresses AH.sub.n1 . . . AH.sub.nh (291) may each be different, one from the other, or the same. The number of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) “m” may be substantially the sum of the server addresses A.sub.n1 . . . A.sub.nu (265) accessible to the user U.sub.n (12) and the hidden server addresses AH.sub.n1 . . . AH.sub.nh (291), i.e., m=u+h.

(649) There may be m different or same ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) from the client C.sub.n (16) at any time, and n×m different and/or same ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) corresponding to the requests Q.sub.11 . . . Q.sub.nm (29) of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20) present on the network 24 at any time.

(650) The optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) may each be different, one from the other, or the same. The optional instructions V.sub.n1 . . . V.sub.nv (289) accessible to the user U.sub.n (12) may each be different, one from the other, or the same. The optional hidden instructions H.sub.n1 . . . H.sub.ni (292) may each be different, one from the other, or the same. The number of the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) “k” may be substantially the sum of the optional instructions V.sub.n1 . . . V.sub.nv (289) accessible to the user U.sub.n (12) and The optional hidden instructions H.sub.n1 . . . H.sub.ni (292), i.e., k=v+i.

(651) There may be m×k different or same ones of the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29) from the client C.sub.n (16) at any time, and n×m×k different and/or same ones of the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) corresponding to the requests Q.sub.11 . . . Q.sub.nm (29) of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20) present on the network 24 at any time.

(652) The requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20) may be made at the same and/or different times. One or more of the requests Q.sub.11 . . . Q.sub.nm (29) may be made of each of the servers S.sub.1 . . . S.sub.z (20) by the same/and or different ones of the clients C.sub.1 . . . C.sub.n (16) and/or the server PS (18) at the same and/or different times.

(653) The server PS (18) and/or the client C.sub.n (16) may make one or more of the requests Q.sub.n1 . . . Q.sub.nm (29) 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.n1 . . . S.sub.nm (30), in order to fulfill the services and/or information requirements of the user U.sub.n (12).

(654) K. Replies from the Servers

(655) Each of the servers S.sub.1 . . . S.sub.z (20) communicated therewith replies to the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), in accordance with the designation scheme which designates the servers S.sub.1 . . . S.sub.z (20) being 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), and communicates the 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).

(656) Now, ones of the servers S.sub.1 . . . S.sub.z (20) having been contacted by the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) and the connections OC.sub.11 . . . OC.sub.nm (323) opened therewith, corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), according to the server designations S.sub.11 . . . S.sub.nm (30) at the corresponding server addresses A.sub.11 . . . A.sub.nu (265) at the corresponding ports W.sub.11 . . . W.sub.nm (343) reply to the server PS (18) and/or the contacting clients C.sub.1 . . . C.sub.n (16) with the corresponding responses R.sub.11 . . . R.sub.nm (32).

(657) A particular one of the responses R.sub.n1 . . . R.sub.nm (32), hereinafter designated as the response R.sub.nm (32), corresponding to one response within the responses R.sub.n1 . . . R.sub.nm (32), the response R.sub.nm (32) corresponding to the request Q.sub.nm (29), and the responses R.sub.n1 . . . R.sub.nm (32) corresponding to the requests Q.sub.n1 . . . Q.sub.nm (29), is shown schematically in FIG. 104.

(658) Now, the response R.sub.nm (32) may have a corresponding response header line LR.sub.nm (351), corresponding optional response header fields JR.sub.n1 . . . JR.sub.nt (352), and a corresponding optional entity body RH.sub.nm (353). The optional entity body RH.sub.nm (353) typically has links, and/or descriptions, and/or other information. The request header line LR.sub.nm (351) may have a corresponding protocol BR.sub.nm (354), a corresponding status SR.sub.nm (355), and a corresponding status explanation SE.sub.nm (356).

(659) Ones of the connections may be closed after ones of the responses R.sub.11 . . . R.sub.nm (32) are communicated to the PS (18) and/or to the requesting corresponding ones of the clients C.sub.1 . . . C.sub.n (16).

(660) Again, the Timeout per Search Engine 329 is considered to be substantially the maximum time for the server PS (18) and/or the particular client C.sub.n (16) making the requests Q.sub.n1 . . . Q.sub.nm (29) to wait for each of the responses R.sub.n1 . . . R.sub.nm (32) from certain ones of the servers S.sub.1 . . . S.sub.z (20), in accordance with the designation scheme which designates the certain ones of 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).

(661) If certain ones of the servers S.sub.1 . . . S.sub.z (20) do not open connections OC.sub.11 . . . OC.sub.nm (323) with and/or communicate the responses R.sub.11 . . . R.sub.nm (32) to the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), and/or if certain other ones of the servers S.sub.1 . . . S.sub.z (20) do not communicate the responses R.sub.11 . . . R.sub.nm (32) to the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) once connections OC.sub.11 . . . OC.sub.nm (323) therewith may have been opened, corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), according to the server designations S.sub.11 . . . S.sub.nm (30), within the timeout set by the Timeout per Search Engine 329, the certain ones of requests Q.sub.n1 . . . Q.sub.nm (29) of such nonresponding ones of the servers S.sub.1 . . . S.sub.z (20) may then be cancelled by the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16). Information about such ones of the nonresponding ones of the servers S.sub.1 . . . S.sub.z (20) may then be communicated from the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) through the corresponding ones of the user interfaces I.sub.1 . . . I.sub.n (14) to the corresponding ones of the users U.sub.1 . . . U.sub.n (12), according to the server designations S.sub.11 . . . S.sub.nm (30) corresponding to the certain ones of requests Q.sub.n1 . . . Q.sub.nm (29) of such nonresponding ones of the servers S.sub.1 . . . S.sub.z (20).

(662) In certain instances, the server PS (18) and/or certain ones of the clients C.sub.1 . . . C.sub.n (16) may contact certain ones of the servers S.sub.1 . . . S.sub.z (20) and open the connections OC.sub.11 . . . OC.sub.nm (323) therewith, corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), according to the server designations S.sub.11 . . . S.sub.nm (30), one or more additional times, in order to satisfy the needs of the users U.sub.1 . . . U.sub.n (12), and/or certain requirements within the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), such as, for example, the URL's per Search Engine 330, and/or as a result of certain information communicated to the PS (18) and/or certain ones of the clients C.sub.1 . . . C.sub.n (16) within the responses R.sub.11 . . . R.sub.nm (32).

(663) If, for example, less links, and/or descriptions, and/or prices/values, and/or images are returned within certain ones of the responses R.sub.11 . . . R.sub.nm (32), which may be considered to be first ones of the responses R.sub.11 . . . R.sub.nm (32), than are requested by certain ones of the users U.sub.1 . . . U.sub.n (12) within certain ones of the URL's per Search Engine 330, the server PS (18) and/or certain ones of the clients C.sub.1 . . . C.sub.n (16) may contact certain ones of the servers S.sub.1 . . . S.sub.z (20), open the connections OC.sub.11 . . . OC.sub.nm (323) therewith, and make additional ones of the requests Q.sub.11 . . . Q.sub.nm (29), according to the server designations S.sub.11 . . . S.sub.nm (30), one or more additional times, in order to satisfy the needs of the users U.sub.1 . . . U.sub.n (12). The links, and/or the descriptions, and/or the images returned within and/or parsed from additional ones of the responses R.sub.11 . . . R.sub.nm (32) to the additional ones of the requests Q.sub.11 . . . Q.sub.nm (29) may then be appended to the corresponding ones of the links, and/or the corresponding ones of the descriptions, and/or the corresponding ones of the images returned within and parsed from the first ones of the responses R.sub.11 . . . R.sub.nm (32)

(664) The servers S.sub.1 . . . S.sub.z (20) communicate the responses R.sub.11 . . . R.sub.nm (32) to the requests Q.sub.11 . . . Q.sub.nm (29) to the server PS (18) and/or specific ones of the clients C.sub.1 . . . C.sub.n (16), in accordance with the designation scheme corresponding to the corresponding ones of the server designations S.sub.11 . . . S.sub.nm (30). Alternatively, and/or additionally, in certain instances, certain ones of the servers S.sub.1 . . . S.sub.z (20), corresponding to certain ones of the server designations S.sub.11 . . . S.sub.nm (30), may request additional information of the server PS (18) and/or specific ones of the clients C.sub.1 . . . C.sub.n (16), prior to communicating the responses R.sub.11 . . . R.sub.nm (32) to the requests Q.sub.11 . . . Q.sub.nm (29). Upon receiving such additional information from the server PS (18) and/or the specific ones of the clients C.sub.1 . . . C.sub.n (16), the certain ones of the servers S.sub.1 . . . S.sub.z (20), corresponding to the certain ones of the server designations S.sub.11 . . . S.sub.nm (30), may then communicate the responses R.sub.11 . . . R.sub.nm (32) to the requests Q.sub.11 . . . Q.sub.nm (29) to the server PS (18) and/or the specific ones of the clients C.sub.1 . . . C.sub.n (16).

(665) In such certain instances, in more detail, the server PS (18) and/or certain ones of the clients C.sub.1 . . . C.sub.n (16) may contact certain ones of the servers S.sub.1 . . . S.sub.z (20) and open the connections OC.sub.11 . . . OC.sub.nm (323) therewith, corresponding to the requests Q.sub.11 . . . Q.sub.nm (29), according to the server designations S.sub.11 . . . S.sub.nm (30), one or more additional times, as a result of certain information communicated to the PS (18) and/or certain ones of the clients C.sub.1 . . . C.sub.n (16) within the responses R.sub.11 . . . R.sub.nm (32), such as, for example, information obtained from and/or parsed from the responses R.sub.11 . . . R.sub.nm (32). This information is typically within certain ones of the response header fields JR.sub.11 . . . JR.sub.n1 (352), but may also be within the corresponding optional entity bodies RH.sub.11 . . . RH.sub.nm (353) and/or the corresponding response header lines LR.sub.11 . . . LR.sub.nm (351).

(666) Now, in such certain instances, the certain ones of the servers S.sub.1 . . . S.sub.z (20) request the information from the server PS (18) and/or certain ones of the clients C.sub.1 . . . C.sub.n (16), prior to communicating the responses R.sub.11 . . . R.sub.nm (32) to the server PS (18) and/or the certain ones of the clients C.sub.1 . . . C.sub.n (16). The server PS (18) and/or the certain ones of the clients C.sub.1 . . . C.sub.n (16) being requested such information may then respond to the requests for such information, by communicating the requested information to the ones of the requesting servers S.sub.1 . . . S.sub.z (20). Upon receipt of the requested information at the ones of the requesting servers S.sub.1 . . . S.sub.z (20), the requesting ones of the servers S.sub.1 . . . S.sub.z (20) reply to the server PS (18) and/or the certain ones of the clients C.sub.1 . . . C.sub.n (16) with the responses R.sub.11 . . . R.sub.nm (32). Such requests for information from the servers S.sub.1 . . . S.sub.z (20) may occur not at all, and/or one or more times.

(667) L. Parsing, Processing, Formatting, Sorting, Grouping, and Organizing Responses into Service and/or Information Responses

(668) A particular one of the optional entity bodies RH.sub.11 . . . RH.sub.nm (353), designated as the entity body RH.sub.nm (353), of a particular one of the responses R.sub.11 . . . R.sub.nm (32), designated as the response R.sub.nm (32), may have optional response individual information groups LS.sub.nm1 . . . LS.sub.nmr (360) and optional information LI.sub.nm (361), as shown in FIG. 105.

(669) Each of the optional response individual information groups LS.sub.nm1 . . . LS.sub.nmr (360) may have and/or be parsed into corresponding optional response links LK.sub.nm1 . . . LK.sub.nmr (362), and/or corresponding optional response descriptions DK.sub.nm1 . . . DK.sub.nmr (363), and/or corresponding optional response prices/values PK.sub.nm1 . . . PK.sub.nmr (364), and/or corresponding optional response images IK.sub.nm1 . . . IK.sub.nmr (365), as shown in FIG. 105.

(670) The optional response links LK.sub.nm1 . . . LK.sub.nmr (362), the corresponding optional response descriptions DK.sub.nm1 . . . DK.sub.nmr (363), the corresponding optional response prices/values PK.sub.nm1 . . . PK.sub.nmr (364), and the corresponding optional response images IK.sub.nm1 . . . IK.sub.nmr (365), corresponding to the optional response individual information groups LS.sub.nm1 . . . LS.sub.nmr (360) are typically associated correspondingly one with the other.

(671) The optional response link LK.sub.nm1 (362), the corresponding optional response description DK.sub.nm1 (363), the corresponding optional response price/value PK.sub.nm1 (364), and the corresponding optional response image IK.sub.nm1 (365), corresponding to the optional response individual information group LS.sub.nm1 (360) are typically associated correspondingly one with the other. The optional response link LK.sub.nm2 (362), the corresponding optional response description DK.sub.nm2 (363), the corresponding optional response price/value PK.sub.nm2 (364), and the corresponding optional response image IK.sub.nm2 (365), corresponding to the optional response individual information group LS.sub.nm2 (360) are typically associated correspondingly one with the other, and so on. The optional response link LK.sub.nmr (362), the corresponding optional response description DK.sub.nmr (363), the corresponding optional response price/value PK.sub.nmr (364), and the corresponding optional response image IK.sub.nmr (365), corresponding to the optional response individual information group LS.sub.nmr (360) are, thus, typically associated correspondingly one with the other.

(672) The optional information LI.sub.nm (361) may have additional links, and/or additional descriptions, and/or additional images, and/or prices/values, and/or other information, and/or services, and/or media, all and/or a portion of which may be used and/or discarded by the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16). The optional information LI.sub.nm (361) is typically filtered from the optional entity body RH.sub.nm (353) and discarded, and/or other unwanted information and/or media is also typically filtered from the response R.sub.nn (32), and/or the optional entity body RH.sub.nm (353), and discarded.

(673) The optional response individual information groups LS.sub.nm1 . . . LS.sub.nmr (360) are typically parsed and/or processed and/or formatted from the entity body RH.sub.nm (353) of the response R.sub.nm (32), and/or parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) of the addressable response information group RG.sub.nm (57), correspondingly associated with the response R.sub.nm (32), as shown in FIGS. 106 and 107.

(674) FIG. 106 shows the addressable response information group RG.sub.nm (57) having the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into the addressable response information group RG.sub.nm (57) from the optional entity body RH.sub.nm (353) of FIG. 105.

(675) FIG. 107 shows a particular one of the optional response individual information groups LS.sub.nm1 . . . LS.sub.nmr (360), designated as the optional response individual information group LS.sub.nmr (360), parsed, and/or processed, and/or formatted, and/or organized, and/or grouped into a particular one of the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80), designated as the addressable individual information group LG.sub.nmr (80).

(676) The addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) are typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other, as the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) are incorporated into the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) from the responses R.sub.n1 . . . R.sub.nm (32).

(677) Alternatively and/or additionally the addressable individual information groups LG.sub.nm1 . . . LG.sub.nmr (80) may be incorporated into the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) from the responses R.sub.n1 . . . R.sub.nm (32) in an as-is condition and/or in raw form.

(678) The optional response links LK.sub.nm1 . . . LK.sub.nmr (362) are typically parsed, and/or processed, and/or formatted into the corresponding optional links LD.sub.nm1 . . . LD.sub.nmr (82). The optional response descriptions DK.sub.nm1 . . . DK.sub.nmr (363) are typically parsed, and/or processed, and/or formatted into the optional descriptions DD.sub.nm1 . . . DD.sub.nmr (83). The optional response prices/values PK.sub.nm1 . . . PK.sub.nmr (364) are typically parsed, and/or processed, and/or formatted into the corresponding optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84). The optional response images IK.sub.nm1 . . . IK.sub.nmr (365) are typically parsed, and/or processed, and/or formatted into the corresponding optional images ID.sub.nm1 . . . ID.sub.nmr (85).

(679) Each of the optional links LD.sub.m1 . . . LD.sub.mr (82) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other. Alternatively and/or additionally the optional links LD.sub.nm1 . . . LD.sub.nmr (82) may be retained in an as-is condition and/or in raw form.

(680) Each of the optional descriptions DD.sub.nm1 . . . DD.sub.nmr (83) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other. Alternatively and/or additionally the optional links optional descriptions DD.sub.nm1 . . . DD.sub.nmr (83) may be retained in an as-is condition and/or in raw form.

(681) Each of the optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other.

(682) Alternatively and/or additionally the optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84) may be retained in an as-is condition and/or in raw form.

(683) Each of the optional images ID.sub.nm1 . . . ID.sub.nmr (85) are also typically parsed, and/or processed, and/or formatted for consistency of presentation and/or appearance one with the other. Alternatively and/or additionally the optional images ID.sub.nm1 . . . ID.sub.nmr (85) may be retained in an as-is condition and/or in raw form.

(684) The optional links LD.sub.nm1 . . . LD.sub.nmr (82), and/or the optional descriptions DD.sub.nm1 . . . DD.sub.nmr (83), and/or the optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84), and/or the optional images ID.sub.nm1 . . . ID.sub.nmr (85), correspondingly associated with the response R.sub.nm (32), may additionally and/or alternatively be parsed individually and/or separately, and incorporated into the addressable response information group RG.sub.nm (57) from the optional entity body RH.sub.nm (353), as shown in FIG. 108.

(685) The response header line LR.sub.nm (351) and/or the optional response header fields JR.sub.n1 . . . JR.sub.nt (352) may also have information, which the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16) may use.

(686) The optional information LI.sub.nm (361) and/or certain information and/or media within the response R.sub.nm (32), particularly within the optional entity body RH.sub.nm (353), may be optionally used by the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), and/or optionally incorporated into the addressable response information group RG.sub.nm (57).

(687) Each of the optional response individual information groups LS.sub.nm1 . . . LS.sub.nmr (360) from each of the responses R.sub.n1 . . . R.sub.nm (32) may be compared one with the other, and duplicate ones of the of the optional response individual information groups LS.sub.nm1 . . . LS.sub.nmr (360) may be discarded.

(688) Alternatively and/or additionally, each of the optional addressable individual information groups LG.sub.n11 . . . LG.sub.nmr (80) from each of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) may be compared one with the other, and duplicate ones of the optional addressable individual information groups LG.sub.n11 . . . LG.sub.nmr (80) may be discarded.

(689) Each of the optional response individual information groups LS.sub.11i . . . LS.sub.nmr (360) and/or portions thereof from the entity bodies RH.sub.11 . . . RH.sub.nm (353) of the responses R.sub.11 . . . R.sub.nm (32) may also be optionally compared one with the other, and duplicate ones of the of the optional response individual information groups LS.sub.11i . . . LS.sub.nmr (360) may be optionally discarded.

(690) Alternatively and/or additionally, each of the optional links LK.sub.n11 . . . LK.sub.nmr (362), and/or the optional descriptions DK.sub.n11 . . . DK.sub.nmr (363), and/or the optional prices/values PK.sub.nm1PK.sub.nmr (364), and/or the optional images IK.sub.n11 . . . IK.sub.nmr (365), from each of the responses R.sub.n1 . . . R.sub.nm (32) may be compared one with the other of like kind, and duplicate ones of the optional links LK.sub.n11 . . . LK.sub.nmr (362), and/or the optional descriptions DK.sub.n11 . . . DK.sub.nmr (363), and/or the optional prices/values PK.sub.nm1 . . . PK.sub.nmr (364), and/or the optional images IK.sub.n11 . . . IK.sub.nmr (365), and/or a combination thereof may be discarded.

(691) Alternatively and/or additionally, each of the optional links LD.sub.n11 . . . LD.sub.nmr (82), and/or the optional descriptions DD.sub.n11 . . . DD.sub.nmr (83), and/or the optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84), and/or the optional images ID.sub.n11 . . . ID.sub.nmr (85) from each of the addressable response information groups RG.sub.n1 . . . RG.sub.nm (57) may be compared one with the other of like kind, and duplicate ones of the optional links LD.sub.n11 . . . LD.sub.nmr (82), and/or the optional descriptions DD.sub.n11 . . . DD.sub.nmr (83), and/or the optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84), and/or the optional images ID.sub.n11 . . . ID.sub.nmr (85), and/or a combination thereof may be discarded.

(692) The optional links LK.sub.n11 . . . LK.sub.nmr (362) are typically compared one with the other, and duplicate ones of the corresponding optional links LK.sub.n11 . . . LK.sub.nmr (362), and/or the corresponding optional descriptions DK.sub.n11 . . . DK.sub.nmr (363), and/or the corresponding optional images IK.sub.n11 . . . IK.sub.nmr (365), and/or the corresponding optional prices/values PK.sub.nm1 . . . PK.sub.nmr (364) are discarded, leaving only one of any ones of the duplicate optional links LK.sub.n11 . . . LK.sub.nmr (362) and/or the corresponding optional descriptions DK.sub.n11 . . . DK.sub.nmr (363), and/or the corresponding optional images IK.sub.n11 . . . IK.sub.nmr (365), and/or the optional prices/values PK.sub.nm1 . . . PK.sub.nmr (364) remaining.

(693) The optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84) and/or the corresponding optional links LD.sub.n11 . . . LD.sub.nmr (82) and/or the corresponding optional descriptions DD.sub.n11 . . . DD.sub.nmr (83), and/or the corresponding optional images ID.sub.n11 . . . ID.sub.nmr (85) may be sorted with respect to the optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84), in accordance with sorting criteria in the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) and/or in accordance with default criteria resident within the server PS (18) and/or the client C.sub.n (16).

(694) The optional links LD.sub.n11 . . . LD.sub.nmr (82), and/or the corresponding optional descriptions DD.sub.n11 . . . DD.sub.nmr (83), and/or the corresponding optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84), and/or the corresponding optional images ID.sub.n11 . . . ID.sub.nmr (85) may be sorted, for example, in ascending order with respect to the optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84) having the lowest price therein being presented to the user U.sub.n (12) at the user interface I.sub.n (14) first and the highest price therein last.

(695) Alternatively and/or additionally, the optional links LD.sub.n11 . . . LD.sub.nmr (82), and/or the corresponding optional descriptions DD.sub.n11 . . . DD.sub.nmr (83), and/or the corresponding optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84), and/or the corresponding optional images ID.sub.n11 . . . ID.sub.nmr (85) may be sorted, for example, in ascending or descending alphabetical order with respect to the optional links LD.sub.nu . . . LD.sub.nmr (82) and/or the corresponding optional descriptions DD.sub.n11 . . . DD.sub.nmr (83) being presented to the user U.sub.n (12) at the user interface I.sub.n (14).

(696) Other sorting criteria may be used for the optional links LD.sub.nu . . . LD.sub.nmr (82), and/or the optional descriptions DD.sub.n11 . . . DD.sub.nmr (83), and/or the optional prices/values PD.sub.nm1 . . . PD.sub.nmr (84), and/or the optional images ID.sub.n11 . . . ID.sub.nmr (85), and may depend upon needs of the user U.sub.n (12). The sorting criteria may be determined by the user U.sub.n (12).

(697) Sorting criteria gives the user U.sub.n (12) the ability to formulate how information is presented to the user U.sub.n (12) at the user interface I.sub.n (14), and may be incorporated into the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), which may be entered into the user interface I.sub.n (14) through the user input UI.sub.n (25) by the user U.sub.n (12). The sorting criteria may additionally and/or alternatively be resident within the server PS (18) and/or the client C.sub.n (16).

(698) Now again, the labelled individual information group LL.sub.nzu (86) associated with the addressable query information group GI.sub.nz (63) has the optional group identifier GL.sub.nc (87), the optional query link identifier LN.sub.ncu (88), the optional resource location identifier SU.sub.nz (89), the optional server and/or query identifier SI.sub.nm (90), and/or the optional server link identifier LX.sub.nmr (91) appended to the addressable individual information group LG.sub.nmr (80), as shown in FIG. 68.

(699) FIGS. 109 and 110 show typical ones of the addressable query information group GI.sub.nz (63), based upon certain sorting and/or grouping criteria, having the labelled individual information groups LL.sub.nz1 . . . LL.sub.nzu (86), the optional database labelled individual information groups RL.sub.nz1 . . . RL.sub.nzx (92), the optional query description QT.sub.nz (93), the optional server descriptions and/or links ST.sub.nz1 . . . ST.sub.nzf (94), and the optional advertisements and/or links LT.sub.nz1 . . . LT.sub.nzt (95) incorporated into certain typical ones of the typical service and/or information response forms IS.sub.n (39) of FIGS. 27A-52C, inclusive.

(700) The client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), then, are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information from the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20), and/or the optional servers SO.sub.1 . . . SO.sub.p (22), and/or the clients C.sub.1 . . . C.sub.n (16), having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information into the user responses UR.sub.1 . . . UR.sub.n (37) for delivery to the user interfaces I.sub.1 . . . I.sub.n (14) and use by the users U.sub.1 . . . U.sub.n (12).

(701) The client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), then, are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information from the same and/or different ones of each of the optional response individual information groups LS.sub.111 . . . LS.sub.nmr (360), and/or the optional response links LK.sub.111 . . . LK.sub.nmr (362), and/or the optional response descriptions DK.sub.111 . . . DK.sub.nmr (363), and/or the optional response prices/values PK.sub.111 . . . PK.sub.nmr (364), and/or the optional response images IK.sub.nm1 . . . IK.sub.nmr (365) from the entity bodies RH.sub.11 . . . RH.sub.nm (353) of the responses R.sub.11 . . . R.sub.nm (32), having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information into the user responses UR.sub.1 . . . UR.sub.n (37) for delivery to the user interfaces I.sub.1 . . . I.sub.n (14) and use by the users U.sub.1 . . . U.sub.n (12).

(702) M. Additional Features and/or Other Considerations

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

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

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

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

(707) 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.

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

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

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

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

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

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

(714) 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.

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

(716) 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.

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

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

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

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

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

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

(723) The client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, the server PS (18) and/or the clients C.sub.1 . . . C.sub.n (16), then, are capable of retrieving, parsing, processing, formatting, organizing, grouping, sorting, and consolidating services and/or information from the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20), and/or the optional servers SO.sub.1 . . . SO.sub.p (22), and/or the clients C.sub.1 . . . C.sub.n (16), having the same and/or different structures, formats, organizations, groupings, and/or data structures, and incorporating the parsed, processed, formatted, organized, grouped, sorted, and consolidated services and/or information into the user responses UR.sub.1 . . . UR.sub.n (37) for delivery to the user interfaces I.sub.1 . . . I.sub.n (14) and use by the users U.sub.1 . . . U.sub.n (12).

(724) The client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process, the user interfaces I.sub.1 . . . I.sub.n (14), and/or the clients C.sub.1 . . . C.sub.n (16), and/or the server PS (18), and/or the servers S.sub.1 . . . S.sub.z (20), and/or the optional servers SO.sub.1 . . . SO.sub.p (22) may be constructed of hardware, firmware, software, machines, and/or operating systems, and/or combinations thereof, and/or other suitable means, and/or other components and/or systems, and/or combinations thereof. Such hardware, firmware, software, machines, and/or operating systems, and/or combinations thereof, other components and/or systems, and/or other suitable means, and/or combinations thereof may have therein and/or be resident therein, but are not limited to computer components and/or systems, television and/or telecommunications components and/or systems, merger of television and computer systems, and/or merger of television and/or computer and/or telecommunications systems, networks, simulators, interactive technologies and/or systems, cybernetics and/or cybernetic systems, and/or combinations thereof.

(725) The clients C.sub.1 . . . C.sub.n (16), the server PS (18), the servers S.sub.1 . . . S.sub.z (20), and/or the optional servers SO.sub.1 . . . SO.sub.p (22) may be search engines, and/or sites, and/or servers, and/or clients, and/or URL's, and/or databases, and/or locations on the network, and/or other suitable components and/or systems, and/or other suitable means, and/or combinations thereof, which may be capable of communicating on the network 24. The scope of the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, however, is not limited to search engines, and/or sites, and/or servers, and/or clients, and/or URL's, and/or databases, and/or locations on the network, and/or other suitable components and/or systems, and/or other suitable means, and/or combinations thereof, which may be capable of communicating on the network 24, as it is recognized that other components, systems, technologies, and/or operating systems exist and/or emerge that may make use of the benefits of the present invention, and are either on the horizon and/or are recognized to be forthcoming.

(726) The client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process, the user interfaces I.sub.1 . . . I.sub.n (14), and/or the clients C.sub.1 . . . C.sub.n (16), and/or the server PS (18), and/or the servers S.sub.1 . . . 5, (20), and/or the optional servers SO.sub.1 . . . SO.sub.p (22), may then be hardware, firmware, software, and/or machines, and/or operating systems, and/or other suitable means, and/or combinations thereof, and may have and/or be resident within general purpose computers, special purpose computers, televisions, computer-television combinations, telecommunications systems, networks, mergers of computer and/or television technology and/or telecommunications technology and/or network technology, media, film, entertainment, interactive technologies and/or systems, cybernetics and/or cybernetic systems and/or technology, components, and/or systems, and/or other suitable means, and/or combinations thereof, and may be integrated one with the other and/or with other components and/or systems of one another, and may each be substantially the same and/or different one from the other.

(727) The client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process, the user interfaces I.sub.1 . . . I.sub.n (14), and/or the clients C.sub.1 . . . C.sub.n (16), and/or the server PS (18), and/or the servers S.sub.1 . . . S.sub.z (20), and/or the optional servers SO.sub.1 . . . SO.sub.p (22) may each have the same and/or different hardware, firmware, software, and/or ones of operating systems, and/or other suitable means, and/or combinations thereof. The optional databases 41 and/or 42 may also be hardware, firmware, software, and/or machine based, and/or other suitable means, and/or combinations thereof, have the same and/or different ones of operating systems and/or combinations thereof, and may have memory components associated therewith.

(728) 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. Such networks may be Earth based, satellite based, and/or space based, and/or other suitable means, and/or combinations thereof.

(729) The scope of the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, however, is not limited to such components, systems, technologies, operating systems and/or networks, as other components, systems, technologies, and/or operating systems exist and/or emerge that may make use of the benefits of the present invention, and are either on the horizon and/or are recognized to be forthcoming.

(730) Determination as to whether the server PS (18) performs the multitasking process 104, and/or whether particular ones of the clients C.sub.1 . . . C.sub.n (16) perform the multitasking process 104, may optionally be made at the particular ones of the clients C.sub.1 . . . C.sub.n (16) and/or the server PS (18). Such determination may optionally be made by the users U.sub.1 . . . U.sub.n (12), and/or be based upon processing power, capabilities, and/or configurations of the particular ones of the clients C.sub.1 . . . C.sub.n (16), the server PS (18), and the network 24 considerations (traffic, load, and/or other considerations).

(731) The client-server multitasking search engine and/or database are capable of updating information and/or services stored therein by querying sites, servers, search engines, and/or databases containing information and/or services referenced in the client-server multitasking search engine and/or database.

(732) The client-server multitasking system and process are capable of use on a variety of networks, such as global area networks, and in particular, the internet, metropolitan area networks, wide area networks, and local area networks, and is capable of searching search engines and/or other sites substantially simultaneously and on-the-fly.

(733) 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.

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

(735) Now again, 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 in 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 into 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).

(736) Now again, The typical ones of the 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) shown in FIGS. 11-26 are typical examples of the 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), a much larger variety of which is possible. Typical queries QQ.sub.n1 . . . QQ.sub.nm (53), typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) in the typical ones of the 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) shown in FIGS. 11-26 are typical examples for illustrative purposes, and are not intended to limit the substantially infinite variety of the queries QQ.sub.n1 . . . QQ.sub.nm (53), the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) that may be entered into the service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38), to derive the 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). Likewise, names and/or links and/or other information are incorporated in the typical ones of the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230) shown in FIGS. 11-26 for illustrative purposes, and are not intended to limit the large variety of the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230) and the names and/or links and/or information that are possible, and that may be incorporated into the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230) at the user interfaces I.sub.1 . . . I.sub.n (14).

(737) Now again, the typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14) shown in FIG. 27A-52C, inclusive, are typical examples of the user responses UR.sub.1 . . . UR.sub.n (37), as typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), a much larger variety of which is possible. FIGS. 27A-52C, inclusive, illustrate typical examples of typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14) to the typical queries typical queries QQ.sub.n1 . . . QQ.sub.nm (53), the typical ones of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) having been entered into the typical ones of the 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) shown in FIGS. 11-26.

(738) The typical examples of the typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as typical service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14) are for illustrative purposes, and are not intended to limit the substantially infinite variety of the user responses UR.sub.1 . . . UR.sub.n (37), as the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), the queries QQ.sub.n1 . . . QQ.sub.nm (53), the server addresses AQ.sub.n1 . . . AQ.sub.nm (54), and the optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) that may be entered into the service and/or information entry request forms IE.sub.1 . . . IE.sub.n (38), to derive the to the completed service and/or information entry request forms IF.sub.1 . . . IF.sub.n (230), and which result in the user responses UR.sub.1 . . . UR.sub.n (37), as the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14). Likewise, names and/or links and/or other information are incorporated into the typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), shown in FIGS. 27A-52C, inclusive, for illustrative purposes, and are not intended to limit the large variety of the user responses UR.sub.1 . . . UR.sub.n (37), as the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), and the names and/or links and/or information that are possible, and that may be incorporated into the user responses UR.sub.1 . . . UR.sub.n (37), as the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14).

(739) The server addresses AQ.sub.n1 . . . AQ.sub.nm (54), such as WebCrawler®, Altavista®, Lycos®, Infoseek®, Excite®, Yahoo®, LookSmart®, HotBot®, Dejanews®, Amazon®, Borders®, BarnesandNoble®, Google®, and/or others that may have been used herein are for illustrative purposes, to illustrate typical ones 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, typical ones of the 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) shown in FIGS. 11-26, and/or typical ones of the user responses UR.sub.1 . . . UR.sub.n (37), as the service and/or information response forms IS.sub.1 . . . IS.sub.n (39) at the user interfaces I.sub.1 . . . I.sub.n (14), shown in FIGS. 27A-52C, inclusive, and other examples used herein, are used merely to illustrate typical examples of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) and results therefrom that may be possible. The examples shown in FIGS. 5A, 5B, and 6-10, 11-26, and FIGS. 27A-52C, inclusive, and other examples used herein, are examples of the substantially infinite variety of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) that may be used with the client-server multitasking system 10 of the present invention and the results that may be obtained therefrom. The typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54), such as WebCrawler®, Altavista®, Lycos®, Infoseek®, Excite®, Yahoo®, LookSmart®, HotBot®, Dejanews®, Amazon®, Borders®, BarnesandNoble®, Google®, and/or others that may have been used herein are for illustrative purposes only and are not intended to limit the scope of the client-server multitasking system 10 of the present invention.

(740) It should also be obvious that the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) used in the examples shown in FIGS. 5A, 5B, and 6-10, 11-26, and FIGS. 27A-52C, inclusive, and other examples used herein are for illustrative purposes and are merely typical examples of the substantially infinite variety of the queries QQ.sub.n1 . . . QQ.sub.nm (53) that may be used with the client-server multitasking system 10 of the present invention and the results that may be obtained therefrom, and are not intended to limit the substantially infinite variety of the queries QQ.sub.n1 . . . QQ.sub.nm (53) that may be used with the client-server multitasking system 10 of the present invention and the results that may be obtained therefrom. The typical queries QQ.sub.n1 . . . QQ.sub.nm (53) used in the examples shown in FIGS. 5A, 5B, and 6-10, 11-26, and FIGS. 27A-52C, inclusive, and other examples used herein are for illustrative purposes only and are not intended to limit the scope of the client-server multitasking system 10 of the present invention.

(741) The typical labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86), the typical optional links LD.sub.n1 . . . LD.sub.nmr (82), and/or the typical optional descriptions DD.sub.n1 . . . DD.sub.nmr (83), and/or the typical optional prices/values PD.sub.n1 . . . PD.sub.nmr (84), and/or the typical optional images ID.sub.nm1 . . . ID.sub.nmr (85), and/or advertisements and/or advertisement links, and/or URL's, and/or locations, and/or other items and/or objects shown in FIGS. 5A, 5B, and 6-10, 11-26, and FIGS. 27A-52C, inclusive, and other examples used herein are typical examples for illustrative purposes only and are not intended to limit the scope of the client-server multitasking system 10 of the present invention. A substantially infinite variety of the labelled individual information groups LL.sub.n11 . . . LL.sub.nzu (86), the optional links LD.sub.n1 . . . LD.sub.nmr (82), and/or the optional descriptions DD.sub.n1 . . . DD.sub.nmr (83), and/or the optional prices/values PD.sub.n1 . . . PD.sub.nmr (84), and/or the optional images ID.sub.nm1 . . . ID.sub.nmr (85), and/or advertisements and/or advertisement links, and/or URL's, and/or locations, and/or other items and/or objects may result from the substantially infinite varieties and combinations of the queries QQ.sub.n1 . . . QQ.sub.nm (53) and the substantially infinite varieties and combinations of the server addresses AQ.sub.n1 . . . AQ.sub.nm (54) of the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process.

(742) Likewise, the typical grouping/sorting criteria shown herein in the examples is for illustrative purposes only and is not intended to limit the scope of the client-server multitasking system 10 of the present invention. It is possible to sort the responses within the service and/or information response, such as, for example, by category, query, group, page, order of importance, ascending and/or descending order, alphabetically and/or numerically, or other characteristics, as determined by the requestor, and/or the user, and/or the client-server multitasking system, or to combine the responses within the service and/or information response, such as, for example, interleaving the responses one with the other, such as, for example, by order of relevance or other parameters. The responses then are capable of being grouped by search criteria, server, order of importance, or by numerical factors such as value, price, or other numerical quantifier. The responses may be presentable, for example, in ascending or descending order in interleaved format, such as top ones, twos, threes, and so on, or presentable separately to the requestor and/or the user. The order may be order of importance or relevance related, or, for example, numerically valued, such as price or stock market value. A substantially infinite variety of results may be generated from the substantially infinite variety of grouping/sorting criteria possible with the client-server multitasking system 10 of the present invention.

(743) A substantially infinite variety of URL's, links, locations, sites, servers, and/or clients, other items and/or objects may be used with the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, which in itself is a process. Examples of URL's, links, locations, sites, servers, and/or clients, other items and/or objects shown in FIGS. 5A, 5B, and 6-52C, inclusive, are typical examples of URL's, links, locations, sites, servers, and/or clients, other items and/or objects that may be of used with the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and the multitasking process 104, and are used herein for illustrative purposes only, and are not intended to limit the scope of the client-server multitasking system 10 of the present invention, the client-server multitasking process 99, and/or the multitasking process 104.

(744) A substantially infinite variety of advertisements and/or links may be used with the client-server multitasking system 10 of the present invention. The advertisements and/or links to such sites as Netscape® and/or “ABC News”®, Disney®, Discovery®, Warner®, ABC®, Universal®, CBS®, NBC®, “TV Guide”®, NYtimes®, ESPN®, WSjournal®, CNN®, and/or other sites used in the examples shown in FIGS. 5A, 5B, and 6-10, 11-26, and FIGS. 27A-52C, inclusive, and other examples used herein are for illustrative purposes only and are not intended to limit the scope of the client-server multitasking system 10 of the present invention.

(745) It should also be obvious that advertisements and/or links to such sites as Netscape® and/or “ABC News”®, and/or other sites that may be used herein are for illustrative purposes only and are not intended to limit the scope of the client-server multitasking system 10 of the present invention.

(746) Each of the typical service and/or information entry request forms 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, may also have news stories, which may be updated intermittently on a substantially routine basis.

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

N. Additional Applications, Features, Uses, Embodiments, and Versions

(748) Although the present invention has been described in considerable detail with reference to certain preferred versions thereof, other versions are possible. The present invention may be used in a variety of applications, which are not limited to those described herein.

(749) The client-server multitasking system 10 of the present invention comprises a metasearch engine, which is a search engine that sends user requests to several other search engines, servers, clients, and/or databases, and other suitable systems and/or devices, groups, sorts, and returns the results from each one.

(750) The client-server multitasking system 10, the client-server multitasking process 99, the multitasking process 104, the search system and/or process, and/or the metasearch system and/or processes of the present invention may be used in a variety of searching, metasearching, ordering, shopping, and purchasing applications, and may alternatively and/or hereinafter be referred to as the client-server multitasking system 10/metasearch system, the client-server multitasking process 99/metasearch process, and/or the multitasking process 104/metasearch process of the present invention.

(751) FIGS. 1 and 2 show the client-server multitasking system 10/metasearch system of the present invention, having the requestors U.sub.1 . . . U.sub.n (12), also called the users U.sub.1 . . . U.sub.n (12), the corresponding user interfaces I.sub.1 . . . I.sub.n (14), the corresponding clients C.sub.1 . . . C.sub.n (16), the server PS (18), the servers S.sub.1 . . . S.sub.z (20), and the optional servers SO.sub.1 . . . SO.sub.p (22), constructed in accordance with the present invention, which reside on the 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) through the corresponding user interfaces I.sub.1 . . . I.sub.n (14).

(752) The client-server multitasking system 10/metasearch system may be used to request, retrieve and organize information and/or data from multiple devices and/or multiple servers having multiple data streams, and group and/or sort the information and/or data in real-time and on-the-fly, according to information in the user's request.

(753) The client-server multitasking system 10/metasearch system of the present invention may be used to search or metasearch a single query or keyword phrase of a plurality of sites substantially simultaneously and/or place one or a plurality of orders/purchases for the same and/or different products or items substantially simultaneously.

(754) The client-server multitasking system 10/metasearch system of the present invention may be used to search or metasearch a plurality of queries or keyword phrases of a plurality of sites substantially simultaneously and/or place one or a plurality of orders/purchases for the same and/or different ones of products or items substantially simultaneously, and has a single point of purchase/sale option, to receive and process orders from the users, based upon selections from the returned grouped and sorted results. The client-server multitasking system 10/metasearch system may alternatively be instructed to place orders and/or purchases automatically or semi-automatically, without user intervention, based upon optional criteria.

(755) For each request from each user, the client-server multitasking system 10/metasearch system searches and/or requests information and/or services from multiple sites, search engines, servers, databases, and/or clients substantially simultaneously. Each user may place multiple orders with multiple suppliers substantially simultaneously. Search criteria may be established by the users, which may comprise multiple queries or keyword phrases and/or multiple site selection, and/or the search criteria, may be resident within the client-server multitasking system 10/metasearch system. The sites, search engines, servers, and/or clients may be to be queried or to have the keyword phrases to be sent to may be chosen or selected by the users. Alternatively, optional default search criteria and/or optional default sites, search engines, servers, and/or clients may be used.

(756) The client-server multitasking system 10/metasearch system processes multiple responses from the sites, search engines, servers, databases, and clients, and groups and sorts the results, all in real time and on-the-fly. Search criteria, grouping, sorting, and display criteria may be established by the users and/or may be internal to the client-server multitasking system 10/metasearch system. The client-server multitasking system 10/metasearch system returns the grouped and sorted results to the users.

(757) The client-server multitasking system 10/metasearch system processes the orders, places the orders with third parties, and provides confirmation to the users, all in real time and on-the-fly.

(758) The client-server multitasking system 10/metasearch system may have additional options, including spidering, advertisements, news by category, data storage, pay per click ads, automatic updating, automatic data refreshing, and other options and other options, may be used on any kind of network, and in particular the internet, and process multiple requests from multiple users substantially simultaneously.

(759) FIG. 148 shows a simplified version of the particular service and/or information request IQ.sub.n (28) being parsed, processed, and/or formatted into current request group QA.sub.nc (50), request groups QA.sub.n1 . . . QA.sub.nz (51), and optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and utilization of information therefrom to make the requests Q.sub.n1 . . . Q.sub.nm (29), obtain the responses R.sub.n1 . . . R.sub.nm (32), and incorporate information therefrom into the particular service and/or information response IR.sub.n (34). The current request group QA.sub.nc (50) may be any particular one the request groups QA.sub.n1 . . . QA.sub.nz (51).

(760) FIG. 149 show yet a more simplified version of the particular service and/or information request IQ.sub.n (28) being parsed, processed, and/or formatted into current request group QA.sub.nc (50), request groups QA.sub.n1 . . . QA.sub.nz (51), and optional instructions VJ.sub.n1 . . . VJ.sub.nk (52), and utilization of information therefrom to make the requests Q.sub.n1 . . . Q.sub.nm (29), obtain the responses R.sub.n1 . . . R.sub.nm (32), and incorporate information therefrom into the particular service and/or information response IR.sub.n (34). The current request group QA.sub.nc (50) may be any particular one the request groups QA.sub.n1 . . . QA.sub.nz (51), and is shown as the single request group QA.sub.nc (50), which may be selected by the user U.sub.n (12), which may alternatively be set to default to the single request group QA.sub.nc (50), and/or which may be resident in the server PS (18).

(761) The client-server multitasking system 10 of the present invention comprises a metasearch engine, which is a search engine that sends user requests to several other search engines, servers, clients, and/or databases, and other suitable systems and/or devices, groups, sorts, and returns the results from each one.

(762) In more detail, the client-server multitasking system 10/metasearch system of the present invention may be used to send user requests to and group, sort, and return results from each of the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22), which may comprise and/or be from the group consisting of: at least one server device, at least one server, at least one search engine, at least one metasearch engine, at least one database, at least one database server, at least one data server, at least one file server, at least one information source, at least one site, at least one website, at least one electronic communication network, at least one ECN, at least one ECN server device, at least one ECN server, at least one ECN database, at least one electronic trading system, at least one alternative trading system, at least one computer assisted trading system, at least one electronic exchange, at least one electronic stock exchange, at least one virtual exchange, at least one electronic market, at least one electronic stock market, at least one virtual market, at least one client device, at least one client, at least one process, at least one software process, at least one program, at least one software program, at least one application, at least one software application, at least one computer, at least one laptop computer, at least one personal digital assistant, at least one peer-to-peer device, at least one peer-to-peer application, at least one peer-to-peer software application, at least one communications device, at least one transceiver, at least one wireless sensor node, at least one mote, at least one wireless gateway node, at least one wireless computer, at least one wireless platform, at least one robot, at least one wireless robot, at least one mobile server, at least one mobile device, at least one cellular server, at least one cellular device, at least one cellular phone, at least one cell phone, at least one miniature computer, at least one nanoscale server, at least one nanoscale computer, at least one nanocomputer, at least one radio frequency identification device, at least one newsgroup server, at least one e-mail server, at least one e-mail client, at least one intranet system, at least one personal search engine, at least one mobile search engine, at least one directory, at least one open directory, at least one web server, at least one File Transfer Protocol (FTP) site, at least one FTP server device, at least one FTP server, at least one podcast, at least one feed, at least one feed aggregator, at least one feed reader, at least one web feed, at least one webcast, at least one XML feed, at least one newsfeed, at least one newsfeed server, at least one blog, at least one RSS feed (Really Simple Syndication feed, Rich Site Summary feed, and/or Resource Description Framework feed), at least one aggregator, at least one feed aggregator, at least one feed reader, at least one web application, at least one video blog, at least one advertiser feed, at least one advertiser server, at least one syndication server, at least one web syndication server, at least one data stream device, at least one multiple data stream device, at least one WiFi device, at least one network, at least one social network, at least one social network site, at least one social network service, at least one small world network, at least one small world network site, at least one community, at least one virtual community, at least one online community, at least one e-community, other suitable systems and/or devices, and any combination thereof.

(763) Each of the clients C.sub.1 . . . C.sub.n (16) of the present invention may comprise and/or be from the group consisting of: a client device, a client, a server device, a server, a process, a program, a software program, an application, a software application, a computer, a laptop computer, a computer terminal, a communications device, a transceiver, a personal digital assistant, a peer-to-peer device, a peer-to-peer application, a peer-to-peer software application, a wireless device, a wireless computer, a wireless server, a wireless platform, a wireless client device, a wireless client, a mobile server, a mobile device, a cellular server, a cellular device, a cellular phone, a cell phone, a miniature computer, a nanoscale server, a nanoscale computer, a nanocomputer, a search engine, a metasearch engine, a site, a website, a television, a television device, a display device, an input-output device, other suitable systems and/or devices, and any combination thereof.

(764) Substantially any item can be ordered and/or purchased, using the client-server multitasking system 10/metasearch system of the present invention, such as, for example, at least one item, at least one product, at least one security, at least one stock, at least one commodity, at least one currency, at least one financial product, at least one financial instrument, at least one bond, at least one arbitrage instrument, at least one transaction, at least one financial transaction, at least one asset, at least one derivative, at least one financial derivative, at least one future, at least one commodity future, at least one contract, at least one futures contract, at least one trade, at least one energy product, at least one holding, at least one financial holding, at least one fund, at least one market fund, at least one property, at least one financial property, at least one ticket, at least one airline ticket, at least one service, information, data, bid data, offer data, at least one quote, at least one bid quote, at least one offer quote, at least one share, music, audio, video, television, radio, at least one device, at least one apparatus, at least one method, at least one process, at least one file, at least one data file, at least one computer file, at least one music file, at least one video file, software, at least one application, at least one software application, at least one item for which at least one order can be placed, at least one item for which at least one order can be processed, at least one item that can be purchased, at least one item that can be shopped, other suitable items, and any combination of one or more thereof.

(765) i. Brief Summary of Typical Applications:

(766) A brief summary of some typical examples of applications, features, uses, systems, embodiments, processes, and/or versions are listed and/or described below, but the uses, applications, features, embodiments, systems, processes, and/or versions of the present invention are not limited to those summarized, listed and/or described below.

(767) Some features of the client-server multitasking system 10/metasearch system include: searching multiple keyword phrases of multiple information sources simultaneously, and grouping, and sorting results according to the keyword phrases; returning product and purchase information according to keyword phrases and/or purchasing multiple products simultaneously; making a single query or keyword search or multiple queries and/or multiple keyword searches of multiple sites, search engines, servers, databases, clients, information sources, applications, software applications, programs, and/or software programs substantially simultaneously, consolidating, grouping and/or sorting search results, and as a single point of purchasing and/or ordering one or more items; searching or metasearching a single query or a plurality of queries or keyword phrases of a plurality of sites, search engines, servers, databases, clients, information sources, applications, software applications, programs, and/or software programs substantially simultaneously and/or placing one or a plurality of orders/purchases for the same and/or different ones of products or items substantially simultaneously; querying and/or searching and/or spidering multiple sites, search engines, servers, databases, clients, information sources, applications, software applications, programs, and/or software programs substantially simultaneously and/or obtaining information and/or services from the multiple sites, search engines, servers, databases, clients, information sources, applications, software applications, programs, and/or software programs; for each request from each user, the client-server multitasking system 10/metasearch system searches, queries, and/or requests information and/or services from multiple sites, search engines, servers, databases, clients, information sources, applications, software applications, programs, and/or software programs substantially simultaneously; multiple requests from multiple users may be processed substantially simultaneously on substantially any kind of network, and in particular the internet; each user may place multiple orders with multiple suppliers substantially simultaneously; search criteria may be established by the users, which may comprise multiple queries or keyword phrases and/or multiple site selection, and/or the search criteria may be resident within the client-server multitasking system 10/metasearch system; the sites, search engines, servers, databases, clients, information sources, applications, software applications, programs, and/or software programs to be searched may have the queries, keyword phrases, search engines, servers, databases, and/or clients chosen or selected by the users; alternatively, optional default search criteria, display criteria, and/or optional default sites, search engines, servers, databases, clients, information sources, applications, software applications, programs, and/or software programs may be used, which may optionally be stored and/or resident within the client-server multitasking system 10/metasearch system; multiple responses from the multiple sites, search engines, servers, databases, clients, information sources, applications, software applications, programs, and/or software programs are processed, grouped, and/or sorted into results, substantially simultaneously, in real time and on-the-fly; search criteria, grouping, sorting, and display criteria may be established by the users and/or default values may be used and/or may be internal to or resident within the client-server multitasking system 10/metasearch system; the client-server multitasking system 10/metasearch system may be used to return the grouped and sorted results to the multiple users, substantially simultaneously, in real time and on-the-fly; the client-server multitasking system 10/metasearch system may have a single point of purchase/sale option, and receive and process orders from the users, based upon selections from the returned grouped and sorted results by the users and/or other criteria, and may alternatively be instructed to place orders and/or purchases automatically or semi-automatically, without user intervention, based upon optional criteria; orders may be processed and/or placed with third parties, and users are provided with confirmation, all in real time and on-the-fly; additional options include spidering, advertisements, news by category, data storage, pay per click ads, automatic updating, automatic data refreshing, and other options.

(768) Some applications of the client-server multitasking system 10/metasearch system include: (a) business, corporate, and industrial systems and applications; (b) business, government, and other types of security/intelligence gathering systems; (c) specialized search management systems; (d) scientific research, requiring multiple simultaneous data acquisition and analysis capabilities; (e) single point of purchase and single point of sale systems; (f) the financial services industry and managed futures markets; (g) commodities based systems and other systems having rapid, dynamically changing environments; (h) internet related systems; (i) the music and video industries; (j) homeland security and military applications; searching, grouping, sorting and/or identifying information and/or services, shopping, placing, and confirming orders for multiple products, financial instruments, stocks, commodities, music, audio, video, television, searching grouping, sorting, and/or identifying multiple data and/or data streams, information and/or services, and/or files from the multiple sites, search engines, servers, databases, clients, information sources, applications, software applications, programs, and/or software programs, substantially simultaneously; search results and/or shopping results may be grouped according to search query/keyword phrases and sorted in order selected by the user or optionally according to default settings, which may optionally be resident within the client-server multitasking system 10/metasearch system and/or the clients; grouped and/or sorted results may be supplemented by optional spreadsheet applications, spread sheet programs, and/or spreadsheet software; news, intelligence, and information gathering from multiple sources substantially simultaneously, consolidating, grouping, sorting, and organizing results by category and/or other criteria, using multiple queries/keyword phrases; searching, querying, purchasing, selling, and/or combination thereof in rapidly changing markets/environments and for arbitrage, such as for commodities, stocks, financial instruments, managed futures, and/or currency trading, and/or any combination thereof, and particularly in commodities based systems and other systems/markets having rapid, dynamically changing environments; parallel processing of multiple queries/keyword searches of multiple information sources of the same and/or different types and may be used on substantially any kind of network; quick response intelligence gathering of multiple same and/or different information requests of multiple sources, grouping and sorting results substantially simultaneously in real time and on-the-fly; combined search and E-Commerce, and/or as a single point of purchase/sale for multiple products in multiple categories from multiple sites, and is particularly useful for corporate, industrial, commercial, and government purchasing of multiple products from multiple sources, as well as internet purchasing of multiple products from multiple sources; performing research, using multiple information sources, multiple sites, search engines, servers, databases, clients, applications, software applications, programs, and/or software programs, and may be performed in parallel using multiple queries/keyword phrases in multiple categories and/or multiple fields substantially simultaneously, in real time, and on-the-fly; downloading multiple title/subject and/or music/audio/video/television substantially simultaneously; presenting results to single and/or multiple users substantially simultaneously in real time and on-the-fly; item/price comparisons, rapidly changing environments, real time trend analyses, the financial services industry, managed futures/arbitrage, business, commercial, and industrial systems/applications, news, business and substantially all types of intelligence gathering systems, and specialized search management systems, such as intellectual property/patent search management systems, libraries, library information retrieval systems, scientific research, and in areas such as bioinformatics, where multiple simultaneous data acquisition and analysis capabilities/data mining would greatly enhance and speed up diagnostics and/or benefit health based systems; point of purchase and point of sale for all types of corporate purchasing systems and/or on premises shopping mall enhancements; purchases may be made via on-line systems, networks, intranets, the internet, and/or on-site shopping for multiple product purchases from multiple stores/suppliers, for example, in a shopping mall and/or other venue; rapid response sale-purchasing system and/or a point of search, purchase and sale for multiple products of multiple vendors at the same and/or different sites with consolidation, grouping, sorting, and item/price comparisons, in dynamic rapidly changing environments; a single point of purchase system for multiple product purchasing systems from multiple sources for corporate, commercial, industrial, military, and logistics clients; a global one stop shopping/purchasing system, as it becomes a central point of sale/purchase, which can fulfill multiple simultaneous same and/or different orders, directed to multiple simultaneous same and/or different products, vendors/suppliers, and sites with a single command (including a single credit card entry) in multiple languages; buyers/consumers can, for example, search for product information and prices of vehicles, automobile windshields, tires, television sets, and shoes, and buy one or more vehicles, television sets, and pairs of shoes from multiple same and/or different vendors at the same time, with a single command. Homeland Security/quick response intelligence gathering/anti-terrorist applications/military applications, including multiple simultaneous data acquisition and analysis capabilities, such as multiple database queries of facial signatures, recognition, fingerprinting, signature analysis, and identification systems, and multiple battlefield tactical and strategic observation and analyses in real time; applications in the music, entertainment, video, television, videogame, game, and cable industries, internet sites, and/or peer-to-peer systems, devices, programs, and/or applications for acquisition of multiple music, video, game, audio, and/or television titles from multiple sources in multiple song, video, game, audio, and/or television categories, and for remarketing to the public; retrieval and organization of information and/or data from multiple devices and/or multiple servers having multiple data streams, and grouping and/or sorting of the information and/or data in real-time and on-the-fly; information and/or data may be grouped and/or sorted, according to information in the user's request and/or data stream identifiers and/or other resident in the client-server multitasking system 10; obtaining information and/or services from a plurality of social networks and/or small world networks, organizing, grouping, and/or sorting the results and/or connecting the plurality of social networks and/or small world networks together; obtaining information and/or services from the plurality of social networks and/or obtaining information and/or services from other sources, and organizing, grouping, and/or sorting the results from the social networks and/or the small world networks and/or the other sources substantially simultaneously; data mining, determining and/or gathering information about the attributes of nodes and/or the attributes of links or ties and/or information about the objects of one or more social networks substantially simultaneously, and determining and/or gathering information about the interdependencies and/or interrelationships within one or more social networks and/or between one or more social networks; searching one or more social networks substantially simultaneously, the responses therefrom being parsed, processed, formatted, grouped, sorted, and/or organized into groups according to selected attributes, objects, links, and/or ties, and/or other suitable criteria, and returned to the corresponding client, in accordance with the present invention; performing multiple keyword queries/searches of multiple servers and/or devices substantially simultaneously, in accordance with a client request (single and/or multiple keyword purchasing searches of multiple servers/devices may optionally be included); grouping and/or sorting search results/device responses and/or shopping results into return groups and/or display lists substantially simultaneously, according to keyword phrase and order selected by client (e.g. alphanumerically) (single and multiple keyword advertising options may be included); grouping and/or sorting search results/device responses and/or results into return groups, order books, and/or display lists substantially simultaneously, according to keyword phrase, bid data, offer data, and order selected by client; executing device responses/search results by a single action substantially simultaneously; executing single and/or multiple orders substantially simultaneously by a single action; providing manual and/or timed updates, allowing for continuous updating of information provided to the requestor and/or the user; the sampling rate or frequency of the timed updates may be adjusted by the user to range from less than one millisecond to milliseconds to seconds to hours to days or longer periods, or other suitable intervals, and may set to be automatic or semi-automatic timed updates, or a reminder may be set for the user to request manual timed updates.

(769) A more detailed discussion of some typical examples of applications, features, uses, systems, embodiments, processes, and/or versions are listed and/or described below, but the uses, applications, features, embodiments, systems, processes, and/or versions of the present invention are not limited to those summarized, listed and/or described below.

(770) ii. Detailed Discussion:

(771) The present invention allows users to manage, communicate with, request, and obtain information and/or services from multiple sites, servers, and/or sources on virtually any kind of network or interconnected networks, in parallel, in real time, and on-the fly. The client-server multitasking/metasearch technology performs multiple simultaneous requests, retrieves, collects, formats, organizes, groups, and sorts results from the same and/or different sites, clients and/or servers on virtually any kind of network, substantially simultaneously, in real time, and on-the-fly.

(772) The client-server multitasking/metasearch technology may be used in financial markets, business-to-business systems, business intelligence, news, data mining, search and database management systems, scientific research, global e-commerce, government and business intelligence and security, research, analysis, on a global, macro, and micro scale, large and small business applications, single point of purchase and sale of multiple products of multiple vendors at the same and/or different sites with grouping, sorting, rank, and item/price comparisons, in dynamic rapidly changing environments, and other applications.

(773) Applications include but are not limited to the Internet, Intranets, Global, Metropolitan, Wide, and Local Area Networks, multiple networks, network and multiple database management systems. The client-server multitasking/metasearch technology may be used in: (a) business, corporate, and industrial systems and applications; (b) business, news, portals, and security/intelligence gathering systems; (c) the financial services industry and managed futures/commodities markets; (d) government, homeland security, intelligence, military, and counter intelligence systems; (e) specialized search management systems, such as intellectual property/patent search management/pharmaceutical search systems; (f) scientific research, in areas such as bioinformatics, health, and DNA research, requiring multiple simultaneous data acquisition and analysis capabilities; (g) single point of purchase and single point of sale systems; (h) systems having rapid, dynamically changing environments; (i) internet related systems, news, and portals; and (j) the music and video industries.

(774) The client-server multitasking/metasearch system and process are capable of: parallel processing and management of the same and/or different information and/or services from a variety of sources. The client-server multitasking/metasearch system and process are capable of: making same and/or different requests of the same and/or different ones of servers; retrieving information and/or services from the servers; collecting and/or sorting, grouping, and/or organizing responses therefrom; and communicating service and/or information responses to requestors and/or users, all substantially simultaneously, in real time, and on-the-fly.

(775) Users, clients, and systems may make multiple requests of multiple servers, databases, systems, and services, simultaneously and in parallel, and manage, group, and sort responses, in real time and on-the-fly. The requests may be the same and/or different one from the other, and may be in any order, for the same and/or different types of information and/or services, the results being automatically managed, grouped and sorted, in accordance with characteristics dictated by the users, clients, and systems.

(776) The client-server multitasking/metasearch system is a quick response intelligence gathering, purchasing and sales system that makes multiple queries of multiple information sources substantially simultaneously, and optionally places buy and sell orders. A diverse crosscut of managed results are grouped and sorted in real-time and on-the-fly into a single graphical user interface.

(777) The client-server multitasking/metasearch system and process are capable of use on a variety of networks, such as global area networks, the internet, metropolitan area networks, wide area networks, and local area networks, and are capable of communicating with, requesting information and/or services therefrom, making requests of, querying, and searching multiple sites and types of sites, database management systems, search engines and/or other sites, in combination one with the other, retrieving responses therefrom, and collecting, and/or sorting, grouping and/or organizing responses therefrom, in parallel, all substantially simultaneously, in real time, and on-the-fly.

(778) Simple, easy to use, control panels and graphical user interfaces allow the requestors and/or users to manage and control information, make requests, and obtain results quickly and efficiently. The client-server multitasking/metasearch system and process are capable of collecting, sorting, grouping, and/or organizing results from the servers, database management systems, search engines, and/or sites, in accordance with instructions from the requestors, and/or users, and/or instructions resident within the client-server multitasking/metasearch system and/or process.

(779) The client-server multitasking/metasearch system and process are capable of use in a large variety of applications and industries, and are capable of information comparison and/or trend analysis of information from the same and/or different sources substantially simultaneously. The client-server multitasking/metasearch system is particularly useful in dynamically changing environments. The client-server multitasking/metasearch system and process are also optionally capable of creating, storing, building, and updating searchable databases from information retrieved, and searching the database alone or in combination with other systems and/or services.

(780) Parallel Processing of Multiple Data Streams

(781) The client-server multitasking/metasearch system and process of the present invention processes multiple data streams in parallel.

(782) The client-server multitasking/metasearch system and process: requests, retrieves, and organizes information and/or data from multiple devices and/or multiple servers having multiple data streams, groups, and sorts retrieved information and/or data in real-time and on-the-fly; (1) transforms a plurality of queries and broadcasts the group of queries to a group of similar or disparate devices, servers, databases, or web resources, with the appropriate syntax, (2) collects and merges the results, (3) presents the results in a succinct and unified format with minimal duplication, and (4) provides a means, performed either automatically or by a user, to sort the merged result set; parallel processes multiple requests/queries/keyword phrases, responses, and multiple data streams from multiple devices, servers, and systems, organizes and formats results, and presents results to users, including optional ordering/purchasing of single or multiple items simultaneously; may be software and/or hardware device oriented; network and/or non-network based;

(783) Business, Corporate, Health, and Industry Applications

(784) The present invention may be applied to a number of business sectors, requiring the management of multiple services, information, and data sources.

(785) The present invention may be directed to hardware/device based applications, software, network, and internet applications. Typical applications include: News, Business, Corporate Intelligence, Industry Applications; Keyword Product Searches and Order Processing; Commodities and Rapidly Changing Markets; Financial Markets; Scientific Research; Homeland Security/Intelligence Gathering; Audio and Video Applications; Search Engines and Search Engine Advertising; E-Commerce/Shopping; Broadband Applications; Cross Platform and Wireless Devices; Devices, Sensor Nodes, Motes, Mobile Servers, Cellular Servers, and Wireless Servers, Wireless Sensors, Wireless Sensor Networks; Social Networks; Processing, Spreadsheet, and Add-On Applications.

(786) The client-server multitasking/metasearch system and process act as a one-stop information, business intelligence, news, services, and data management system, performing multiple simultaneous queries of multiple simultaneous sites, databases and/or networks in parallel, specifically dedicated to particular industry and corporate needs. The use of the technology results in improved management of information, services, and data, increased efficiency, significant reduction of time, decreased manpower requirements, and substantial cost savings.

(787) News, business, and other types of intelligence may be gathered, grouped, sorted, and organized in multiple categories from multiple same and/or different sources and types of sources, simultaneously, in real time, on-the-fly, to supply corporate and industrial clients with the most recent up to date intelligence information in multiple specific fields of interest and in general, as well as internet based needs.

(788) Pharmaceutical industry searches may be made of the National Institute of Health, while simultaneously searching several public and/or private databases, rather than sequentially searching each database, separately. Multiple simultaneous patent database searching, and parallel rather than sequential searching will result in significant improvements in efficiency, time, and cost savings in the intellectual property field, DNA, genetics, disease, and health research fields.

(789) The present invention can perform as a one stop sales and purchasing system satisfying large corporate system needs. The client-server multitasking/metasearch system and process may be used to evaluate multiple supply sources by category, price, delivery dates, schedules, and other criteria simultaneously, and automatically make multiple purchases in different categories simultaneously. Large automobile manufacturers may license the technology as one stop purchasing systems and/or logistics management systems, as the supply chain is commodity based, having real time fluctuating prices and fluctuating availability of supply. Automobile manufacturers may obtain quotes on multiple products from multiple vendors, simultaneously, in real time and on-the-fly, required for the construction of one or more automobile models, sort and group the results by price and delivery schedule, and purchase the products, either automatically, semi automatically, or manually, in parallel, in real time, and on-the-fly.

(790) The present invention may also be used in small office management systems, and may be used by internet based companies seeking to broaden their businesses from typical internet portals and search sites. The client-server multitasking/metasearch system and process' single point of sale system, which has a built in order processing system may also be used to fulfill internet based needs, providing item price comparison shopping for multiple products from multiple suppliers, simultaneously.

(791) News, Business, Corporate Intelligence, Industry Applications

(792) News, business, business intelligence information, and data may be gathered, grouped, sorted, and organized in multiple categories from multiple same and/or different sources and types of sources, simultaneously, in real time, on-the-fly, to supply corporate and industrial clients with the most recent up to date intelligence information in multiple specific fields of interest and in general, as well as data management internet based needs, by performing multiple simultaneous queries of multiple sites, servers, databases and/or networks in parallel, dedicated to particular industries, trend analyses, and corporate needs.

(793) Facilitates research, using multiple information sources, multiple sites, search engines, servers, databases, clients, applications, software applications, programs, and/or software programs may be performed in parallel using multiple queries/keyword phrases in multiple categories and/or multiple fields substantially simultaneously, in real time, and on-the-fly.

(794) Data mining and/or determining and/or gathering information about the attributes of nodes and/or the attributes of links or ties and/or information about the objects of one or more social networks may be performed substantially simultaneously, using the present invention, and/or information about the interdependencies and/or interrelationships within one or more social networks and/or between one or more social networks, which may or may not be social in context may be determined and/or gathered, using the client-server multitasking/metasearch system and process of the present invention.

(795) Item/price comparisons, rapidly changing environments, real time trend analyses, the financial services industry, managed futures/arbitrage, business, commercial, and industrial systems/applications, news, business and substantially all types of intelligence gathering systems, and specialized search management systems, such as intellectual property/patent search management systems, libraries, library information retrieval systems, scientific research, and in areas such as bioinformatics, where multiple simultaneous data acquisition and analysis capabilities/data mining would greatly enhance and speed up diagnostics and/or benefit health based systems may be performed.

(796) A combined search and E-Commerce option may be used as a single point of purchase/sale for single or multiple products in multiple categories from multiple sites, which is particularly useful for corporate, industrial, commercial, and government purchasing of multiple products from multiple sources, as well as internet purchasing of single or multiple products from multiple sources.

(797) Commodities and Rapidly Changing Markets

(798) The client-server multitasking/metasearch system and process may be used in multiple rapidly changing dynamic markets and environments, to make multiple queries of multiple commodities and financial instruments in multiple markets, to place substantially simultaneous buy and sell orders in multiple markets, and to evaluate the effects of simultaneously changing multiple variables on desired results in real time, and commodities markets, sophisticated purchasing systems, on-line price comparisons and simultaneous ordering of multiple products from multiple suppliers.

(799) The client-server multitasking/metasearch system and process may be used in rapidly changing markets, such as airline ticket comparison shopping, commodities markets of all types, from financial commodities, to the purchase of oil, beef, and other commodities, the financial services industry, applications having real time multiple interactive information and/or service acquisition requirements, as well as multiple news, sports, weather, and other information feeds. The present invention may be used in multiple rapidly changing dynamic markets and environments, to make multiple queries of multiple commodities and financial instruments in multiple markets, to place substantially simultaneous buy and sell orders in multiple markets, and to evaluate the effects of simultaneously changing multiple variables on desired results in real time.

(800) The client-server multitasking/metasearch system and process is capable of providing manual and/or timed updates. Such timed updates allow for continuous updating of information provided to the requestor and/or the user. The sampling rate or frequency of the timed updates may be adjusted by the user to range from less than one millisecond to milliseconds to seconds to hours to days or longer periods, or other suitable intervals. The timed updates may be automatic or semi-automatic, or a reminder may be set for the user to request manual timed updates.

(801) Financial Markets

(802) The present invention has direct applications to financial markets, and more specifically, the managed futures, risk arbitrage and risk management businesses. Risk arbitrage is an attempt to profit by exploiting price differentials of identical or similar financial instruments, on different markets or in different forms, such as simultaneous comparison of several financial instruments in multiple markets, in addition to simultaneously comparing financial instruments in underlying markets, such as different options, strike prices and exchanges. The panacea would be multiple opposite transactions that take place simultaneously, generating profits with zero risk. Risk management is the ability to view financial exposure based upon queries of multiple data streams, and return information in user friendly formats. The system can also be used as a compliance monitor for clearing firms or other banking or financial institutions, where net capital computations are required on a real-time basis.

(803) Multiple simultaneous buy and sell transactions may be performed with the present invention, using, for example, multiple order books.

(804) The client-server multitasking/metasearch system and process may be used in and/or with electronic communication networks (ECNs), Alternative Trading Systems (ATS), and electronic trading systems to deliver substantially simultaneous multiple order books to traders and/or brokers for placement of multiple orders of multiple financial instruments, securities, and/or stocks simultaneously, and is especially useful in today's rapidly changing and dynamic market environments.

(805) The present invention may be used in managed futures, risk arbitrage and risk management businesses. Risk arbitrage is an attempt to profit by exploiting price differentials of identical or similar financial instruments, on different markets or in different forms, such as simultaneous comparison of several financial instruments in multiple markets, in addition to simultaneously comparing financial instruments in underlying markets, such as different options, strike prices and exchanges.

(806) Simultaneous comparison and purchasing of several financial instruments may be performed in multiple markets, in addition to simultaneously comparing financial instruments in underlying markets, such as different options, strike prices and exchanges.

(807) An “order book” may be used by stock exchanges and other exchanges for storing and matching various kinds of orders (such as limit orders and/or market orders) that can be placed on such exchanges, although other suitable order books may apply. The order book for the financial instrument being traded is typically displayed to a subscriber on a computer terminal, on which the subscriber may place an order.

(808) Scientific Research

(809) The client-server multitasking/metasearch system and process may be used for scientific research areas requiring multiple simultaneous data acquisition and analysis capabilities, such as bioinformatics, where parallel searching of multiple networks and databases will accelerate and provide results heretofore not possible.

(810) Unique to the client-server multitasking/metasearch system and process is the ability to have a user input the criteria for which the user desires results to be displayed, and prioritize the results by category in a variety of ways, within and external to groups, ascending/descending, price, numerical, alphabetical, and rank, etc.

(811) Applications may also include the user of user defined multiple database sources, which form a single data stream into a single user interface for simultaneously viewing multiple data sources.

(812) Pharmaceutical industry searches may be made, for example, of the National Institute of Health, while simultaneously searching several public and/or private databases, rather than sequentially searching each database, separately. Multiple simultaneous patent database searching, and parallel rather than sequential searching will result in significant improvements in efficiency, time, and cost savings in the intellectual property field, DNA, genetics, disease, and health research fields.

(813) Homeland Security/Intelligence Gathering

(814) The client-server multitasking/metasearch system and process may be applied to business and government security, intelligence gathering, and anti-terrorist applications areas requiring multiple simultaneous data acquisition and analysis capabilities, such as multiple database queries, using multiple keyword phrases, facial signatures, recognition, fingerprinting, signature analysis, and identification systems, where parallel searching of multiple networks and databases for multiple targets will accelerate and provide results heretofore not possible.

(815) The present invention may be applied to a number of security sectors, requiring the management of multiple services, information, and data sources, and, in particular, government, corporate and industry specific tools, requiring robust multiple client-server database management systems for both large and small business systems and applications.

(816) The client-server multitasking/metasearch system and process can act as a one-stop information, services, and data management system, performing multiple simultaneous queries of multiple simultaneous databases and/or networks in parallel, specifically dedicated to particular industry and corporate needs. The use of the technology results in improved management of information, services, and data, increased efficiency, significant reductions of time, decreased manpower requirements, and substantial cost savings.

(817) The technology may be directed to strategic and tactical security needs requiring a quick response from multiple sources substantially simultaneously and on the fly. Homeland Security and other classified/unclassified sites, such as NLETS, NCIC, FBI, Interpol, ATF, U.S. Marshall, and Homeland Security systems and databases (users must obtain all required security clearances) may be queried on a global scale, and results of multiple queries of multiple threats and suspects will be provided to users substantially simultaneously and on the fly. The latest continuously updated security news and alerts will also be provided to users. Typical operational applications include airports, borders, ports, public venues, and the battlefield requiring quick response intelligence information to be collected from multiple global sources, grouped, sorted, and provided to users in an easy to view and understand format for substantially simultaneous threat assessment.

(818) The present invention may be applied to Homeland Security/quick response intelligence gathering/anti-terrorist applications/military applications, including multiple simultaneous data acquisition and analysis capabilities, such as multiple database queries of facial signatures, recognition, fingerprinting, signature analysis, and identification systems, and multiple battlefield tactical and strategic observations and analyses in real time, and to multiple battlefield sensors, robots, and/or networks, including airborne, ground based, and/or sea based sensors and/or robots and/or networks.

(819) Audio and Video Applications

(820) The client-server multitasking/metasearch system and process may be used in the music, video, and entertainment industry and selected internet sites, for acquisition of multiple music and video titles from multiple sources in multiple song and video categories, and for remarketing to the public, as the next generation licensed napster.com and scour.com type audio and video systems. Different music and video titles, genres, and artists may be requested and purchased from multiple sources, for example, from the same and/or different sites, simultaneously and in parallel, affording users the ability to determine availability, pick and choose their best entertainment options, and order multiple items and types of items from multiple sources at the best prices, substantially simultaneously. The technology may also be used to provide continuously, automatically, updated network and internet event and programming guides, such as real time type TV, gaming, chat group, and entertainment guides, applied to different network events and programs. Downloads of multiple genre/title/subject and/or combinations thereof and music/audio/video/television and/or combinations may be performed substantially simultaneously.

(821) Search Engines

(822) The present invention is capable of multiple simultaneous same and/or different search queries, grouping, and sorting of results from the same and/or different search engines and/or sites, all at the same time, on-the-fly, whereas, other Internet search engines are only capable of single searches. The technology is capable of expanding the universe to an infinite number of simultaneous searches in multiple languages for domestic and international markets, and being indexed on other search engines. Virtually anyone using the Internet and other networks, especially those who regularly have a need to perform several tasks simultaneously, can use the client-server multitasking/metasearch system and process. For example, researchers can use the search capability to upgrade their searches by performing several searches in parallel, rather than, sequentially, and reduce research time.

(823) The client-server multitasking/metasearch system and process is particularly useful to address industries and entities with specialized data mining requirements. The user controls the topics, the sites the user searches, searches per group, url's per search, search time, data mining page and other characteristics. Users may control delivery of results, such as alternating interleaved results from each of the search engines and/or sites, shopping sites, i.e. top ones, twos, threes, etc., or separately and/or by category, grouping and sorting.

(824) Since the searching that is performed may be incorporated into web sites that are dynamic, there is no great need for expensive, massive storage capacity, and the information is always up to date. This differs radically from Internet portal search sites, such as Yahoo®, which are basically cataloguing systems, some of which go out and “spider” the web. It also differs from other metasearchers, which go out and return the first few results of a single search query of a few search engines. The client-server multitasking/metasearch system and process' unique graphical user interfaces facilitate and offer the user control in making multiple parallel searches of multiple sites, controlling, grouping, searching, and sorting the results in a user friendly manner. Default sites may also be used with the client-server multitasking/metasearch system and process.

(825) The technology is capable of simultaneously searching search engines, metasearchers, the Internet, and other networks in multiple languages; and can also store the resulting data and/or spider sites for creation of dedicated search engines and databases. The speed with which the client-server multitasking/metasearch system and process is able to process and return dynamic data makes the present invention an extremely important tool. In addition to unlimited multitasking and search capabilities, the client-server multitasking/metasearch system and process removes duplicates and returns clear concise results.

(826) The present invention allows simultaneous searching of search engines, consumer product rating services, and shopping sites, including order placement. Typical scenarios allow users to simultaneously search sites, such as search engines, product rating organizations, such as Consumer Reports®, and shopping sites for multiple products, obtain ratings and assessments, place orders, and receive order confirmation in real time.

(827) Advertising

(828) The client-server multitasking/metasearch system and process includes single and multiple keyword advertising options.

(829) Placement of Single or Multiple Orders with Multiple Servers/Third Parties

(830) The client-server multitasking/metasearch system and process may be used to place single or multiple orders with multiple servers and/or third parties substantially simultaneously. Single or multiple keyword queries/searches of multiple servers may be performed substantially simultaneously. Search results and/or single or multiple query shopping results are grouped and sorted into return groups (e.g. spreadsheet, tabular, or list format) substantially simultaneously, according to keyword phrase(s) and sorting order(s) (e.g. alphanumerically). Single or multiple orders may then be executed substantially simultaneously by a single action and/or multiple keyword search results reviewed, Multiple groups of multiple keyword requests may additionally be executed; including single or multiple keyword advertising. Users may perform combined single and/or simultaneous multiple product information searches and supplier searches and place single or multiple orders.

(831) Combined single and multiple keyword product searches, order processing, and single or multiple third party order placement with multiple servers and/or third parties may be performed substantially simultaneously and in parallel.

(832) The client-server multitasking/metasearch system and process may be used as a single or multiple product ordering system for processing one or more keyword purchasing query/search requests of multiple servers/third parties substantially simultaneously; grouping and sorting search results and/or shopping results into at least one return group (e.g. spreadsheet, tabular, or list format) substantially simultaneously, according to keyword phrase and sorting order (e.g. alphanumerically); multiple orders may then be executed simultaneously by a single action and/or keyword search results reviewed; keyword advertising may optionally be included.

(833) The present invention may be used to evaluate multiple supply sources by category, price, delivery dates, schedules, and other criteria simultaneously, and automatically makes multiple purchases in different categories simultaneously. Large automobile manufacturers, for example, may use or license the technology as one stop purchasing systems and/or logistics management systems, as the supply chain is commodity based, having real time fluctuating prices and fluctuating availability of supply. Automobile manufacturers may obtain quotes on multiple products from multiple vendors, simultaneously, in real time and on-the-fly, required for the construction of one or more automobile models, sort and group the results by price and delivery schedule, and purchase the products, either automatically, semi automatically, or manually, in parallel, in real time, and on-the-fly.

(834) Single and multiple product and multiple supplier item price comparisons may be performed, including order processing and placement, including price comparisons, product groupings and/or vendor groupings, price sorting within groupings, listings/spreadsheets, price and delivery comparisons of multiple products from multiple suppliers, and substantially simultaneous order processing, placement, and order confirmations.

(835) E-Commerce

(836) The client-server multitasking/metasearch system and process' single point of sale system, which has a built in order processing system, may be used to fulfill internet based needs, providing item price comparison shopping for multiple products from multiple suppliers, simultaneously. The present invention's global E-commerce system enables users to comparison shop on-the-fly, performing price comparisons, product grouping and/or vendor grouping, price sorting within groupings, and other comparisons of multiple simultaneous same and/or different shopping sites in the same and/or different merchandise categories, from the same and/or different vendors, in multiple languages.

(837) The technology also enables users to perform multiple product information searches and place multiple orders, simultaneously. A consumer can, thus, search, for example, consumer reports to obtain product information and place multiple product orders with multiple vendors of the user's choice, at the same time. The consumer can, for example, search for product information and prices of television sets and shoes, and buy a television set and a pair of shoes from different vendors at the same time. The system truly acts as a global one stop shop, as it becomes a central point of sale, which can fulfill multiple simultaneous same and/or different orders, directed to multiple simultaneous same and/or different products, and vendors/suppliers with a single command (including a single credit card entry) in multiple languages.

(838) Broadband Applications

(839) The client-server multitasking/metasearch system and process enable people and systems to manage resources, scan, find, and access needed information and services quickly, easily, and efficiently, especially as internet, media, and other technologies converge. The technology has the ability to correlate Internet and television programming with other programming and/or media, as it becomes available, and integrate the results. As broadband technology becomes more prevalent in homes and offices, worldwide networks, cable TV and a host of other venues, will expand broadcast programming on the Internet.

(840) The present invention is capable of searching available programming for a set of parameters and/or keywords, and simultaneously correlating the keywords with news stories. Financial institutions, for example, have a need to watch multiple sources of news, markets, and/or other sources of information, in order to become more profitable in their particular businesses. A user can, for example, enter the keyword “merger,” and/or other keywords, and if that word and/or words are used on a particular TV station and/or stations, and/or in an article or news story, the client-server multitasking/metasearch system and process can retrieve such sources of information and/or services substantially simultaneously, sort, and group, the information and/or services, and communicate the information and/or services to the user. A financial institution can, thus, for example, monitor many more sources and find opportunities that will increase its growth. The technology is also obviously beneficial for use in a variety of home and office applications.

(841) Cross Platform and Wireless Devices

(842) The present invention is applicable to multiple platforms, cross platforms, and wireless devices. The technology may be used across a number of platforms. The present invention may be used with virtually any kind of wireless system and/or platform, including wireless servers, wireless sensors, motes, wireless sensor networks (WSNs), wireless robotic servers and devices, mobile servers, Radio Frequency Identification (RFID) devices, mobile servers and devices, cellular servers and devices, sensor nodes, miniature, nanocomputers, and nansoscale servers and devices, wireless miniature devices, nanocomputers, and nansoscale servers and devices, and other wireless devices, and future wireless applications.

(843) The present invention may be used to request, retrieve and organize information and/or data from multiple wireless devices and/or multiple wireless servers having multiple data streams, and group and/or sort the information and/or data in real-time and on-the-fly, according to information in the user's request and/or data stream identifiers.

(844) The present invention may also be used across platforms, including systems and browsers for interactive technology, which combine broadcast, cable, satellite, Internet technology, internet television, WiFi, television applications, other future medium forms for distribution of Internet, network and/or computer-based content, Wireless Application Protocol (WAP) enabled devices, cellular telephones, wireless personal digital assistants (PDA's), other wireless devices, and other future wireless applications.

(845) The client-server multitasking/metasearch system and process of the present invention is applicable to multiple platforms, cross platforms, and wireless devices, and may be used across a number of platforms. The technology may be used with virtually any kind of platform convenient to users and their locations, custom web browsers for interactive technology, which combine broadcast, cable, satellite, Internet technology, internet television, WiFi, television applications, other future medium forms for distribution of Internet and/or computer-based content, wireless sensors, Radio Frequency Identification (RFID) devices, mobile servers and devices, Wireless sensor networks (WSNs), which may be used for environment sensing, tracking and/or control, and in battlefield systems, virtually any kind of wireless system and/or platform, including wireless servers, wireless sensors, motes, wireless sensor networks (WSNs), wireless robotic servers and devices, mobile servers, cellular servers and devices, sensor nodes, miniature, nanocomputers, and nansoscale servers and devices, wireless miniature devices, nanocomputers, and nansoscale servers and devices, and other wireless devices, Wireless Application Protocol (WAP) enabled devices, cell phones, wireless personal digital assistants (PDA's), and future wireless applications.

(846) Retrieval and organization of information and/or data from multiple devices and/or multiple servers having multiple data streams, and grouping and/or sorting of the information and/or data in real-time and on-the-fly; information and/or data may be grouped and/or sorted, according to information in the user's request and/or data stream identifiers and/or resident in the system.

(847) Additional Discussion on Financial Markets, Commodities and Rapidly Changing Markets

(848) A stock market is a market for trading securities, including company stock and derivatives, which are typically listed and traded on a stock exchange or stock exchanges. Stock exchanges provide real-time information on listed securities, and provide a marketplace (virtual or real), which facilitate the exchange of securities between buyers and sellers. Various stock exchanges bring buyers and sellers of securities, stocks, derivatives, and other financial instruments together for the purposes of trading. Derivatives may also be traded on a variety of other markets. Bonds are still traditionally traded in an informal, over the counter market, often referred to as the bond market. Commodities are traded on commodities markets. Other financial instruments may be traded on a variety of markets.

(849) The size of the ‘stock market’ is estimated to be approximately $51 trillion. The world derivatives market is estimated to be about $480 trillion, and the worldwide ‘bond market’ is estimated at $45 trillion.

(850) The stock market in the United States includes the trading of all securities listed on the New York Stock Exchange (NYSE)®, the American Stock Exchange (AMEX)®, National Association of Securities Dealers Automated Quotations system (NASDAQ)®, as well as on many regional exchanges, the Over The Counter Bulletin Board (OTCBB)®, and the Pink Sheets®, which is an electronic quotation system that displays quotes from broker dealers for many over-the-counter traded securities. European examples of stock exchanges include the Paris Bourse® (now part of, Euronext®, which is a pan-European stock exchange based in Paris, with subsidiaries in Belgium, France, the Netherlands, Portugal, and the United Kingdom), the London Stock Exchange (LSE)®, and the Deutche Borse®. It should be noted that the NYSE Group® merged with Euronext® in April, 2007 to form the first global equities exchange.

(851) Participants in the stock market range from small individual stock investors to large hedge fund traders, who can be based anywhere. Orders are usually executed by a professional at a stock exchange.

(852) Some exchanges have physical locations, where transactions are carried out on trading floors. Other types of exchange are virtual exchanges, composed of a network or networks of computers, where trades are made electronically via traders at computer terminals.

(853) Actual trades are based on an auction market paradigm, in which, for example, a potential buyer bids a specific price for a stock, and a potential seller asks a specific price for the stock. When the bid and ask prices match, a sale takes place on a first come first served basis, if there are multiple bidders or askers at a given price.

(854) The New York Stock Exchange® is a physical exchange, and is also a “listed” exchange, because only stocks listed with the exchange may be traded. Orders enter via brokerage firms that are members of the exchange and flow down to floor brokers, who go to specific locations, called trading posts, on the floor, where the stock or stocks trade. At each of the trading posts, there are specific individuals, known as specialists, who match buy and sell orders, using an auction method known as “open outcry,” in which traders may enter “verbal” bids and offers. The current bid price is the highest amount any buyer is willing to pay, and the current ask price is the lowest price at which someone is willing to sell. For a trade to take place, there must be a matching bid and ask price. If there is a spread, which is the difference between the price available for an immediate sale (bid) and an immediate purchase (ask/offer), no trade takes place, although the specialist is supposed to use his own resources of money or stock to close the difference, after some time. Once a trade takes place, details of the trade are reported on the “tape”, and sent back to the brokerage firm that placed the order. The brokerage firm then notifies the investor who placed the order that the trade has taken place and the price of the trade.

(855) The NASDAQ®, on the other hand, is a virtual (listed) exchange, where all trading is performed over a computer network, which is similar to trading on a physical exchange, in that the seller provides an asking price, and the buyer provides a bidding price. However, buyers and sellers are electronically matched. One or more NASDAQ® market makers always provides a bid and ask price at which they will always purchase or sell ‘their’ stock. The market maker is typically a firm that quotes both a buy and a sell price in a financial instrument or commodity, hoping to make a profit on a ‘turn’ or bid/offer spread.

(856) The Paris Bourse®, now part of Euronext® is an order-driven, electronic stock exchange, which was automated in the late 1980s, which prior to that time was an open outcry exchange in which stock brokers met on the trading floor. In 1986, however, the Paris Bourse® adopted a Computer Assisted Trading System (CATS) developed for the Toronto Stock Exchange® in 1977, and the order matching process was fully automated. Since that time, many exchanges have shifted to electronic trading.

(857) Computers and electronic trading have decreased or eliminated the need for physical trading floors, and the balance of power has shifted to electronic markets, with more and more electronic trading taking place. All of the above orders could be entered into an electronic market, although simple market and limit orders are generally encouraged by order priority rules. A market order is a buy or sell order to be executed by a broker immediately at current market prices, and as long as there are willing sellers and buyers, a market order will be filled. A limit order is an order to buy a security at no more (or sell at no less) than a specific price, which gives a customer some control over the price at which a trade is executed, but may prevent the order from being executed (“filled”).

(858) An electronic communication network (ECN), as understood and currently used in financial circles, is a type of computer system that facilitates trading of financial products outside of stock exchanges. The primary products that are traded on ECNs are stocks and currencies, although other suitable products and/or financial instruments may be traded on ECNs. For the most part, ECNs came into existence in 1998, when the Securities and Exchange Commission (SEC) authorized their creation. However, the first true ECN was the NASDAQ over-the-counter quotation system, created by the National Association of Securities Dealers (NASD)® in 1971.

(859) Electronic communication networks (ECNs) are commonly known as Alternative Trading Systems (ATS). The Securities and Exchange Commission has defined an ECN as any electronic system that widely disseminates to third parties orders entered into it by an exchange market maker or over-the-counter (“OTC”) market maker, and permits such orders to be executed in whole or in part.

(860) A 1969 American Stock Exchange (AMEX)® study estimated that errors in hand written securities order processing cost brokerage firms approximately $100 million per year. The NASDAQ system automated such order processing, and provided brokers with the latest competitive price quotes via a computer terminal, in order to overcome such problems. Later, more advanced ECNs were developed, as a result of regulatory changes, resulting from a 1994 United States Justice Department investigation of possible antitrust violations by NASDAQ® itself. NASDAQ® adopted new order handling rules that integrated ECNs into the NASDAQ® system, as part a settlement relating to the antitrust charges. The Securities and Exchange Commission (SEC) adopted Regulation ATS, after the settlement, which permitted ECNs the option to register as stock exchanges or else to be regulated under a separate set of standards for ECNs.

(861) Major ECNs that became active at that time were Instinet® and Island® (part of Instinet® was spun off and merged with Island® into NET®, and acquired by NASDAQ®), Archipelago Exchange®, and Brut® (now acquired by NASDAQ®). The Archipelago Exchange® is an entirely online securities exchange on which both stocks and options are traded, which was acquired by the New York Stock Exchange®, and which is currently owned by NYSE Euronext®, which merged with Archipelago Holdings® in a reverse merger in early 2006.

(862) For stock, ECNs exist as a class of Securities and Exchange Commission (SEC) permitted Alternative Trading Systems (ATS). ECNs are also used for currency trading. By trading through an ECN, a currency trader generally gets a better price than trading by voice over the phone. Other benefits are greater price transparency, faster processing, increased liquidity and more availability in the marketplace. Banks also lower their costs as there is less manual involvement.

(863) In order to trade with an ECN, one must be a subscriber to the ECN. ECN subscribers can enter orders into the ECN via a custom computer terminal or network protocols. The ECN then matches contra-side orders (i.e. a sell-order is “contra-side” to a buy-order with the same price and share count) for execution. The ECN posts unmatched orders on the system for other subscribers to view. Generally, buyers and sellers are anonymous, with the trade execution report listing the ECN as the party to the transaction

(864) ECNs increase competition among trading firms by lowering transaction costs, giving clients full access to their order books, and offering order matching outside of traditional exchange hours. The technology used for ECNs, Alternative Trading Systems (ATS), electronic trading systems, and the like is expected to spread to electronic markets and markets of all kinds and types. The present invention is intended to include all such electronic markets, electronic trading systems, markets, and the like.

(865) An “order book” refers to the system operated by many stock exchanges and other exchanges for storing and matching the various kinds of orders (such as limit orders and/or market orders) that can be placed on such exchanges. The order book for the financial instrument being traded is typically displayed to the subscriber on a computer terminal, on which the subscriber may place an order.

(866) The client-server multitasking system 10/metasearch system of the present invention may be used to request, retrieve and organize information and/or data from a plurality of ECNs, and group and/or sort the information and/or data in real-time and on-the-fly, according to information in the user's request and/or instructions resident in the client-server multitasking system 10/metasearch system. The client-server multitasking system 10/metasearch system may be used to group and/or sort information into a plurality of order books, each order book for a different financial instrument, security, and/or stock. Users may place orders for the financial instruments, securities, and/or stock.

(867) Again, FIGS. 1 and 2 show the client-server multitasking system 10/metasearch system of the present invention, having the requestors U.sub.1 . . . U.sub.n (12), also called the users U.sub.1 . . . U.sub.n (12), the corresponding user interfaces I.sub.1 . . . I.sub.n (14), the corresponding clients C.sub.1 . . . C.sub.n (16), the server PS (18), the servers S.sub.1 . . . S.sub.z (20), and the optional servers SO.sub.1 . . . SO.sub.p (22), constructed in accordance with the present invention, which reside on the 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) through the corresponding user interfaces I.sub.1 . . . I.sub.n (14).

(868) Again, the user U.sub.n (12) enters the corresponding user input UI.sub.n (25) having one or more of the same and/or different user requests qu.sub.11 . . . qu.sub.nu (26) into the corresponding user interface I.sub.n (14), as shown in FIG. 3. The user requests qu.sub.11 . . . qu.sub.nu (26) are communicated from the user interface I.sub.n (14) to the corresponding client C.sub.n (16) within the corresponding user service and/or information request iq.sub.n (27), having the user requests qu.sub.11 . . . qu.sub.nu (26) and other optional information. The user U.sub.n (12) may enter the corresponding user input UI.sub.n (25) at the same and/or different times.

(869) Now again, the user interface I.sub.n (14) communicates the user service and/or information request iq.sub.n (27) to the corresponding client C.sub.n (16), which optionally formats the corresponding user service and/or information request iq.sub.n (27) into the corresponding service and/or information request IQ.sub.n (28), as required. The service and/or information requests IQ.sub.n (28) has information therein that may be used to formulate 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), referred to by the 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.

(870) Again, in more detail, the client C.sub.n (16) formats the service and/or information response IR.sub.n (34) into the corresponding user service and/or information response ir.sub.n (36), as required, and communicates the user service and/or information responses ir.sub.n (36) to the corresponding user interface I.sub.n (14). The user interface I.sub.n (14) incorporates the user service and/or information responses ir.sub.n (36) into the corresponding user responses UR.sub.n (37), which is derived at the user interfaces I.sub.n (14), and communicated by the user interface I.sub.n (14) to the corresponding user U.sub.n (12) (See FIG. 2). The user U.sub.n (12) reviews the corresponding user response UR.sub.n (37) at the user interfaces I.sub.n (14) and/or selects additional services and/or information therefrom, such as, for example, placing an order for one or more securities.

(871) Now again, in more detail, the service and/or information responses IR.sub.n (34) has the parsed, processed, formatted, sorted, grouped, and/or organized service and/or information group G.sub.n (35) having the query information groups GI.sub.n1 . . . GI.sub.nz (63) therein, resulting from the same and/or different ones of the typical queries QQ.sub.n1 . . . QQ.sub.nm (53) having been sent to the same and/or different ones of the typical server addresses AQ.sub.n1 . . . AQ.sub.nm (54). Each of the query information groups GI.sub.n1 . . . GI.sub.nz (63) may have the services and/or information therein optionally parsed, processed, formatted, sorted, grouped, and/or organized according to sorting/grouping criteria specified in the typical optional instructions VJ.sub.n1 . . . VJ.sub.nk (52) by the user U.sub.n (12), and/or according default instructions and/or according to other information resident within the server PS (18).

(872) FIGS. 148 and 149 show simplified versions of the particular service and/or information request IQ.sub.n (28) being parsed, processed, and/or formatted into the current request group QA.sub.nc (50), and utilization of information therefrom to make the requests Q.sub.n1 . . . Q.sub.nm (29), obtain the responses R.sub.n1 . . . R.sub.nm (32), parse, process, format, group, sort, and/or organize the service and/or information group G.sub.n (35) having the query information groups GI.sub.n1 . . . GI.sub.nz (63) therein, and incorporate information therefrom into the particular service and/or information response IR.sub.n (34).

(873) The query information groups GI.sub.n1 . . . GI.sub.nz (63) associated with a typical securities transaction may comprise a plurality of order books OB.sub.n1 . . . OB.sub.nz (410), in accordance with the present invention.

(874) FIG. 150 shows the service and/or information group G.sub.n (35) associated with a typical securities transaction. The query information groups GI.sub.n1 . . . GI.sub.nz (63) are represented as the plurality of order books OB.sub.n1 . . . OB.sub.nz (410) for a plurality of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies, resulting from the user service and/or information request iq.sub.n (27) being executed by the user U.sub.n (12) at the user interface I.sub.n (14), in accordance with the present invention.

(875) Now, again, the query information groups GI.sub.n1 . . . GI.sub.nz (63) comprise the plurality of order books OB.sub.n1 . . . OB.sub.nz (410) for the plurality of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies, and are represented in FIG. 150 as the plurality of order books OB.sub.n1 . . . OB.sub.nz (410) for the plurality of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies.

(876) Each of the queries QQ.sub.n1 . . . QQ.sub.nm (53) typically comprises a keyword phrase, comprising at least one keyword, indicia, or symbol, which signifies the security for which each respective one of the plurality of order books OB.sub.n1 . . . OB.sub.nz (410) is to be returned, and which are shown in FIG. 150.

(877) Typical market data is shown in FIG. 150 for the order books OB.sub.n1 . . . OB.sub.nz (410) for Exxon (XOM)®, IBM (IBM)®, and Bank of America (BAC)®, resulting from the queries QQ.sub.n1 . . . QQ.sub.nm (53), which typically comprise the keyword phrases XOM®, IBM®, and BAC®, and which signify the securities for which the order books are to be displayed, although other suitable keyword phrases, indicia, symbols, and/or a combination thereof may be used.

(878) The plurality of order books OB.sub.n1 . . . OB.sub.nz (410) have names NM.sub.n1 . . . NM.sub.nz (412) of the securities and other identifiers ID.sub.n1 . . . ID.sub.nz (414), such as keyword phrases, indicia, symbols, and/or a combination thereof, in this case the ticker symbol, that identifies for which security that the market data of the respective plurality of order books OB.sub.n1 . . . OB.sub.nz (410) is for. FIG. 150 shows market data for Exxon®, IBM®, and Bank of America®, each of the plurality of order books OB.sub.n1 . . . OB.sub.nz (410) typically being different from each other. In order to trade with an ECN, the user U.sub.n (12) must typically be a subscriber to the ECN.

(879) Last trade prices TD.sub.n1 . . . TD.sub.nz (416), indicia ND.sub.n1 . . . ND.sub.nz (418), in this case arrows or other suitable indicia, indicating the current movement of the highest bid, net changes NC.sub.n1 . . . NC.sub.nz (420) of the last trade prices with respect to yesterday's closing prices, volumes VL.sub.n1 . . . VL.sub.nz (422) of the last trades, high trade prices for the day HH.sub.n1 . . . HH.sub.nz (424), low trade prices for the day LW.sub.n1 . . . LW.sub.nz (426), and the total volumes traded for the day VT.sub.n1 . . . VT.sub.nz (428) are also shown in FIG. 150 for each of the securities.

(880) The plurality of order books OB.sub.n1 . . . OB.sub.nz (410) comprise bid data BD.sub.n1 . . . BD.sub.nz (430) and offer data OD.sub.n1 . . . OD.sub.nz (432) for each of the securities, as shown in FIG. 150. The bid data BD.sub.n1 . . . BD.sub.nz (430) is sorted in descending order according to bid price DP.sub.n1 . . . DP.sub.nz (434). The offer data OD.sub.n1 . . . OD.sub.nz (432) is sorted in ascending order according to offer price AP.sub.n1 . . . AP.sub.nz (436).

(881) The bid data BD.sub.n1 . . . BD.sub.nz (430) and the offer data OD.sub.n1 . . . OD.sub.nz (432) comprise a plurality of bid quotes QB.sub.n11 . . . QB.sub.nzx (438) and a plurality of offer quotes QO.sub.n11 . . . QO.sub.nzx (440), respectively, for each of the plurality of order books OB.sub.n1 . . . OB.sub.nz (410). Each of the bid quotes QB.sub.n11 . . . QB.sub.nzx (438) and each of the offer quotes QO.sub.n11 . . . QO.sub.nzx (440) comprise volume in hundreds (100's) of shares 442, an identifier 444, in this case a four character identifier, that identifies the ECN or market maker of the security (the identifier 444 may be a keyword phrase, indicia, or symbol or other suitable identifier), and the bid price DP.sub.n1 . . . DP.sub.nz (434) or the offer price AP.sub.n1 . . . AP.sub.nz (436). An identifier 446, which may be an asterisk (*) or other suitable identifier, shows the most recently updated quote for each of the plurality of order books OB.sub.n1 . . . OB.sub.nz (410).

(882) A plurality of optional order entry boxes OE.sub.n1 . . . OE.sub.nz (448) and OG.sub.n1 . . . OG.sub.nz (450) are also shown in each of the plurality of order books OB.sub.n1 . . . OB.sub.nz (410), which allows the user U.sub.n (12) to place a plurality of bids and/or offers, respectively, for any and/or all of the plurality of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies shown in the plurality of order books OB.sub.n1 . . . OB.sub.nz (410), by entering suitable bid and/or order information. The user U.sub.n (12) may optionally also place a plurality of bids and/or offers for any and/or all of the plurality of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies shown in the plurality of order books OB.sub.n1 . . . OB.sub.nz (410) by highlighting the particular bid data BD.sub.n1 . . . BD.sub.nz (430) and/or the offer data OD.sub.n1 . . . OD.sub.nz (432) for the plurality of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies shown in FIG. 150 and clicking on the highlighted bid data BD.sub.n1 . . . BD.sub.nz (430) and/or the highlighted offer data OD.sub.n1 . . . OD.sub.nz (432) with a mouse or other suitable tool. The plurality of bids and/or offers may alternatively be entered on a separate graphical user interface.

(883) FIG. 150 shows the plurality of order books OB.sub.n1 . . . OB.sub.nz (410) for securities, although other suitable financial products, financial instruments, stocks, commodities, currencies, and/or combinations thereof may be used.

(884) The query information groups GI.sub.n1 . . . GI.sub.nz (63) associated with a typical securities transaction may comprise a plurality of order books OB.sub.n1 . . . OB.sub.nz (410), in accordance with the present invention, as shown in FIG. 150, or, alternatively, the query information groups GI.sub.nz (63) associated with another typical securities transaction may comprise a single order book OB.sub.nz (410), as shown in FIG. 151, in accordance with the present invention.

(885) The user U.sub.n (12) may optionally enter one or more orders into any single order book OB.sub.nz (410) or plurality of order books OB.sub.n1 . . . OB.sub.nz (410). The order and/or orders may be, for example, for products, items, financial products, financial instruments, stocks, commodities, currencies, orders, purchases, and/or instructions, and/or payment, and/or other information and/or services to be directed to and/or requested of third parties, and/or combinations thereof. The order and/or orders may be placed, for example, with the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22), any of which may be ECNs, other suitable parties and/or third parties, and/or other ones of the clients C.sub.1 . . . C.sub.n (16) through the server PS (18) and/or the client C.sub.n (16). The order and/or orders may, thus, be placed through and by the server PS (18) and/or the client C.sub.n (16), eliminating the need for the user U.sub.n (12) to place one or more separate ones of the orders with the third parties, ECNs, the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22) separately and/or individually.

(886) FIG. 150 shows a particular service and/or information group G.sub.n (35) associated with a typical securities transaction, showing query information groups GI.sub.n1 . . . GI.sub.nz (63) represented as a plurality of order books OB.sub.n1 . . . OB.sub.nz (410) at the user interface I.sub.n (14) for a plurality of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies; and FIG. 151 shows a particular service and/or information group G.sub.n (35) associated with a typical securities transaction, showing the query information group GI.sub.nz (63) represented as the order book OB.sub.nz (410) at the user interface I.sub.n (14) for a security, stock, financial product, financial instrument, commodity, and/or currency.

(887) The order books OB.sub.n1 . . . OB.sub.nz (410) at the user interface I.sub.n (14) of FIG. 150 and/or the order book OB.sub.nz (410) at the user interface I.sub.n (14) of FIG. 151 may be used as an order form or order forms, which provide direct placement of orders and/or confirmation of orders and/or purchases with the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22), and/or ECNs, and/or third parties that reside on the network 24. The user U.sub.n (12) may enter the order placement into the user interface I.sub.n (14) through the user input UI.sub.n (25), and receive order confirmation through the user interface I.sub.n (14). The client C.sub.n (16) may communicate the order placement from the user interface I.sub.n (14) to the server PS (18), which may communicate the order placement to the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22) and/or the ECNs and/or the third parties. The server PS (18) may alternatively and/or additionally communicate the order confirmation received from the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22) and/or the ECNs and/or the third parties to the client C.sub.n (16), which may communicate the order confirmation to the user interface I.sub.n (14) for presentation to the user U.sub.n (12). The order placement and/or the order confirmation may be stored within the server PS (18) and/or the client C.sub.n (16). The order placement and/or the order confirmation is typically secure, and may be encrypted, and is typically communicated using secure communications means.

(888) FIG. 151 shows the service and/or information group G.sub.n (35) associated with another typical securities transaction, in which, for example, one or more transactions are conducted for a single security, stock, financial product, financial instrument, commodity, and/or currency. The query information groups GI.sub.n1 (63) are represented as the order books OB.sub.nz (410) for the security, stock, financial product, financial instrument, commodity, and/or currency, resulting from the user service and/or information request iq.sub.n (27) being executed by the user U.sub.n (12) at the user interface I.sub.n (14).

(889) The optional order entry boxes OE.sub.nz (448) and OG.sub.nz (450) shown in the order book OB.sub.nz (410) allow the user U.sub.n (12) to place one or more bids and/or offers, respectively, for a security, stock, financial product, financial instrument, commodity, and/or currency, by entering suitable bid and/or order information. One or more bids and/or offers may be made substantially simultaneously, using the optional order entry boxes OE.sub.nz (448) and OG.sub.nz (450).

(890) The optional order entry boxes OE.sub.nz (448) comprise a plurality of bid volume entry boxes 460, a plurality of bid price entry boxes 462, and a plurality of bid ECN identifier boxes 464 that identify the ECN or market maker of the security for which a bid or bids are may be made. Volume, bid price, and ECN may be entered into the bid volume entry boxes 460, the bid price entry boxes 462, and the bid ECN identifier boxes 464, respectively to place one or more bid orders substantially simultaneously. One or more bid orders may be entered into the optional order entry boxes OE.sub.nz (448), by entering bid volume, bid price, and ECN into the respective bid volume entry boxes 460, the bid price entry boxes 462, and the bid ECN identifier boxes 464, to place one or more bid orders, respectively, substantially simultaneously.

(891) The optional order entry boxes OG.sub.nz (450) comprise a plurality of offer volume entry boxes 470, a plurality of offer price entry boxes 472, and a plurality of offer ECN identifier boxes 474 that identify the ECN or market maker of the security for which an offer or offers may be made. Volume, offer price, and ECN may be entered into the offer volume entry boxes 470, the offer price entry boxes 472, and the offer ECN identifier boxes 474, respectively to place one or more offer orders substantially simultaneously. One or more offer orders may be entered into the optional order entry boxes OG.sub.nz (450), by entering offer volume, offer price, and ECN into the respective offer volume entry boxes 470, the offer price entry boxes 472, and the offer ECN identifier boxes 474, to place one or more offer orders, respectively, substantially simultaneously.

(892) Both bid orders and/or offer orders may be made substantially simultaneously and/or separately, as required.

(893) The user U.sub.n (12) may optionally alternatively and/or additionally place bids and/or offers for one or more of the security, stock, financial product, financial instrument, commodity, and/or currency shown in the order book OB.sub.nz (410) by highlighting the particular bid data BD.sub.n1 . . . BD.sub.nz (430) and/or the offer data OD.sub.n1 . . . OD.sub.nz (432) for the security, stock, financial product, financial instrument, stock, commodity, and/or currency, and highlighting and/or clicking on the bid data BD.sub.n1 . . . BD.sub.nz (430) and/or the offer data OD.sub.n1 . . . OD.sub.nz (432) with a mouse or other suitable tool, and/or using a keyboard or other suitable tool for order entry and/or order placement.

(894) Alternatively and/or additionally bid volume and/or offer volume may be entered into one or more bid volume entry boxes 482 and/or one or more offer volume entry boxes 484 adjacent respective ones of the bid quotes QB.sub.n11 . . . QB.sub.nzx (438) and/or the offer quotes QO.sub.n11 . . . QO.sub.nzx (440), to place one or more bid orders and/or one or more offer orders, respectively, substantially simultaneously. Bid orders and/or offer orders may be made by highlighting and/or clicking on the bid volume entry boxes 482 and/or the offer data offer volume entry boxes 484 with a mouse or other suitable tool, and/or using a keyboard or other suitable tool for order entry and/or order placement.

(895) One or more bid orders and/or one or more offer orders may be made substantially simultaneously and/or separately, as required.

(896) Bid orders and/or offer orders may alternatively and/or additionally be entered and/or placed by highlighting and clicking on Bid order box 476, Offer order box 478, and or Submit box 480 with a mouse or other suitable tool, and/or using a keyboard or other suitable tool for order entry and/or placement

(897) The bid orders and/or offer orders may alternatively be entered and/or placed, using any other suitable or separate graphical user interface.

(898) The bid volume entry boxes 482 and/or the offer volume entry boxes 484 adjacent respective ones of the bid quotes QB.sub.n11 . . . QB.sub.nzx (438) and/or the offer quotes QO.sub.n11 . . . QO.sub.nzx (440) may be used to place one or more bid orders and/or one or more offer orders, respectively, substantially simultaneously, for one or a plurality of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies, as shown in FIGS. 150 and 151 for typical ones of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies.

(899) The optional order entry boxes OE.sub.nz (448), comprising the bid volume entry boxes 460, the bid price entry boxes 462, and the bid ECN identifier boxes 464, and/or the optional order entry boxes OG.sub.nz (450), comprising the offer volume entry boxes 470, the offer price entry boxes 472, and the offer ECN identifier boxes 474, may alternatively and/or additionally be used to place one or more bid orders and/or one or more offer orders, respectively, substantially simultaneously, for one or a plurality of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies, as shown in FIGS. 150 and 151 for typical ones of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies. Each of the bid orders and/or the offer orders may typically be placed directly with the appropriate ECNs without the need for additional steps, additional clicks and/or click-throughs, and/or use of additional screens and/or user interfaces. The Bid order box 476, the Offer order box 478, and/or the Submit box 480 may optionally be used to enter and/or place orders for one or a plurality of securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies.

(900) FIG. 151 shows the order book OB.sub.nz (410) for a security, although other suitable financial products, financial instruments, stocks, commodities, currencies, and/or combinations thereof may be used.

(901) Again, the client-server multitasking system 10/metasearch system of the present invention may be used to search or metasearch a single query or keyword phrase of a plurality of sites and/or ECNs substantially simultaneously and/or place one or a plurality of orders/purchases for the same and/or different securities, stocks, financial products, financial instruments, stocks, commodities, and/or currencies, or items substantially simultaneously.

(902) Now, again, the client-server multitasking system 10/metasearch system may be used to make a single query or keyword search or multiple queries and/or multiple keyword searches of multiple sites, search engines, servers, ECNs, databases, clients, information sources, applications, software applications, programs, and/or software programs substantially simultaneously, consolidating, grouping and/or sorting search results, and as a single point of purchasing and/or placing and/or ordering one or more items.

(903) A partial list of present and past ECNs, some of which have been included in FIGS. 150 and 151, includes: ARCA: Archipelago ECN®; BEST: Bear, Stearns and Co., Inc.®; BTAB: BT Alex Brown Inc.®; DLJP: Donaldson, Lufkin and Jenrette Securities®; FBCO: Credit Suisse First Boston Corporation®; GSCO: Goldman, Sachs and Co.®; HMQT: Hambrecht and Quist LLC®; HRZG: Herzog, Heine, Geduld, Inc.®; INCA: Instinet Corp. (ECN)®; ISLD: The Island ECN®; MASH: Mayer and Schweitzer, Inc.®; MLCO: Merrill Lynch, Pierce, Fenner and Smith Inc.®; MSCO: Morgan Stanley and Co., Inc.®; NITE: Knight Securities, Inc.®; PIPR: US Bancorp Piper Jaffray Inc.®; PRUS: Prudential Securities Inc.®; RSSF: Bancboston Robertson Stephens Inc.®; SBSH: Salomon, Smith Barney Inc.®; TNTO: Terra Nova Trading, LLC®; TSCO: Troster Singer Corporation®; Direct Edge ECN®; BATS®; Currenex®; Fxall®; eSpeed®; Global Link®; Hotspot®; MilanFX®; NYFIX®; Track ECN®; and Dukascopy®.

(904) The client-server multitasking/metasearch system and process is capable of providing manual and/or timed updates. Such timed updates allow for continuous updating of information provided to the requestor and/or the user. The sampling rate or frequency of the timed updates may be adjusted by the user to range from less than one millisecond to milliseconds to seconds to hours to days or longer periods, or other suitable intervals. The timed updates may be automatic or semi-automatic, or a reminder may be set for the user to request manual timed updates.

(905) Additional Discussion on Sensor Nodes, Motes, Mobile Servers, Cellular Servers, and Wireless Servers, Wireless Sensors, Wireless Sensor Networks

(906) The client-server multitasking system 10/metasearch system of the present invention may be used to request, retrieve and organize information and/or data from multiple devices, wireless devices and/or multiple wireless servers having multiple data streams, and group and/or sort the information and/or data in real-time and on-the-fly, according to information in the user's request and/or data stream identifiers.

(907) A wireless sensor network (WSN) is a wireless network comprising spatially distributed autonomous devices, using sensors to cooperatively monitor physical, environmental and/or other conditions at different locations. Wireless sensor networks (WSNs) may also be used for tracking and/or control.

(908) Typical applications of WSNs include monitoring, tracking, and controlling, and may be used in battlefield surveillance, command and control systems, civilian applications, including environment and habitat monitoring, healthcare applications, automation, traffic control, and other suitable applications. Other applications include security, intrusion detection, perimeter warning systems, intruder detection, fire safety, medical monitoring, smart spaces, seismic detection, monitoring of ice flows and icebergs, military surveillance, inventory tracking, process monitoring, structural systems monitoring, nuclear reactor monitoring, ocean current and wave detection and monitoring, atmospheric monitoring, monitoring of air, water, and ground pollutants, tracking of people and animals, and numerous other suitable applications.

(909) A wireless sensor network (WSN) and/or wireless sensor networks (WSNs) may be scattered throughout a region to collect data through its sensor nodes.

(910) Information and/or data may be collected for a host of parameters, including, for example, temperature, sound, light, pressure, motion, heat, pressure, sound, light, magnetic fields, electromagnetic fields, vibration, wind speed and direction, and other suitable information and/or data.

(911) Wireless sensor networks (WSNs) may comprise heterogeneous sensor webs and/or homogeneous sensor webs. Heterogeneous sensor webs may have a combination of the same and/or different types of motes, sensors, and/or nodes, whereas homogeneous sensor webs may have substantially the same types of motes, sensors, and/or nodes. Wireless sensor networks (WSNs) will often comprise distributed databases.

(912) Wireless sensor networks (WSNs) may be extended to include wireless robotic devices, in which in addition to sensing and/or cooperatively monitoring physical, environmental and/or other conditions at different locations, but also to control systems, controlling, moving and/or following commands to move from location to location and/or accomplish manual and/or mechanical tasks and/or other tasks, requiring a degree of dexterity and/or combinations thereof.

(913) Certain sensors may be interactive, whereas other sensors may not be interactive. For those sensors that are interactive, information and/or data may be retrieved from the interactive sensors and/or via at least one node or a plurality of nodes that are interactive. For those sensors that are not interactive, information and/or data may be retrieved via at least one node or a plurality of nodes that are interactive. A web browser or other suitable graphical user interface may be used to monitor the wireless sensor networks (WSNs).

(914) Miniaturization and low cost are often key ingredients in wireless sensor networks (WSNs). The size of a single sensor node can vary from shoebox-sized nodes down to devices the size of a cubic millimeter or even down to the size of a grain of dust. Sensor nodes may be considered to be small computers or servers, or server devices.

(915) Each sensor node, which may optionally be called a mote, is a node in the wireless sensor network (WSN) that is often capable of performing some processing, gathering sensory information, and communicating with other connected nodes in the network.

(916) Each sensor node may be considered to be a small computer, server, or server device. In addition to one or more sensors and/or robots, each sensor node in a wireless sensor network (WSN) is typically equipped with a transceiver or other wireless communications device, a small processor, microprocessor, or microcontroller, additional optional memory, one or more analog to digital converters, as required, and an energy source, such as a battery, energy harvesting device, or other suitable power source. The wireless transceiver may be a radio transceiver, an optical transceiver, or other suitable wireless communications device or combination thereof. Data transmission is usually multi-hop, i.e., from node to node, towards the base stations, and is often based upon distributed algorithms.

(917) Wireless sensor networks (WSNs) may have one or more gateways, gateway sensor nodes, or base stations between the sensor nodes and the end user, and which may have more computational power, energy resources, and/or communication resources than the sensor nodes.

(918) The sensor nodes are typically deployed to sense, track, and/or control phenomena, and the gateway node is typically the interface between the wireless sensor network (WSN) and the world external to the wireless sensor network (WSN). The gateway nodes and/or certain ones of the sensor nodes and/or other suitable components of the wireless sensor network (WSN) may be configured to perform as servers, depending upon the configuration of the wireless sensor network (WSN).

(919) Substantially the same system and method that is used to retrieve information and/or data for wireless sensor networks (WSNs) may be used for other wireless devices and/or RFIDs.

(920) Each of the requests Q.sub.11 . . . Q.sub.nm (29) may then be made of certain ones of the same and/or different ones of the gateway nodes and/or certain ones of the sensor nodes and/or other suitable components of the wireless sensor network (WSN) in the same manner as the requests Q.sub.11 . . . Q.sub.nm (29) are made of the servers S.sub.1 . . . S.sub.z (20), and/or the optional servers SO.sub.1 . . . SO.sub.p (22) of the client-server multitasking system 10/metasearch system.

(921) The client-server multitasking system 10/metasearch system may then be used to process multiple responses from the certain ones of the same and/or different ones of the gateway nodes and/or the certain ones of the sensor nodes and/or the other suitable components of the wireless sensor network (WSN), and group and sort the results, all in real time and on-the-fly.

(922) The particular service and/or information request IQ.sub.n (28) received from the corresponding client C.sub.n (16) is parsed, processed, and/or formatted by the server PS (18) into the current request group QA.sub.nc (50), and information therefrom is used to make the requests Q.sub.n1 . . . Q.sub.nm (29) of the certain ones of the same and/or different ones of the gateway nodes and/or the certain ones of the sensor nodes and/or the other suitable components of the wireless sensor network (WSN), obtain the responses R.sub.n1 . . . R.sub.nn (32) therefrom, parse, process, format, group, sort, and/or organize the service and/or information group G.sub.n (35) having the query information groups GI.sub.n1 . . . GI.sub.nz (63) therein, incorporate information therefrom into the particular service and/or information response IR.sub.n (34), and return the particular service and/or information response IR.sub.n (34) to the corresponding client C.sub.n (16).

(923) Substantially the same system and method that is used to retrieve information and/or data for wireless sensor networks (WSNs) may be used for other wireless devices and/or RFIDs.

(924) The client-server multitasking/metasearch system and process is capable of providing manual and/or timed updates. Such timed updates allow for continuous updating of information provided to the requestor and/or the user. The sampling rate or frequency of the timed updates may be adjusted by the user to range from less than one millisecond to milliseconds to seconds to hours to days or longer periods, or other suitable intervals. The timed updates may be automatic or semi-automatic, or a reminder may be set for the user to request manual timed updates.

(925) Management, Monitoring, and Control of Industrial Processes, Industrial Plants and Facilities, Manufacturing Plants and Facilities, Oil Drilling, and Oil Refining

(926) The client-server multitasking/metasearch system and process may be used in a variety of industrial control, industrial process control, manufacturing, oil drilling, oil refining, power plant, water and wastewater treatment, management, control, and monitoring applications, and other suitable applications.

(927) The client-server multitasking/metasearch system and process may be used with wireless and/or wired sensors and/or controls and/or robots to manage, control, and monitor a large variety of industrial and other suitable processes and/or facilities.

(928) Substantially the same system and method that is used to retrieve information and/or data for wireless sensor networks (WSNs) and/or Radio Frequency Identification (RFID) devices may be used for wireless and/or wired sensors and/or controls and/or robots to manage, control, and monitor a large variety of industrial and other suitable processes and/or facilities.

(929) The client-server multitasking/metasearch system and process may be used in “digital oil fields”, comprising suites of interactive and complementary technologies that facilitate gathering and analyzing data throughout a job site. For example, “intelligent wells,” may have fiber-optic sensors and/or other sensors within or associated with drilling apparatus, which may be controlled manually by operators on the surface and/or semi automatically or automatically through closed-loop information systems. The fiber optic and/or other sensors transmit data streams about the wells and their environment, enabling operators to respond to shifting circumstances in real time. The client-server multitasking/metasearch system and process may perform multiple queries of multiple fiber optic sensors and/or the other sensors substantially simultaneously and present results to the operators in return groups selected by the operators. Physical parameters, performance levels, and potential equipment failure may be provided to the operators via the client-server multitasking/metasearch system and process. The operators, for example, may adjust fluid pressure or valve settings as the drilling surface becomes more or less permeable.

(930) The client-server multitasking/metasearch system and process may be applied to a variety of different “digital oil fields”, including managing operations of both new and mature oil and gas fields, discovering new reserves, on shore and offshore exploration and drilling, and other suitable oil and gas operations.

(931) Substantially the same system and method that is used to retrieve information and/or data for “digital oil fields” and/or wireless sensor networks (WSNs) and/or Radio Frequency Identification (RFID) devices may be used in a variety of industrial control, industrial process control, manufacturing, automobile and other types of manufacturing, pharmaceutical, petrochemical, and chemical processing and manufacturing, oil drilling, oil refining, power plant, water and wastewater treatment, management, control, and monitoring applications, mining, ore recovery, and other suitable applications. Information and/or data retrieved from the fiber optic sensors and/or other sensors may be communicated to the client-server multitasking/metasearch system and process via one or more communications and network technologies or combination thereof, including satellite relays and other suitable network and communications systems.

(932) The client-server multitasking/metasearch system and process is capable of providing manual and/or timed updates. Such timed updates allow for continuous updating of information provided to the requestor and/or the user. The sampling rate or frequency of the timed updates may be adjusted by the user to range from less than one millisecond to milliseconds to seconds to hours to days or longer periods, or other suitable intervals. The timed updates may be automatic or semi-automatic, or a reminder may be set for the user to request manual timed updates.

(933) Social Networks

(934) Any one or more of the servers S.sub.1 . . . S.sub.z (20) and/or any one or more of the optional servers SO.sub.1 . . . SO.sub.p (22) of the client-server multitasking system 10/metasearch system may comprise one or more social networks and/or one or more small world networks.

(935) A social network may be considered to be a social structure or other suitable structure comprised of a network of actors or nodes, comprising individuals, entities, organizations, devices, systems, processes, and/or other suitable structures, certain ones of which are linked to one another by ties or links.

(936) Although social networks and/or small world networks are often thought of as being social in context, such as, for example, communities of people who share interests and/or activities, and who typically interact with one another, such as friends, chat, video, file sharing, blogging, messaging, email, voice chat, and discussion groups, social networks may be other than social in context, and may include real world instances of technological, business, economic, and biological social networks, among other social networks. Social networks and/or small world networks that are not social in context may include, for example, molecular networks and/or electric power grids, and other suitable social networks and/or small world networks that are not social in context.

(937) A social network may be viewed in terms of relationships, in which the social network comprises a structure having nodes and ties that tie certain of the nodes to one another via one or more interdependencies.

(938) Social networks that are social in context typically comprise social structures that may be viewed in terms of social relationships, in which the nodes generally comprise individuals and/or organizations that are tied together by interdependencies, such as values, friends, relationships, ideas, philosophies, thoughts, trade, financial exchange, visions, likes, dislikes, conflicts, links, kinship, disease transmission, travel routes, technologies, interests, and/or other suitable interdependencies.

(939) A social network may be represented as a heterogeneous and multirelational data set, which may be represented by a graph, comprising the nodes and links or ties. The graph may comprise the nodes corresponding to objects and edges corresponding to the links or ties representing relationships or interactions between objects. Nodes have attributes and links or ties have attributes; objects may have class labels; and links or ties may be unidirectional or bidirectional.

(940) A small world network may be characterized as a social network having a high degree of clustering for a small fraction of the nodes.

(941) Data mining may be used to determine and/or gather information about the attributes of the nodes and/or the attributes of the links or ties and/or information about the objects of one or more social networks substantially simultaneously and/or determine and/or gather information about the interdependencies and/or interrelationships within one or more social networks and/or between one or more social networks, substantially simultaneously, in accordance with the present invention.

(942) The attributes, interdependencies and/or interrelationships may be also be described in terms of “profiles” of the users of the social networks and/or small world networks that are social in context. The profiles may be automatically, semi automatically, and/or manually generated by the users. Certain of the social networks and/or small world networks, such as social networking services, allow users to create profiles of themselves, which may include users' interests, likes, dislikes, personal characteristics, and other attributes, and to generate communities of certain users based upon selected profiles, attributes, interdependencies, and/or interrelationships, and memberships in the communities.

(943) The present invention may be used to determine selected attributes, preferences, objects, links, and/or ties, and/or other suitable criteria, and return such information and/or data to the client.

(944) The present invention may be used to obtain information and/or services from a plurality of social networks and/or small world networks, organizing, grouping, and/or sorting the results and/or connecting the plurality of social networks and/or small world networks together; obtaining information and/or services from the plurality of social networks and/or obtaining information and/or services from other sources, and organizing, grouping, and/or sorting the results from the social networks and/or the small world networks and/or the other sources substantially simultaneously.

(945) One or more searches and/or one or more queries may be made of one or more social networks substantially simultaneously, and the responses therefrom may be parsed, processed, formatted, grouped, sorted, and/or organized into groups according to selected attributes, objects, links, and/or ties, profiles, characteristics, communities, groups, and/or other suitable criteria, and returned to the corresponding client, in accordance with the present invention. These searches and/or queries may be used to aggregate and/or collect content from multiple social networks and/or small world networks and provide the results to a user or users via the client-server multitasking/metasearch system and process of the present invention. The results may be grouped and/or sorted according to attributes, objects, links, and/or ties, profiles, characteristics, communities, groups, and/or other suitable criteria selected by the user or users and returned to the requesting client via the client-server multitasking/metasearch system and process of the present invention.

(946) Typical social networks may include, for example, social networks, social network sites, social network services, small world networks, small world network sites, communities, virtual communities, online communities, e-communities, and other suitable social networks and/or small world networks, and combinations thereof.

(947) Substantially the same system and method of the present invention that is used to request and/or retrieve information and/or data associated with other applications, systems, processes, and/or devices residing and/or running on any one or more of the servers S.sub.1 . . . S.sub.z (20) and/or any one or more of the optional servers SO.sub.1 . . . SO.sub.p (22) may be used to request and/or retrieve information and/or data associated with one or more social networks and/or one or more small world networks, obtain the responses R.sub.n1 . . . R.sub.nm (32) therefrom, parse, process, format, group, sort, and/or organize the service and/or information group G.sub.n (35) having the query information groups GI.sub.n1 . . . GI.sub.nz (63) therein, incorporate information therefrom into the particular service and/or information response IR.sub.n (34), and return the particular service and/or information response IR.sub.n (34).

(948) Again, any one or more of the servers S.sub.1 . . . S.sub.z (20) and/or any one or more of the optional servers SO.sub.1 . . . SO.sub.p (22) of the client-server multitasking system 10/metasearch system may comprise one or more social networks and/or one or more small world networks.

(949) Each of the requests Q.sub.11 . . . Q.sub.nm (29) may be made of any one or more of the servers S.sub.1 . . . S.sub.z (20) and/or any one or more of the optional servers SO.sub.1 . . . SO.sub.p (22) comprising the one or more social networks and/or the one or more small world networks in the same manner as any other requests Q.sub.11 . . . Q.sub.nm (29) and/or in addition to those requests Q.sub.11 . . . Q.sub.nm (29) of the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22) of the client-server multitasking system 10/metasearch system, obtain the responses R.sub.n1 . . . R.sub.nm (32) therefrom, parse, process, format, group, sort, and/or organize the service and/or information group G.sub.n (35) having the query information groups GI.sub.n1 . . . GI.sub.nz (63) therein, incorporate information therefrom into the particular service and/or information response IR.sub.n (34), and return the particular service and/or information response IR.sub.n (34) to the corresponding client C.sub.n (16).

(950) In more detail, each of the requests Q.sub.11 . . . Q.sub.nm (29) may then be made of any one or more of the servers S.sub.1 . . . S.sub.z (20) and/or any one or more of the optional servers SO.sub.1 . . . SO.sub.p (22) and/or certain ones of the same and/or different ones of the servers S.sub.1 . . . S.sub.z (20) and/or certain ones of the same and/or different ones of the optional servers SO.sub.1 . . . SO.sub.p (22) comprising the one or more social networks and/or the one or more small world networks, in addition to and/or in lieu of any one or more of the applications, suitable systems, processes, and/or devices, or any combination thereof, residing and/or running on the servers S.sub.1 . . . S.sub.z (20) and/or the optional servers SO.sub.1 . . . SO.sub.p (22) of the client-server multitasking system 10/metasearch system, obtain the responses R.sub.n1 . . . R.sub.nm (32) therefrom, parse, process, format, group, sort, and/or organize the service and/or information group G.sub.n (35) having the query information groups GI.sub.n1 . . . GL.sub.nz (63) therein, incorporate information therefrom into the particular service and/or information response IR.sub.n (34), and return the particular service and/or information response IR.sub.n (34) to the corresponding client C.sub.n (16).

(951) Additional Processing and Add-on Applications

(952) Additional processing and/or add-on applications, such as spreadsheet programs and/or database applications may be added to the client-server multitasking system 10, the client-server multitasking process 99, and/or the multitasking process 104, as required.

(953) Additional processing and/or add-on programs and/or applications, such as spreadsheet programs and/or applications, and/or database applications and/or programs, and/or other suitable processing may be used to further process the output of the client-server multitasking system 10/metasearch system, the client-server multitasking process 99/metasearch process, and/or the multitasking process 104/metasearch process of the present invention, as required.

(954) Although the present invention has been described in considerable detail with reference to certain preferred versions thereof, other versions are possible. Therefore, the spirit and scope of the appended claims should not be limited to the description of the preferred versions contained herein.