cascading PUTs

[ironspecs]

Allow cascading PUTs, so that people can save things like this:

ref at { a: "b", c: {_ref: "d", e: "f"}}

which will produce two PUTs in this order:

ref at { a: "b", c: {_ref: "d"}}
d at { e: "f"}

If either PUT fails, they'll both fail.

[cruzanmo]

Why not just obj = {};?

[ironspecs]

Because it needs to be a particular object, specifically the one linked to by the original object. That's what it means by "in-place". Creating a new object might as well be {}, like you say.

In this case, there is a root object with many objects within it, and we're clearing those deep objects located somewhere deep within that root object. We don't know where these deep objects are -- they could even be within several layers of other objects within the root object.

[cruzanmo]

Looks good.