Hi thomas,
I'm trying to integrate your listener, but i do not know where to put
the classes you provided - i assumed they should go into the shared
module, but they try to import classes from the server module
(org.apache.slide.webdav.*), and so they do not compile.
thomas
Le 8 févr. 06 à 09:26, Thomas Bellembois a écrit :
I would like to add the quota listener I have sent to bugzilla.
Thomas
--
......-=( Thomas Bellembois )=-......
CRI - University of Rennes 1 (France)
.....................................
Darren Hartford a écrit :
Just curious, what is the limiting factor that prevents some of these
great ideas, patches, and improvements from occuring?
Max Pfingsthorn (Below)
Fabrice
http://www.mail-archive.com/slide-dev@jakarta.apache.org/
msg15053.html
Robert http://sourceforge.net/projects/webdav-servlet
Daniel http://marc.theaimsgroup.com/?l=slide-
dev&m=113464532806849&w=2
And many, many others available as patches in bugzilla and scattered
throught the mailing list. If it's lack of people to simply apply the
patches and test, I can help out with that (if tests are provided)
- I'm
not a committer as I'm limited in time and the learning curve of the
project, but patch testing is relatively straightforward. If the
lack
of tests is the problem, maybe write up a document to let
non-apache-contributors know how to best make sure their patches get
approved?
I've seen quite a few enchancements and ideas throughout the
history of
this project, and unfortunately some of them may have disappeared.
How
can *I* help make it easier for these ideas, patches, and
improvements
to move forward?
-D
-----Original Message-----
From: Max Pfingsthorn [mailto:[EMAIL PROTECTED] Sent:
Monday, February 06, 2006 7:04 AM
To: slide-dev@jakarta.apache.org
Subject: 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
-------------------------------------------------------------
[EMAIL PROTECTED] / www.hippo.nl
-------------------------------------------------------------
--------------------------------------------------------------------
-
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]
