That is a shame.  I just don't have time to set up slide 2.  

Any ideas on how I can PROPFIND all documents in the store easily, in a
loop?  That's all I need.

Many thanks

Stuart


-----Original Message-----
From: Wallmer, Martin [mailto:[EMAIL PROTECTED] 
Sent: 04 September 2003 14:55
To: 'Slide Users Mailing List'
Subject: RE: RE: Search facility - document iterator

Hi,

strength of DASL is search on properties. You will need slide 2 to use DASL.

Regards,
Martin

-----Original Message-----
From: stuart macpherson [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 4. September 2003 15:41
To: Slide Users Mailing List
Subject: Re: RE: Search facility - document iterator


Many thanks for your prompt replies.  I can't find anything to do with DASL
in my version of slide (latest production release, i.e. 1.0.16), and I don't
have time to be compiling migrating to Slide2.  Can I still use DASL?  DASL
is definitely something I will talk about in my report, but my simple search
mechanism is based on properties, not actual text content (at the moment).
Does DASL support this kind of simplicity?

I have nearly constructed my 'PROPFIND > compare > score' system, all I
really need is some hints about how I can iterate through the entire store.
If DASL can do this, and I am able to get it without too much time-wasting
then cool.  Otherwise, does anyone have some hints about parent-independent
iteration?

Sorry if I am asking basic questions... I don't think I am alone in being
largely unable to establish what my options are with Slide... the docs and
literature seem to lag so far behind.  I remain enthusiastic however, and I
am nearly finished!

Kind regards
stuart




======================================== 
Message date : Sep 04 2003, 08:14 AM 
>From : Wallmer, Martin 
To : 'Slide Users Mailing List' 
Copy to : 
Subject : RE: Search facility - document iterator 
Hi, 

I'd suggest to use DASL. There is a generic implementation within the slide 
kernel. 

Regards, 
Martin 

-----Original Message----- 
From: stuart macpherson [mailto:[EMAIL PROTECTED] 
Sent: Donnerstag, 4. September 2003 00:24 
To: [EMAIL PROTECTED] 
Subject: Search facility - document iterator 


I am implementing a search facility for my doc store, and I would like to 
know what are people's thoughts on the best way to iterate through the store

(doing PROPFINDs on each doc as it goes). Obviously you can check if each 
resource is a collection, and tif so, then enumerate its children (as the 
webdav servlet does when doing directory listings)... but I don't just want 
to look at the children of one collection, I want to look at every 
(non-collection) node i.e. document. Is there some kind of 'depth' flag... 
or some other way of basically saying 

while (moreDocsInStore) { 
String currentResource = (String) resources.nextElement(); 

while (moreQueryKeys) { 
String prop = currentResource.getProperty(foo); 
//do some checks against query keys, and give it a hit score 
} 
} 

I know the logic to do everything except the iteration thu each doc 
regardless of its parent. Any help would be much appreciated. 

Regards 
stu 

--------------------------------------------------------------------- 
To unsubscribe, e-mail: [EMAIL PROTECTED] 
For additional commands, e-mail: [EMAIL PROTECTED] 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to