dale w lance wrote:
1. If methodX writes new values to these properties, which object gets modified?
That depends on how you modify them. There isn't any simple way to say "give me the object whose property I would acquire if I asked for 'foo'", and since you can only change a property by calling a method of the owning object... <shrug> Besides, writing is very different from reading, and with good reason. You often won't *want* to write a property on the same object from which you acquired its old value, especially if the old value is a "default" value.
2. Since everything is off of [one] can't I get everything through proper structuring of the url?
Not sure what you mean. Get every what? You can arrange your URL to give your target object whatever acquisition chain you like, but unless it is a method, it will always search its absolute path first.
3. Isn't security (permissions) acquired? (see previous post about structuring large projects)
Yep. That can be a royal pain, too, if your security arrangements are complex.
4. Can I circumvent security by structuring my url to acquire methodX from another object?
Circumvent which security? methodX will operate in the security context of your target object, but you also won't be able to acquire it unless you have permission to access it in the first place. You can never get at an any object without passing (at least) all security restrictions imposed in its absolute path. Cheers, Evan @ 4-am