-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 29, 2012, at 3:10 PM, Chris Wilper wrote:

>  Going after a smaller level of granularity (e.g. the datastream) would be a 
> different challenge which, if folks want to go down that road as a thought 
> exercise, I'm happy, but in my mind there's already a pretty easy answer for 
> anyone who has use cases that really provoke 
> different-datastream-same-object-update concurrency: Use atomistic content 
> modeling

Hm. I'm not sure whether I agree or disagree with you, Chris. {grin}

Couldn't this be construed as forcing people to conflate two sets of values: 
accuracy in domain modeling and policies around the curation of content? If my 
identities really are well-chosen to model my domain, having to break them 
apart to satisfy operational concerns feels wrong. There might also be scaling 
concerns: in an example of objects that contains both metadata and data, which 
might be subject to different constraints of transactionality, breaking one or 
the other out into a separate object could instantly double the number of 
objects in the repo.

I do see your point, and I accept that Fedora can't offer all things to all 
people, but I wonder if we can find a way to leave the door open for 
"other-than-object" atomicity, perhaps without building it out immediately?

> FedoraStoreSession session = fedoraStore.getSession();
> <snipped>
>  session.close();
> }
> 
> Now, unless someone has gone a bit wild with datastreams, 
> FedoraObject.copy(), a "deep" copy, is going to be fairly cheap on its
> own. But what do we actually do with managed datastream content?

I'm not sure I understand the question... wouldn't it be a pointer and nothing 
more? If you provide access to it through the FedoraObject object, we can still 
treat an URI as a value. And if someone creates a new URI (e.g. by offering new 
content in a modifyByValue) then you can change the URI to the URI of the new 
content (value-for-value). But perhaps I'm misunderstanding the question... 
especially because I'm not sure I understand what "deep" copy means-- a copy 
wherein all datastream content is also duplicated?

- ---
A. Soroka
Software & Systems Engineering :: Online Library Environment
the University of Virginia Library

> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJPdLxKAAoJEATpPYSyaoIkkmMH/1oqHFzljZT9/Tq17XhyKdHv
wlyZOx0uMfRx+JepTI2xh7CTHigtxTemKLtIuc3EK/XtU1M+0Tb34vez2kfjOO6C
TM50BtU/7dT2MQmg6zZdhCCh15i7pifL97DrxzrzHYbuv1jKvV4bsOGBDJsM67iD
ZAjZSvOZlJZ8ob18fvGuMttfZ29K74gz0wHeEMuyTG0s5WPfiy/q/Ft2X3+Hc/CB
LE1o3tM0yPyi7mmEhMGYMnkfXjKQckVCYJ0DkJwRU0JeVog/UlM1Orl0f2gxpDPW
xmWpSHfFMnDDM6cY0Jlns+err/PI4bJ5qU5NmM6keDgMII1LwFgXrpOyrVUYzjA=
=0tNK
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Fedora-commons-developers mailing list
Fedora-commons-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers

Reply via email to