On Sat, Jan 30, 2010 at 7:09 AM, Vladimir Dronnikov <[email protected]> wrote: >> >> I don't quite understand what you mean by the real world not cascading? >> > > Suppose A buys B manufactured by C. When A or C go out of scope (die, > e.g.), it doesn't mean the end of B, right?
It all depends on what the resource is. Often with /A/B/C, C is a logical subcategory of B, and B of A. So if B ceases to exist, all C's disappear too. I would not necessarily assume that database cascading is related to URL cascading. It's up to the client to determine whether to delete that particular resource. It's up to the server to determine whether it should also cascade to delete some other resources too. I have applications where the client is never allowed to delete anything because it's meant to be a permanent record. And others where the client can't create or delete, but only edit, because all creation is done offline. map.resources (and I guess REST/Atom) assume you can always create and delete anything at any time, unless you get a forbidden error. So that's another thing I'd like to add to it, suppressing certain actions. -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
