Hi, Adding the search method is a very good start but the mayor work will be the engine and stores.
The option method would call public SearchLanguage[] getSupportedLanguages(SlideToken token) in the search interface. (maybe a subject parameter should be added to select the store depending on the scope) On the store level this method is called SearchLanguage[] getSupportedLanguages(); and returns the needed information. Regards Dirk "Wallmer, Martin" wrote: > > Hi, > > which parts have to be implemented in slide, which ones in the store? So far > as I understand the search fragments in org.apache.slide.search, > SearchLanguage, Search.java and SearchRequest.java are abstract classes, > that will be overridden by at least a concrete basicSearch implementation. > An own SearchLanguage could be implemented by directly inheriting from these > base classes or by extending the basic search implementation. > A store specific implementation could of course interact directly with the > underlying database, whats about basic search? > > Adding the SEARCH method seems to be straight forward (after a very brief > look). An open question currently is, how the OPTIONS method knows which > resource allows SEARCH and what grammars. > > If you think that could be a good starting point to contibute, I can start > with the webdavServlet. > > Martin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
