Browsing should span to remote Toolboxes

[jukka]

(for story #29, #224) Browsing content, tools, activities and people should also use results from remote Toolboxes.

[jukka]

We've been discussing how to organize the network of toolboxes and currently it looks like we'll have one central lemill.net that will provide the ZCatalog indexes for searches. So the results of remote toolboxes would mean getting results from that (big) index and appending them to local results.

There are though some issues I'm not sure about: ZCatalog can provide 'lazy' results, as when asked for all content objects and displaying them as batches of 30, Catalog will provide them in those groups of thirty. If we use this with remote catalog, it answers faster, but every next batch will also need a remote query, as opposed to getting the whole list of hits and locally manipulating them as long as they are 'the result'. Also if we take the remote results lazy, we have to compare them to local results every time we get a new batch to decide if local results belong to this batch. (Remote results contain 'Aardvark', 'Akhnaten', 'Arrow' and local 'Akhnaten' and 'Alligator' - they have to reordered into batch of displayable size.)

Some of the user properties need also be catalogued so that users can be remotely searched. Current user searches don't use portal_catalog at all.

[tarmo]

Not a defect. And needs more design before implementation.