find-fit-numbers message

See also 2015-10-01_core-algorithm

"find-fit-numbers" is sent when a E presses the button on the enquiry page to try the enquiry.

It takes one enquiry (from local server) and returns (to that node) a number of fits, which may be an estimate if > 10. The enquiry is held only on the originating node, and that only temporarily. It causes no change in central records.

The Enquiry Core is given in data-structures.txt

local server may find local fit numbers as a preliminary, and may estimate total numbers. If less than 10, pass to hub.

local server keeps correspondences between:

• E's correspondent numbers and GUID;
• E's enquiry name and MID.

Enquirer's local server requests new MID from hub.

Message from local server to hub contains as above and adds:

• the freshly minted MID
• local server ID (LUID is kept by server but not needed to be passed on)

Hub

• keeps note of local server ID and MID
• substitutes MID, so which server it comes from is not deducible
• relays message to remote servers

remote servers send back to hub:

• number of fits
• for each Q
• number of people answering that Q
• for each essential Q
• number of people answering that Q fittingly

If non-zero fits, hub sends back to local server:

• number of fits

If zero fits, hub immediately send out a "what-answers-wanted" message...

Q? how are we going to check on fits if we don't send out the GUIDs? The point is, either side may have been blocked, and if so, we don't want the fit to count.