Hi Amy, On 2011-07-19, at 9:24 AM, Amy Worrall wrote:
> On Tue, Jul 19, 2011 at 4:50 PM, Ramsey Gurley <ramseygur...@gmail.com> wrote: >> Personally, I find this approach the simplest. The main problem I run into >> here is rule system caching. ERD2W does a fantastic job of caching to keep >> the rule system really fast, but in the case of auth logic, it isn't hard to >> imagine ways that cached values can become invalid. > > Couldn't you solve the caching problem with strategic use of > significant/dependent keys? I'm not sure that the "significant key" concept survives into ERD2W. It was necessary in D2W, but I understand that the ERD2W rule caching mechanism no longer uses that. Have you experienced Rule caching issues with authorization keys in ERD2W Ramsey? David > Of course, I can see the other advantages > to having a nice auth framework :) > >> The primary downside to ERAuth is that it requires support built into the >> view components. Right now, only one 'look' framework can use it... R2D2W > > I'm somewhat a D2W novice… is R2D2W a 'look' in the same way > ERModernLook is? Or are they different sorts of things? > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/programmingosx%40mac.com > > This email sent to programming...@mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
