Return-Path: 
 <dev-return-47166-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 28881 invoked from network); 1 Sep 2003 09:22:37 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 1 Sep 2003 09:22:37 -0000
Received: (qmail 21041 invoked by uid 500); 1 Sep 2003 09:21:50 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 20987 invoked by uid 500); 1 Sep 2003 09:21:50 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 20947 invoked from network); 1 Sep 2003 09:21:49 -0000
Received: from unknown (HELO confixx.bestiole.ch) (66.111.0.243)
  by daedalus.apache.org with SMTP; 1 Sep 2003 09:21:49 -0000
Received: from codeconsult.ch ([62.220.137.25])
	by confixx.bestiole.ch (8.11.6/8.11.6) with ESMTP id h819LEP21784
	for <dev@cocoon.apache.org>; Mon, 1 Sep 2003 11:21:14 +0200
Date: Mon, 1 Sep 2003 11:21:16 +0200
Subject: Re: WebDAV proxy available
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Bertrand Delacretaz <bdelacretaz@codeconsult.ch>
To: dev@cocoon.apache.org
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <3F5309EE.90802@apache.org>
Message-Id: <A34F2DE2-DC5D-11D7-8B14-000393CFE402@codeconsult.ch>
X-Mailer: Apple Mail (2.552)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Le Lundi, 1 sep 2003, =E0 10:57 Europe/Zurich, Gianugo Rabellino a =E9crit=
 :

> ...The hooks IMO should be in the pipeline actually....

sounds good.

>   <match type=3D"request-method" pattern=3D"PUT">
>     <act type=3D"syncmetadatadb">
>      <generate type=3D"webdavproxy">
>         <parameter name=3D"url" value=3D"http://whatever/dav/{../1}"/
>      </generate>
>      <serialize/>
>     </act>
>   </match>

I think the webdav backend is much more likely to fail than syncmetadb=20=

in such cases (due to insufficient authorizations etc), which would=20
create inconsistencies between the backend and meta db if the sync is=20
done with actions.

It might be better to sync the meta db based on the results of the=20
backend, in which case I'd go for a Transformer to post-process the PUT=20=

result from the backend, feeding sql code to a downstream=20
SQLTransformer:

PUT operation:
WebdavProxy -> DaslTransformer -> SQLTransformer

I haven't studied all details yet, but hopefully I'm not too far from=20
reality ;-)

-Bertrand