URI Handlers

What about adding a facility to register URI handlers in
PresentationServer? For instance one could write a handler for the
"scope:" scheme that given the URL "scope:session:resources" would
return the document stored by the scope serializer in the session with
the "resources" key.

Use case: i18n in XForms; when the end-user logs in, put an XML
document containing the resources for his language in the session
under the "resources", then expose this document to XForms with
<xforms:instance src="scope:session:resources" id="resources"/> in
each view. The downside of using this special schema for i18n is that
this would not be necessarily portable to another XForms engine.
Comments?

Alex
--
Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Le lundi 14 novembre 2005 à 10:39 -0800, Alessandro Vernet a écrit : I am not sure that this is a good idea in this specific case if that can
compromise the interoperability of the forms, but that looks like
something that could be useful within pipelines and transformations
(which are already heavily coupled to the OPS features and
architecture).

That makes me think that I am not very clear on how protocols and
resource managers interact (now and if you were implementing this
feature).

Are protocols "below" resource managers meaning that each resource
manager must provide an implementation of each protocol or "above" the
resource managers meaning that a new protocol would eventually rely on
the resource managers?

Eric

--
Weblog:
                 http://eric.van-der-vlist.com/blog?t=category&a=English
------------------------------------------------------------------------
Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
(ISO) RELAX NG   ISBN:0-596-00421-4 http://oreilly.com/catalog/relax
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Eric van der Vlist wrote: Well, yes and no, the XPL engine is fairly well decoupled. The real
specific OPS things here are really the PFC, and individual processors
used by XPL.

> That makes me think that I am not very clear on how protocols and
> resource managers interact (now and if you were implementing this
> feature).
>
> Are protocols "below" resource managers meaning that each resource
> manager must provide an implementation of each protocol or "above" the
> resource managers meaning that a new protocol would eventually rely on
> the resource managers?

A resource manager is nothing but an implementation of the "oxf:"
protocol. So the "oxf:" protocol is above the resource managers. The
only protocol we have is "input:", and it is handled quite separately
the the XPL implementation.

-Erik



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

On 11/14/05, Eric van der Vlist <[hidden email]> wrote: OK - that makes sense. As I also think that XForms interoperability is
very important, let's forget about this idea of using a special scheme
in this use case.

Alex
--
Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Le mardi 15 novembre 2005 à 18:50 -0800, Alessandro Vernet a écrit : There might be other cases where that could be interesting...

That would make it easy to support standard URI scheme (mailto:, ldap:
ftp: and other come to mind).

If you take the example of the ldap: scheme, one could then support it
by connecting the scheme to a pipeline that would use the existing LDAP
processor.

We could also use it to implement application specific URI scheme that
would call pipelines.

For instance, if you have Lucene indexes, you could implement a lucene:
scheme that would return search results.

All that could be made available in pipelines but also in XSLT
transformations where they would be very handy.

I think I have already mentioned on this list that Cocoon has a very
handy cocoon: scheme that invokes pipelines defined in the sitemap.

Implementing URI handlers could be seen as a generalization of this
concept.

My 0.02 €.

Eric

--
Freelance consulting and training.
                                            http://dyomedea.com/english/
------------------------------------------------------------------------
Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
(ISO) RELAX NG   ISBN:0-596-00421-4 http://oreilly.com/catalog/relax
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

On 11/16/05, Eric van der Vlist <[hidden email]> wrote:
> [...]
> Implementing URI handlers could be seen as a generalization of this
> concept.

I concur. Any taker for implementing something along those lines? ;)

Alex
--
Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Le mercredi 16 novembre 2005 à 00:35 -0800, Alessandro Vernet a écrit :
> On 11/16/05, Eric van der Vlist <[hidden email]> wrote:
> > [...]
> > Implementing URI handlers could be seen as a generalization of this
> > concept.
>
> I concur. Any taker for implementing something along those lines? ;)

I'd love to if I had some free time... unless I could find someone
willing to sponsor that work ;-) ???

Eric
Freelance consulting and training.
                                            http://dyomedea.com/english/
------------------------------------------------------------------------
Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
(ISO) RELAX NG   ISBN:0-596-00421-4 http://oreilly.com/catalog/relax
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

On 11/16/05, Eric van der Vlist <[hidden email]> wrote:
> I'd love to if I had some free time... unless I could find someone
> willing to sponsor that work ;-) ???

:-D

Alex
--
Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws