the second hitch is that "docs" only makes sense in ssuedo code ... in
reality there are DocSets and DocLists, and the efficiencies of geting
only one instead of both can be significant, but if the first phase of
processing doesn't know what expectations the later phases have (facet or
not? returns aDocList in teh response or not?) it may have to assume you
need both.
This is where Yonik's "prepare" loop suggestion could help:
for (component : List<Component>) {
// Do we need a DocList? DocSet? both?
component.prepare(req, rsp);
}
while (not all components done) {
for (component : List<Component>) {
boolean done = component.process(req,rsp);
}
}
- - - - -
Yonik, what components do you imagine need to run multiple times?
- - - - -
In this style approach, I think we will want a strongly typed response
builder so components know where to put stuff and what has been done. I
don't think adding/retrieving stuff to a freeform NamedList or stuffing
stuff into SolrQueryRequest.getContext() would be much fun to work with.
ryan
