matthijs wrote:At first sight I would say let's go with the slashes. My only concern is: we want to support different kinds of data in the end. How does using slashes cope with that? Thinking about XML, CVS, etc.
We're only interested in storing key-value pairs with some nesting support. We don't have to implement the entire XML API. If at some point down the line we decide to support XPath-like queries then it'll probably degrade nicely to other formats anyway

For now, let's just concern ourselves with the most simple situations.
I don't think CSV was ever going to work well with this project since it's tabular and not tree-like. I'm sure there'd be a way to force it work but it would be messy

We'll move onto XmlModel when we finish this wrapper. It doesn't seem we're far away from being able to do that
I should probably discuss our options for writing the test for branching. First and foremost we want to know that values can get has(), set(), get() and remove()'d using the new syntax. But we also will need to ensure that the array we pass to $storageModel->save() is in a format we will stick to.
Let's do the tests for get(), set(), has() and remove() using our new syntax first. Hopefully we'll find that they "just work"

But we're about to see how the tests support our ability to refactor.
Care to write those get(), set(), has() and remove() tests?
