[
Lists Home |
Date Index |
Thread Index
]
> I suggest we make one core twist to XML. Lets express the various layers
> to XML parsing in terms of a pipeline and see if it can help us
> accommodate the date typing folk, the binary XML folk etc. without
> throwing out the baby with the bathwater.
Excellent suggestion, Sean! It has the potential to keep everyone happy if
done right.
But not every operation needs to be a separate process in a pipeline (though it
could be). In the example of validation versus schemas, it might be easier to
have one validation process, but have different parameters used to configure
that process (validate structure only, validate structure AND types..etc.).
Modularity has a way of solving such thorny issues, and pipelines are just
another form of modularity.
What is interesting is that this approach is finding favour with the Aspect-
Oriented Programming crowd, where method calls and aspects (interceptors)
are, in a sense, pipelined together dynamically. The architecture of the JBoss
project is an excellent example of such thinking and provides many benefits
and flexibilities.
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com
|
