On 2013-10-30 19:25, Jukka Zitting wrote:
In fact most content structures and access patterns I've seen make a big distinction between properties and child nodes, so it makes sense to treat them separately on the storage layer (as discussed, all our backends do that). From that perspective having a shared namespace for properties and child nodes goes against the grain, as it forces a backend to either use a data structure that's not optimal for common access patterns or to do extra work to prevent separate data structures from overlapping.
+1 Best regards, Julian
