This would allow storing arbitrary binary objects and make it easier to handle them in a consisntent way. For example, file-storage could be fixed.
We already have acs-subsite/www/file.vuh which will allow downloading an file stored in the content repository consistently.
This will allow us to deal with files uploaded with the oacs-attach widget for xinha or tinymce to be correctly handled and indexed for search etc.
The problem is if you enable search of generic content_revisions you could get any object which may or may not be interesting or searchable.
From years of experience it has occured to me that only subtypes of content revision should actually implement the search callbacks (or service contracts in legacy installs). There should be a way to create a non-searchable content_revision.