need for KvpFrame vs /path/for/key in key/value store

2014-12-16 Thread Sébastien de Menten
Hello, I was wondering why there was a need for a KvpFrame type when the key was nevertheless holding the full path to the value, for example a Book may have the slot: options : a frame holding options/Accounts : a frame holding options/Accounts/Use Trading Accounts : a boolean If

Re: need for KvpFrame vs /path/for/key in key/value store

2014-12-16 Thread Sébastien de Menten
replying to myself :-) - in xml, the slots frame present an hierarchical structure as slot slot:keyoptions/slot:key slot:value type=frame slot slot:keyAccounts/slot:key slot:value type=frame slot slot:keyUse Trading Accounts/slot:key

Re: need for KvpFrame vs /path/for/key in key/value store

2014-12-16 Thread Phil Longstaff
Simple answer is that when the sql backend was designed/written, I just duplicated the xml structure. Yes, the name could have included everything. Phil On Tue, Dec 16, 2014 at 2:50 PM, Sébastien de Menten sdemen...@gmail.com wrote: replying to myself :-) - in xml, the slots frame present an