Check out for instance www.twigkit.com which is a light-weight middleware (as well as GUI framework) for Solr. It could speed up development time considerably for your project. It has hooks to transform queries before they are sent to Solr and process responses before displaying, if needed.
-- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com On 19. nov. 2010, at 22.59, Dan Lynn wrote: > You might be able to skip on a front-end to solr by making extensive use of > XSL to format the results, but there are several other arguments putting code > in front of solr (e.g. saved searches, custom sorting, result-level embedded > actions, etc..) > > Cheers, > Dan > > On 11/19/2010 01:58 PM, cyang2010 wrote: >> Hi, >> >> I am new to the lucene/solr. I have a very general question, and hope to >> hear your recommendation. >> >> Do you need a middleware/module between your search client and solr server? >> The response message is very solr specific. Do you need to translate it to >> application object model and return back to search client? In that case, i >> am thinking to have a search module in middleware server. it will >> route/decorate the search request to solr server, and after getting solr >> response then package in an application object list return back to search >> client. Does it make sense? >> >> My concern is whether it is unnecessarily add a network layer and slow down >> the search speed? But from application point of view, i see that is >> necessary. What do you think? >> >> Thanks, >> >> >> cy >
