Original Message From: "John Cowan"
> All that parsing and unparsing would be expensive:
That was certainly one of my concerns, does it scale (unscale?!) to the
tiny? If the cost of serialization is small compared to the number of cores
you can throw at a problem then it might cost in. These days that's
probably an accessment you have to make on a daily basis!
> you might as well deal
> in binary immutable objects instead. But otherwise the idea is good and
> has been in use for decades (Unix pipelines being the best-known example).
> The key is to share nothing except immutable objects.
I was thinking the act of serialization could be used to enforce the
immutability aspects and reduce the changes of unintentionally getting
access to 'foreign' mutating state.
> See Flow-Based Programming, a framework based on passing around immutable
> packets between components (there are Java, C#, and C++ versions) at
> http://www.jpaulmorrison.com/fbp/ .
Will do, Thanks.
Pete Cordell
Codalogic Ltd
Interface XML to C++ the easy way using C++ XML
data binding to convert XSD schemas to C++ classes.
Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
for more info