> are we interested in exposing the _operation_ of the repository (current JMS > function) to a growing suite of external services, or exposing _the evolving > state_ (Steve's new-school thinking) of the repository? Can we think of any > use cases for exposing streams of operations that can't be supported by > exposing streams of state-changes?
I tend to naturally think in terms of state changes, and believe it is generally more straightforward/flexible. Imagine purgeRelationship() vs modifyDatastream(RELS-EXT-minus-relationship)). Both would have exactly the same effect on system state*. I would think that only some sort of logging/auditing/statistics/journaling type of service would care which method particular was used. -Aaron * Actually, I'm not sure about that. The AUDIT datastream might be different. ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
