Regarding the CR ... I'm not sure. Yes, if editing is allowed then versioning seems necessary. The CR also now has some Tcl API hooks that makes loading of content concise and easy at the client package end, and of course has the user-configurable filesystem vs. database option for large content. So ... if image or similar attachments are allowed I think I'd argue for the CR just to avoid duplication of effort.
<p>
I think it is also reasonable to argue that in the future the CR should be able to support versionable and non-versionable content. For instance I don't see any reason why image attachments to comments need to be versionable ...
<p>The reason why folks argue against the use of the CR and sometimes objects is because of the perceived pain, misery and potential scalablity issues associated with them.
<p>I think we really need to give serious thought to making the CR, in particular, feel less like an overkill solution ...
