I am prototyping a web application using some of the "microframeworks",
including Squatting. As part of that I want to have the best chance of doing
things the right, not just the obvious, way.
One of the issues I have with Squatting, right now, is working out how best to
integrate authentication into the site: we are going to have a couple of areas
that require a login, along with a couple of unprotected areas.
As far as I can tell the best way to implement this protection uniformly
across the "admin" area — which will be a handful of different controllers, in
the current design — is to wrap the 'service' method.
That way we can ensure that we apply the right protection to the area, no
matter how many or few controllers it consists of. (Also, that we apply them
to third party applications we might mount into that space.)
Is that the best model? If so, one of the issues we face is that we will want
to redirect an unauthenticated session to the login form, which presumably
means doing that inside the 'service' method...
✣ Daniel Pittman ✉ dan...@rimspace.net
☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
You received this message because you are subscribed to the Google Groups "squatting-framework" group.
To post to this group, send email to squatting...@googlegroups.com
To unsubscribe from this group, send email to squatting-frame...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/squatting-framework?hl=en