Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 1307 invoked from network); 15 May 2008 15:37:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 May 2008 15:37:54 -0000 Received: (qmail 20993 invoked by uid 500); 15 May 2008 15:37:54 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 20973 invoked by uid 500); 15 May 2008 15:37:54 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 20962 invoked by uid 99); 15 May 2008 15:37:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 May 2008 08:37:54 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [69.25.87.29] (HELO compucredit.com) (69.25.87.29) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 May 2008 15:37:01 +0000 Received: from ([10.24.56.6]) by mail4.compucredit.com with ESMTP id 5503069.75172990; Thu, 15 May 2008 11:36:58 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: Is there a resolver that is not tightly coupled to filesystem semantics? Date: Thu, 15 May 2008 11:36:58 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Is there a resolver that is not tightly coupled to filesystem semantics? Thread-Index: Aci2oYLE0N9OTsooRoauyxDvpwlfCw== From: "Brown, Carlton" To: Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8B6A1.83327B1E" X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C8B6A1.83327B1E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all,=0D=0A =0D=0AAs far as I can see, every documented Ivy resolver requ= ires an=0D=0A element and element, each of which requires s= ome=0D=0Aknowledge of how the repository is laid out=2E This means if I w= ant to=0D=0Are-arrange a popular and heavily used repository, there has to = be a=0D=0Acorresponding change for every ivy-settings=2Exml in the wild tha= t=0D=0Areferences this repository=2E I understand namespaces can help, bu= t even=0D=0Anamespaces are stored in ivy-settings=2Exml and thus suffer fro= m the same=0D=0Aproblem=2E=0D=0A =0D=0AIf we had some sort of resolver that= was completely orthogonal to=0D=0Adirectory layout, this wouldn't be a pro= blem=2E There could be a=0D=0Aresolver whose only non-generic attributes = are a hostname and port=2E=0D=0AThe host would be running some server which= in turn would use ivy to map=0D=0Athose requests to a physical storage imp= lementation (filesystem, dbms)=0D=0Aor maybe even delegate it to a subordin= ate resolver=2E In this way, the=0D=0Aclient would never need to know whi= ch implementation served the request,=0D=0Ait could be just concerned with = getting the content=2E=0D=0A =0D=0ADoes any such resolver exist? Could it = be easily created by extending=0D=0Aabstract resolver and adding the behavi= or, or is there a lot of baked-in=0D=0Afilesystem stuff in there?=0D=0A =0D= =0AThanks,=0D=0ACarlton=0D=0A=0D=0A=0D=0A=0D=0A----------------------------= -------------=0D=0A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=0D=0AThis message contains PRIVILEGED and CONFI= DENTIAL=0D=0Ainformation that is intended only for use by the =0D=0Anamed r= ecipient=2E If you are not the named recipient,=0D=0Aany disclosure, dissem= ination, or action based on =0D=0Athe contents of this message is prohibite= d=2E In such=0D=0Acase please notify us and destroy and delete all =0D=0Aco= pies of this transmission=2E Thank you=2E=0D=0A=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ------_=_NextPart_001_01C8B6A1.83327B1E--