CIFS not adding 'versionnable' aspect

[jservajean]

I'm facing two different behaviours whether I had offices files from the CIFS or from the Share client :
1 - If I initially create a Word document using Share, then all the consecutive updates (no matter how, from CIFS or Share) will result in the version (1.0, 1.1, etc.) beeing automatically incremented.
2 - If the Word file is initially created thought CIFS, then all the consecutive updates (CIFS and/or Share) won't update the version number.

It turns out in the first case, the "versionnable" aspect is added, whereas it's not in the second case.

Is there a way to configure CIFS so that it behaves the same way that Share ?
How come this is not already the case ?

Thanks

[mrogers]

No.    It's a feature of share that it lazy versions.   

If you need to make everything versionable then define it via a rule (like share should have done)

[jservajean]

Thx for the reply

Just any idea on where and where it is defined in Share ? I'd like to reproduce the default behaviour even when using CIFS (it seems Alfresco adds versionnable aspects on selected mimetypes, eg. MS Office).

There's no default content rule of that kind, to my knowledge. I'd have rather bet on a policy/behaviour kind of intregation, but in that case it should be triggered server-side, so CIFS should trigger it, right ?

[mrogers]

Its hard coded into share.   As is the starting of versions as 1.0.

[jservajean]

Any idea of the name of the svn project to look into and/or the webscript/class/javascript if it's not too much to ask ?
thx