Hi, >personally i am not aware of real life use cases requiring 'large' mv >properties. > >since the ultimate goal of oak is to provide a JCR implementation and the >JCR API doesn't provide any methods to manipulate/access single members >of a mv property i don't think we need to support it under the hood.
+1 Regards, Thomas
