Hi, Pierre-Yves
When you create an "M" datastream, Fedora stores the content in a separate
location with byte-for-byte accuracy. It stores exactly what you send
without modification. With inline XML (and FOXML in general), the whitespace
(indenting, spaces between attribute values, etc) may be modified by the
object serializer/deserializer. Indeed, when Fedora calculates the checksum
for "X" datastream, it canonicalizes the content before calculating the
checksum so that it may arrive at the same value despite formatting changes
that may have been introduced in the XML serialization or parsing. Since "M"
datastreams are stored as exact bytes and never travel through an XML parser,
Fedora simply calculates the checksum on the bytes without any sort of
manipulation
-Aaron
-----Original Message-----
From: Pierre-Yves JALLUD [mailto:[email protected]]
Sent: Fri 5/15/2009 5:28 AM
To: fedora-commons-developers
Subject: [Fedora-commons-developers] Checksum problem for datastream
Hi all,
I have a problem of checksum for datastreams. If I add a datastream with
a Content Model wich is equal to "M", the checksum I had calculate and
the one fedora-commons calculates are the same. But if I add the same
datastream with a Content Model wich is equal to "X", fedora-commons
finds another checksum.
Is that normal?... I don't see why there is a difference... Is that a
bug or a normal behaviour?
Greetings
Pierre-Yves
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Fedora-commons-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
