> Hi,
>
> Can somebody explain how Slide interpetes the mapping URIs to Namespaces
> Nodes and further to URLs.
>
> Say, RFC 2396 defines URI like: "schema://server(authority)/path/query".
And
> URI in RFC 2518 is considered just as a name that is supposed to map to
the
> Resource Model Namespace and then further to a physical location with
access
> protocol defined(URL).
>
> Leaving the query part aside, schema "dav:" can define the DAV Namespace.
It
> would be great to directly map the path part to the collection-resource
> elements in a Namespace based on the "/" divider. But what about the
server
> part that can include the port part as well?
>
> How does Slide map the server/path parts into Namespace hierarchy, like
> "dav://a.com/files"?
>
> /files attaches to the root "/" and defines a Collection, but where does
> a.com go?
>
> A servlet can consume the server part, but a general content management
> system is supposed to work with a full URI.
All uris manipulated by Slide are relative to a namespace, so the full URL
equivalent is :
slide://machine_name/namespace_name/url
Of course, there is no Slide proprietary protocol. Instead we use WebDAV
(which is just a set of new HTTP methods, so the protocol is HTTP), and the
URL is dependent on the mapping and context name of the WebDAV servlet.
Remy
