On Fri, 15 Feb 2008, Tobias Schlitt wrote:

> On 02/15/2008 04:43 PM Derick Rethans wrote:
> 
> > +The classes representing documents need to implement an interface though 
> > that
> > +specifies __get_state() and __set_state() - something we forgot for
> > +PersistentObject.
> 
> These methods are named getState() and setState() in PersistentObject. 
> And the interface defining those actually exists in PersistentObject now 
> (ezcPersistentObject). We should stick to these method names, I think.

Fixed.

> >  ezcSearchHandler
> >  ----------------
> >  
> >  The base class that all search backends implement. The handlers now how to
> >  communicate to the backends, generate correct search query strings, and 
> > how to
> > -present results. Handlers can also accept search-backend specific options.
> > +present results. Handlers can also accept search-backend specific options. 
> > For
> > +the first version only ezcSearchSolrHandler is planned, while later 
> > versions
> > +might also have backends for Google, Yahoo! etc. A backend does not have to
> > +implement the index(), createDeleteQuery() and delete() methods, as they 
> > are
> > +not available for every handler.
> 
> Could you name and describe the interfaces defining these methods here? 
> I'd suggest ezcSearchIndexHandler and ezcSearchDeleteHandler.

Actually, it does not make sense to have to interfaces for this, as 
indexing and deleting are tied together. I updated the text though.

regards,
Derick
-- 
Components mailing list
[email protected]
http://lists.ez.no/mailman/listinfo/components

Reply via email to