Supporting FileField fields

@arhak :

a filefield has several properties: filesystem path, timestamp, filesize, etc, etc
I have support for multi-dimensional properties, e.g. textfields with input format, and they are considered equals "if and only if" they match in both: the text and the format (nevertheless, until now I have no idea on how to visualize a format change which doesn't reflects on the text, it just shows up as a change, but both sides look the same)
for filefield I was thinking something like considering: filesystem path, timestamp and fid (serial id in files table), don't know if something else might/should get in, or if timestamp/filesize should be ignored

My first idea : I don't think that timestamp is important , the combination of file path (in case of using FileField Path or similar modules)/filename/fid seems/description enough to me. Unless we can justify a usage for filesize and timestamp for users.

I'm not familiar with filefield module code , but according to the modules i used so far, it's pretty much extensible. So module may extend it and add more fields, and i think comment_driven should be able to consider this new fields as well.