Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Subject: Re: [VFS] questions and suggestions
From: Simon Kitching <skitching@apache.org>
Reply-To: skitching@apache.org
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
In-Reply-To: <4281D934.1020909@ops.co.at>
References: <4280E925.8070101@sophia.inria.fr> <4280F2B9.5020008@ops.co.at>
	 <4281C805.4030207@sophia.inria.fr>  <4281D934.1020909@ops.co.at>
Content-Type: text/plain
Date: Wed, 11 May 2005 22:14:47 +1200
Message-Id: <1115806487.3837.65.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Wed, 2005-05-11 at 12:06 +0200, Mario Ivankovits wrote:
> >>> Suggestion : adding a capability to deal with I/O services
> >> Or implement your own (virtual) directory called "services"?
> >> eg
> >> xmldb://host/services/service_name?param=value&param=value
> > I don't like this solution because :
> > -it's a hack, I prefer more formal solutions ; the XML:DB spec offers 
> > specific means to get a service, not arbitrary URIs
> > -what happened if a real directory called "services" already exists ?
> You could also use a special scheme for this purpose, say: 
> xmldbsvc://host/service_name/......

Just a thought: mapping a directory to a "service" looks rather like a
linux "mount". Or even more like a HURD "translator".

Regards,

Simon


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