enhancements/fixes for slide 2.1

[Max Pfingsthorn <m....@hippo.nl>]

Dear sliders,

I've been developing with slide for a long long time and our webdav server is almost a distinct fork of slide already. We've been working with patches to keep somewhat in sync with the slide 2.1 codebase, but it is getting too clumsy.

Some of the work I have done here, which we would like to contribute back to slide, is:

- lucene-based DASLs are sorted within lucene to make it even faster, and some other optimizations, like allowing DAV:limit without DAV:orderby since we found out that the real bottleneck is generating the data for all resources in a multi-status response. now DASLs are around a factor of 10 faster than the 'old' SQL way.
(I just saw in the logs that Daniel Florey committed my initial patch for this, thanks! That one didn't include the optimizations above, though.)

- added support for multiple search scopes and the slide:exclude option for the lucene backed DASLs

- jms notification of changes to an external system. we have been using it for a long time for invalidating the cache of our cocoon websites using cocoon's event cache block.

- a replication event handler which replicates webdav methods to a number of other hosts, configurable per path per namespace

- extractors (content and property) for the OpenDocument format (any type), and some general ones for xml

- a cache manager web interface to have some rudimentary control over the caches in slide

I would really like to contribute this to slide itself (FYI, I already signed a CLA, I'm a committer for Cocoon), but I haven't seen many commits lately, and merging something like this might be some work.. I just wouldn't want the patches to get dusty in bugzilla again for a few months, it might then be easier to dump my working copy in our svn here.

A working version with these features is downloadable from www.hippocms.org. It is called "Hippo Repository", the backend for our cms. For svn access, click on "Getting the Code", a build is available as a zip under "Getting Started". That one is slightly outdated though, I'm hoping to upload a new build tomorrow.

Best regards,

Max Pfingsthorn

Hippo  

Oosteinde 11
1017WT Amsterdam
The Netherlands
Tel  +31 (0)20 5224466
-------------------------------------------------------------
m.pfingsthorn@hippo.nl / www.hippo.nl
-------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org

Re: AW: enhancements/fixes for slide 2.1

[Andrew Savory <an...@luminas.co.uk>]

Hi,

On 11 Feb 2006, at 12:33, Daniel Florey wrote:

> Fromm y point of view it would be great if you would become a slide
> committer and could add patches to the sources directly. If you are
> interested, I would start a voting thread on this mailing list.

I think some new blood would be useful - and Max has already proved  
to be a valuable committer over in cocoon land.

So here's my non-binding +1 for you starting a vote ;-)

Andrew.

--
Andrew Savory, Managing Director, Luminas Limited
Tel: +44 (0)870 741 6658  Fax: +44 (0)700 598 1135
Web: http://www.luminas.co.uk/
Orixo alliance: http://www.orixo.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org

AW: enhancements/fixes for slide 2.1

[Daniel Florey <da...@web.de>]

Hi Hippo!
Fromm y point of view it would be great if you would become a slide
committer and could add patches to the sources directly. If you are
interested, I would start a voting thread on this mailing list.
I think most of your patches are very helpful for the slide community.
One comment to your patches regarding the lucene-based search:
If you use lucene directly to limit the results this might cause some
trouble if you are using acl's. The acl's get evaluated after slide
retrieves the search result from lucene. If you for example specify a limit
of 10 results and the user executing the DASL-request has no permissions to
read half of them, he would only get 5 files even if he specified to get 10.
So it would be very helpful to have a configurable switch to select if you
want to have a fast system (with the risk of wrong number of results) or a
slower search with correct results.
Why have you used JMS to notify cocoon? Have you had a look at the
Notification abilities in the slide webdavlib?

Cheers,
Daniel


> -----Ursprüngliche Nachricht-----
> Von: slide-dev-return-16893-daniel.florey=web.de@jakarta.apache.org
> [mailto:slide-dev-return-16893-daniel.florey=web.de@jakarta.apache.org] Im
> Auftrag von Max Pfingsthorn
> Gesendet: Montag, 6. Februar 2006 12:04
> An: slide-dev@jakarta.apache.org
> Betreff: enhancements/fixes for slide 2.1
> 
> Dear sliders,
> 
> I've been developing with slide for a long long time and our webdav server
> is almost a distinct fork of slide already. We've been working with
> patches to keep somewhat in sync with the slide 2.1 codebase, but it is
> getting too clumsy.
> 
> Some of the work I have done here, which we would like to contribute back
> to slide, is:
> 
> - lucene-based DASLs are sorted within lucene to make it even faster, and
> some other optimizations, like allowing DAV:limit without DAV:orderby
> since we found out that the real bottleneck is generating the data for all
> resources in a multi-status response. now DASLs are around a factor of 10
> faster than the 'old' SQL way.
> (I just saw in the logs that Daniel Florey committed my initial patch for
> this, thanks! That one didn't include the optimizations above, though.)
> 
> - added support for multiple search scopes and the slide:exclude option
> for the lucene backed DASLs
> 
> - jms notification of changes to an external system. we have been using it
> for a long time for invalidating the cache of our cocoon websites using
> cocoon's event cache block.
> 
> - a replication event handler which replicates webdav methods to a number
> of other hosts, configurable per path per namespace
> 
> - extractors (content and property) for the OpenDocument format (any
type),
> and some general ones for xml
> 
> - a cache manager web interface to have some rudimentary control over the
> caches in slide
> 
> I would really like to contribute this to slide itself (FYI, I already
> signed a CLA, I'm a committer for Cocoon), but I haven't seen many commits
> lately, and merging something like this might be some work.. I just
> wouldn't want the patches to get dusty in bugzilla again for a few months,
> it might then be easier to dump my working copy in our svn here.
> 
> A working version with these features is downloadable from
> www.hippocms.org. It is called "Hippo Repository", the backend for our
cms.
> For svn access, click on "Getting the Code", a build is available as a zip
> under "Getting Started". That one is slightly outdated though, I'm hoping
> to upload a new build tomorrow.
> 
> Best regards,
> 
> Max Pfingsthorn
> 
> Hippo
> 
> Oosteinde 11
> 1017WT Amsterdam
> The Netherlands
> Tel  +31 (0)20 5224466
> -------------------------------------------------------------
> m.pfingsthorn@hippo.nl / www.hippo.nl
> -------------------------------------------------------------
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org