Hi Tyler,
I looked in the DB and noticed that the "application-xhtml" code is stored in and upon update the version are stored. Is there a way to prevent versioning globally or per field? How can you access the
No, there isn't, currently. Versioning is present by default and we shipped the CMF with that inside with the plan to make it configurable later. That hasn't happened yet. Also, to retrieve the older versioned content there is currently no easy way. The plan is to develop a JSR-170 compliant query language, but that hasn't happened yet either. These are perfect places to contribute to RIFE! ;-)
versions store in the CMF? If you're going to store version info would it be better to store diff / xdiff (for bins) info instead? I understand it could be more processor intensive, but maybe it could be an option. For binary files, an xdiff on a 5 meg file could be 200 bytes or less, a great savings over 5 megs. Obviously it would have to "patch" the files when they're retrieved, but with caching and the option to "merge" versions (patch them and store back in DB as final result) it would make for a huge space savings without much of a hit on performance.
I totally agree and ideally it would have to at least be an option, we didn't implement this from the start since it doesn't add much functionality-wise and totally makes sense as 'later optimization'. Do you know of a pure-Java xdiff library?
Best regards, Geert -- Geert Bevin Uwyn bvba "Use what you need" Avenue de Scailmont 34 http://www.uwyn.com 7170 Manage, Belgium gbevin[remove] at uwyn dot com Tel +32 64 84 80 03 PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
