I have been trying to decide where to place the interfaces (i.e. what is provider specific and what isn't). I've also been researching Lucene and Casandra to to try and determine if either or both (via Lucandra) would be appropriate and how their use would affect the interfaces.
There's also the problem of an impedance mismatch between the robot search interface and what would be needed to support live search results (ala Google Wave). I'm leaning towards an iterator plus listener model plus an adaptor for the robot search interface. I'm trying to make sure the interfaces don't place constraints on scalability. Once I have something that seems to look right, I'll post a patch for review. I should also mention that I haven't spent much time on this since Christmas. If there are others that are keen to work on this I don't mind collaborating. Competing designs are welcome. This is a meritocracy after all :-) -Tad On Wed, Jan 12, 2011 at 2:42 AM, Alex North <ano...@google.com> wrote: > Tad Glines was beginning designs for the server-side indexing infrastructure > needed to do non-trivial search. > > On 12 January 2011 17:21, David Hearnden <hearn...@google.com> wrote: > >> As far as I know, nobody is working on that. You're more than welcome to >> dive in! >> >> -Dave >> >> On Tue, Jan 11, 2011 at 5:43 AM, Yuri Z <vega...@gmail.com> wrote: >> >> > I am currently working on the UI for the search functionality. I would >> like >> > to know if someone is working on the server side aspects of this. >> > Thanks >> > >> >
