ConcurrencyCheck

   I notice in Cocktail that in AuditEntityBase, there is this property:

        [DataMember]

        [ConcurrencyCheck]

        [ConcurrencyStrategy(ConcurrencyStrategy.AutoIncrement)]

        public int RowVersion { get; internal set; }

If I test this with two simultaneous instance of TempHire, I do indeed get a messagebox saying that the record had been previously saved by another user.

So two questions:

1.  Most of the samples I have seen has used TimeStamp as the data type instead of int.  Any particular reason for using int instead?

2.  Is there anything else required to concurrency checking other than using the above attributes?  