Hi Martin, what exactly do you mean by connecting the client SEARCH to server SEARCH? The client parses the response in the same way as the response to a PROPFIND method. That means you get the URLs of the hits and their associated properties.
The "problem" with the client SEARCH is that you have to generate the request body yourself from scratch. This of course gives you the freedom to use any search grammar the server supports. If you have an idea how to simplify the generation of the request body, I would be glad to contribute implementations for different search grammars. Regards, Ingo > Hi Stefano, > > I never used slide client nor know its sources. I think there is work to be > done connecting the client SEARCH to server SEARCH. AFAIK the SEARCH in > client somehow filters the result of a PROPFIND. > > Is there anybody who can volunteer in mapping the client SEARCH to server > SEARCH? > > Regards, > Martin > > -----Original Message----- > From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 26. November 2003 14:50 > To: Slide Developers Mailing List > Subject: Re: Problems with DASL basic search > > > > On 26 Nov 2003, at 14:12, Wallmer, Martin wrote: > > > Hi Stefano, > > > > do you use the server side implementation of DASL? > > Martin, > > my setup is currently > > cocoon DASL transformer -> Slide Client library -(http)-> Slide > server -> TX stores > > Both Cocoon and Slide are running on the same machine (macosx 10.3.1), > on two different jetty instances on two different ports. > > I am using the DASL implementation that comes with Slide, > BasicSearchImpl I think it's the class that implements it. > > Did you even experience the same problems I mentioned previously? or do > you have any suggestions on something that I might be doing wrong? > > TIA > > -- > Stefano. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
