Create a new account
All that great family of people interested in pipelines might be interested in this new W3C Note. It's just a Note (ie early alpha) and looks like it has a few faults, but I think it's interesting.
It got me thinking that what we really need is an XML format for declaring pipelines, so that XML::Pipeline->create can instantiate all of the code needed to do the work, without actually writing Perl code. Alternatively, XML::Pipeline->compile could take an XML description and produce a module that does what the p
A couple of major differences between X::S::M and the XPipe stuff are that XPipe seems to be a specialized make/ant thing and that it's a lot higher level than X::S::M. X::S::M is meant to make it easy to connect and manage SAX processors, while XPipe wants to manage the overall transformation process.
I'd like to see X::S::M grow some XPipe like
For example, I'd expect XPipe to handle the case where data is coming in from DBI and into a SAX head conversion, passing through some filters, being converted into a DOM tree, munged and then ferried through an XSLT transform, to be re-serialized as SAX events to be filtered again and output thorough a tail conversion into another DBI connection.
It does seems like XML::Generator::FromDBI and XML::Handler::ToDBI would be handy modules. I've written SAX modules before that store and retrieve XML as event lists (with unnecessary events omitted on store and recreated on retreival), so I know it's not too difficult. Kind of like a DBIx
Get More Comments