Geoff Howard [mailto:[EMAIL PROTECTED] wrote:
On 12/20/05, Max Pfingsthorn [EMAIL PROTECTED] wrote:
On another note: I need the eventcaching block for webdav, but
that one only needs jms in one class, and databases in the
samples. So, I'll work on the dependency issue there
On 1/4/06, Max Pfingsthorn [EMAIL PROTECTED] wrote:
Geoff Howard [mailto:[EMAIL PROTECTED] wrote:
On 12/20/05, Max Pfingsthorn [EMAIL PROTECTED] wrote:
On another note: I need the eventcaching block for webdav, but
that one only needs jms in one class, and databases in the
On 12/20/05, Max Pfingsthorn [EMAIL PROTECTED] wrote:
On another note: I need the eventcaching block for webdav, but
that one only needs jms in one class, and databases in the
samples. So, I'll work on the dependency issue there instead of
in the webdav block directly.
...
-Original Message-
From: Max Pfingsthorn
Sent: Wednesday, December 21, 2005 12:04
To: dev@cocoon.apache.org
Subject: RE: rejuvenating the webdav block
Hi!
Can you show me a block (or some sort of description of how
it should look like) so I can rearrange the structure
accordingly? I
Message-
From: Gianugo Rabellino [mailto:[EMAIL PROTECTED]
Sent: Friday, December 16, 2005 12:48
To: dev@cocoon.apache.org
Subject: Re: rejuvenating the webdav block
On 12/16/05, Max Pfingsthorn [EMAIL PROTECTED] wrote:
Dear Cocooners,
I would like to start rejuventating the webdav
* Max Pfingsthorn:
- Currently, there is no way to access older revisions of a
source, you have to guess
In the WebDAV jargon, this is the REPORT method. Maybe we can
call that getRevisionHistory() to be protocol-independant?
So, seeing the current shortcomings and inadequacies
Jean-Baptiste Quenot [mailto:[EMAIL PROTECTED] wrote:
* Max Pfingsthorn:
- Currently, there is no way to access older revisions of a
source, you have to guess
In the WebDAV jargon, this is the REPORT method. Maybe we can
call that getRevisionHistory() to be
Max Pfingsthorn wrote:
Dear Cocooners,
I would like to start rejuventating the webdav block. We have some code to do
cool things like event caching and a more general purpose WebDAVTransformer
(which can also do propfind, proppatch, etc).
If you know anything you would like to see in the
@cocoon.apache.org
Subject: Re: rejuvenating the webdav block
* Max Pfingsthorn:
I would like to start rejuventating the webdav block. We have
some code to do cool things like event caching and a more
general purpose WebDAVTransformer (which can also do propfind,
proppatch, etc
Since you're looking into it, can you also take a shot at
http://issues.apache.org/jira/browse/COCOON-1696
It's just a matter of copying sources in different directories and
modifying descriptors slightly...
Pier
On 16 Dec 2005, at 10:42, Max Pfingsthorn wrote:
Dear Cocooners,
I
Dear Cocooners,
I would like to start rejuventating the webdav block. We have some code to do
cool things like event caching and a more general purpose WebDAVTransformer
(which can also do propfind, proppatch, etc).
If you know anything you would like to see in the webdav block, please say so
On 12/16/05, Max Pfingsthorn [EMAIL PROTECTED] wrote:
Dear Cocooners,
I would like to start rejuventating the webdav block. We have some code to do
cool things like event caching and a more general purpose WebDAVTransformer
(which can also do propfind, proppatch, etc).
If you know
* Max Pfingsthorn:
I would like to start rejuventating the webdav block. We have
some code to do cool things like event caching and a more
general purpose WebDAVTransformer (which can also do propfind,
proppatch, etc).
If you know anything you would like to see in the webdav
13 matches
Mail list logo
