On Sun, 27 May 2001, Berin Loritsch wrote:
> The context and resource protocols should match the semantics for
> file and jar:
>
> context://relative/path/from/context/root
> resource://path/to/packaged/resource
why don't we go ahead and enumerate all of the extra protocols recognized
by c2 and their semantics, and stick them in a document for reference.
i'll take a stab:
context urls point to xml resource pipelines relative to the root of the
current sitemap. the same context url in two seperate sitemaps can resolve
to two seperate pipelines. format: context://{path}
cocoon urls point to xml resource pipelines relative to the root of the
current webapp. the same cocoon url in two seperate sitemaps always
resolves to the same resource pipeline. format: cocoon://{path}.
resouce urls point to binary resources that are accessible via the jvm
classloader. typically, these are data files included in a jar file.
format: resource://{path}.
is this correct?
is this as we would like it to be?
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
