RE: enhancements/fixes for slide 2.1

Hi!

> Hi Max and thanks for the quick reply.

No problem :)

> The optimal solution would of course be if Slide 2.2 would come out  
> sooner than later with your patches...
> However I'm already using some stuff from Hippo actually 
> (extractors)  
> although I hadn't thought about using your custom build of Slide  
> since I thought it was plain old Slide 2.1. : )

Nice to hear that our work is useful to other people as well! :) I believe, we integrated some bugfixes which might not be part of the 2.1 branch yet, but are in bugzilla.

> What stuff from 2.2 have you back ported?

As far as I remember only the Lucene indexing. "Backporting" is maybe a little strong of a word.. I integrated those pieces of code so they are useful to us. I combined the content and properties indexers since both write to the same index for us (less overhead for dasls which query both content and properties) and hardcoded some useful defaults.

> I ask because I have an old  
> snapshot build from Slide head running under our webapplication  
> platform (IdegaWeb) and I'm wondering if your stable build might be  
> better. I need Lucene indexing with DASL working correctly and the  
> triggers/event system...

Hmm, this is a topic for us as well. We are trying to go back to a WAR now, and for now it seems to work even with the use of fortress around slide and the slide servlet. However, it is not tested at all, so maybe it would be a better idea to integrate patches (once I get to put them up as well) into our application slowly.
However, the features you mentioned work very well for us, so you might want to have a closer look. There are also some goodies in the cluster package, like JGroups based notification for zero-conf clustering. We are using it for two of our bigger clients and it's quite well tested.

> Offtopic > One of the guys here at Idega wanted me to ask you 
> also if  
> the Hippo team is considering developing a JCR plugin on top of Slide?

No, we aren't really into JCR too much at the moment. That might change, but by then we might have moved away from slide. I mean, slide works great, but our requirements are growing and slide's rigid data model is starting to become limiting.

Bye!
max