alamid Rework model (again)

The model code is potentially buggy and partially inefficient.

I think we should move some parts into an own class (e.g all the stuff related to set, get, validate).
[ ] setSchema appears to be buggy when a normal and a shared schema are set (I'm not sure about this).
[x] The noop feature with save, fetch, destroy doesn't work

This is just for the protocol, it's not relevant now :smile:

Mar 04 '13 14:03 jhnns

I would also like to exclude the schema handling (validation & schema defintion) as a separate module. Or maybe use an existing module if there is something suitable out there.

Mar 20 '13 10:03 meaku

Yep, that's exactly what I'm planning. If there's no module that fits our needs we should extract this functionality into in independent module. This way anyone who doesn't want to use alamid entirely can use the indepedent module. Thus we can also focus on the important stuff within alamid.

Mar 20 '13 10:03 jhnns