'content_class' of Field.FileField is OFS.Image.File instead of CMFDefault.File

Hi,

I have the problem that in plone files and images do not go through CMF's 
caching policy manager (e.g.  http://myplone.org/big_file/view goes through 
the caching policy manager, but http://myplone.org/big_file and 
http://myplone.org/big_file/download do not, which means that for the big 
files no caching header can be set easily). 

There is a patch for this at http://www.zope.org/Collectors/CMF/454 
However, this patch does not effect plone, since Archetypes does not use the 
CMFDefault.File implementation for a file but the elementary one provided by 
zope, that is OFS.Image.File (as far as I can see in 
Archetypes.Field.FileField)

Is there any reason for this? Could CMFDefault.File be used instead as 
the 'content_class' for FileField (that is ATFile) in the future? (I tried to 
replace "from OFS.Image import File" with 
"from Products.CMFDefault.File import File" but ended up with 
an 'seek'-Attribute-Error, also I am afraid of side effects)

I thought it would be a good idea to asked here first, before opening a 
feature request.

jens

PS: The same holds somehow true for Images with regards to OFS.Image.Image and 
CMFDefault.Image

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV