Joseph Kesselman wrote:
One very strong vote in favor. This would also presumably make it easier
to plug in other "translating" output stages, such as my XNI to DTM
builder.... or to set up Elena's revalidating pipeline.
True.
XNI's about data flow from component to component. It should be possible
to treat an XNI-to-whatever stage as just another component. Once the
pipeline is assembled into a configuration it should be controllable at
the pipeline (configuration) level. And for basic reasons of software
architecture hierarchy, it ought to be possible to treat configurations
themselves as components.
That's certainly possible but there's more to a config
than just the document processing pipeline. There's a
lot of infrastructure stuff that is taken care of at
that level. So using a configuration as a stage might
prove to be difficult to implement and clumsy to use.
But it would certainly be useful to be able to deal
with a mini-pipeline as a single component to insert
into the component pipeline.
--
Andy Clark * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
