Hi, We're using Lucene in exactly this way (even though we have java throughout).
I have wrapped up lucene as a web service and send search requests as xml strings that are unmarshalled on the server (using JAXB). These are then used to build up a query and execute it returning the number of results (storing the search for the web service client by an ID). Then the client requests a subset of the results (10 at a time in our case) and these are returned as an XML string. We initially had it set up with AXIS (trying to keep to the JAX-RPC standards) but there were too many bugs and performace issues for our production environment. We finally launched with glue (www.themindelectric.com) and I was amazed with the stability and ease of use. To be fair though it was very easy to switch between the two and I'll keep a watch on the AXIS development. This allows your web service clients to be any SOAP client. Richard Taylor New Scientist Developer ----- Original Message ----- From: "Christian Ubbesen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 31, 2002 10:00 PM Subject: Standalone Lucene server > I'm thinking of using Lucene as a general purpose tool in my toolbox, > and therefore use it in non-java-only-environments. > > For instance, I would like to use the search capabilities in one of my > clients NT4/IIS/ASP-environments. > > Since Lucene is essentially a java-library today, I'm wondering if > anyone have wrapped it up as standalone search engine with some neat > interface (keywords: TCP, HTTP, XML-RPC, SOAP, whatever really...)? > > Otherwise I suppose it could be an idea to create this sort of > container. > > > Christian > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
