[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: URI Design

• To: "M. David Peterson" <m.david.x2x2x@g...>
• Subject: Re: URI Design
• From: Alan Gutierrez <alan-xml-dev@e...>
• Date: Thu, 21 Apr 2005 14:45:01 -0400
• Cc: Philippe Poulard <Philippe.Poulard@s...>, xml-dev@l...
• In-reply-to: <f8da4eba05042111143945a919@m...>
• Mail-followup-to: "M. David Peterson" <m.david.x2x2x@g...>,Philippe Poulard <Philippe.Poulard@s...>,xml-dev@l...
• References: <20050421152930.GE29144@m...> <4267D480.8070406@s...> <20050421173716.GG29144@m...> <f8da4eba05042111143945a919@m...>
• User-agent: Mutt/1.4.1i

* M. David Peterson <m.david.x2x2x@g...> [2005-04-21 14:27]:
> Alan, out of curiosity have you spent any time studying Norman Walsh's
> SXPipe project?
> 
> from the first paragraph of http://norman.walsh.name/2004/06/20/sxpipe:
> 
> "SXPipe is a language for building Simple XML Pipelines and a Java
> toolkit that implements it. This is hardly a new idea; a quick web
> search will turn up a number of similar projects. I've written
> elsewhere about why I did it and why I think pipelines are important.
> This essay just describes SXPipe."

    Yup. Relay/Varsity is a little more advanced that SXPipe. SXPipe, IIRC,
    moves documents from one process to the next, while Relay will
    link streams to streams, without materialization. It will
    materialize documents as needed, for an XSLT processor for example.

    Norman can correct me, but I think SXPipe was a proof of
    concept, and he left it at that stage.
    
    Relay/Varsity includes caching of documents, caching of
    partially configured processors (i.e. compiled XSLT transforms),
    and a straight-forward dependency mechanism, that cause
    dependenices to be inherited from cached documents, and across
    pipelines.

    Relay/Varisty is much smaller than Cocoon, and has far fewer
    dependencies. It is easy to add a processor to Relay by
    implementing a few well defined interfaces. Confiugration via
    the Varisty container is done using constructor or setter
    injection, specified in an XML file. Caching is pretty much
    automatic, as are dependencies, if you use stock protocols.

    Can't compare to Obreon OXF, since I've not worked with it. Last
    I checked it was proprietary, but it turns out they released it
    open souce back in August.

--
Alan Gutierrez - alan@e...
    - http://engrm.com/blogometer/index.html
    - http://engrm.com/blogometer/rss.2.0.xml

• Follow-Ups:
  • Re: URI Design
    • From: "M. David Peterson" <m.david.x2x2x@g...>

• References:
  • URI Design
    • From: Alan Gutierrez <alan-xml-dev@e...>
  • Re: URI Design
    • From: Philippe Poulard <Philippe.Poulard@s...>
  • Re: URI Design
    • From: Alan Gutierrez <alan-xml-dev@e...>
  • Re: URI Design
    • From: "M. David Peterson" <m.david.x2x2x@g...>

• Prev by Date: Re: URI Design
• Next by Date: RE: extract the value attribute of a node in a xml file.
• Previous by thread: Re: URI Design
• Next by thread: Re: URI Design
• Index(es):
  • Date
  • Thread