: > but the first step would probably be to provide the same
: > level of functionality MultiSearcher
:
: Ahh, I was thinking the first step would be to try and use
: MultiSearcher via RemoteSearcher/RemoteSearchable.
Ah ... you were thinking something like this...
MultiSearcher(Searchable[])
--> SolrRemoteSearchable
--HTTP--> http://solr:9999/select?qt=standard
...i was thinking of something like this...
SolrMultiSearcher(URL[])
--HTTP--> http://solr:9999/select?qt=RemoteSerachableQueryHandler
...where MultiSearcher and SolrMultiSearcher inherit common logic from
some subclass.
My hunch is that the way MultiSearcher uses the Searchable API would make
it impractical to use MultiSearcher as is, because it would probably
making many "little" method calls that would each have to be sent as HTTP
requests and involve XML parsing. I was assuming that it would be better
to make a request handler that knew everything the multiseracher was going
to be interested in and could return it all at once.
But like i said, i don't really know anything about how MultiSearcher
works, and i really don't understand RemoteSearchable ... so i could be
way off.
-Hoss
