kelvin goodson wrote:
[snip]
With regards to sharing change histories, I imagine the primary use case
for change histories is when you give a give a modified graph back to the
"same" DAS for writing back to the original source. So I in terms of
cross
language interoperability I would extrapolate that the scenario we
would be
supporting would be that of fairly tightly coupled DAS
implementations, all
accessing the same source. I may be wrong, but It doesn't sound like a
frequently encountered scenario, so whilst it sounds like goodness, it
wouldn't be at the top of my priority list.
[snip]
I have also not seen many interop scenarios requiring cooperation
between two different DAS implementations. The only one that comes to
mind is reading from one database and writing to another. This would be
very cool, especially if the two DAS implementations were in different
languages(C++, Java, PHP, Ruby), but I doubt that this scenario will be
common.
I think a more frequent interop scenario will involve reading data from
a data source and shipping it to some remote engine for processing. The
modified graph would be shipped back to the originating DAS and the
changes reflected to the originating data source. The remote engine
could be implemented in another language or, if it is the same language,
it could be using a different implementation of SDO.
