see below billf wrote: > I guessing this didn't push anyone's buttons but I thought I'd bring > it to the top of the queue just one more time in case someone could > respond :-) Apologies if this is a breach of forum etiquette. > > On Jan 27, 6:52 am, billf <[email protected]> wrote: > >> 1. The idea of bundling Mail, Auth and Crud in tools.py seems >> shortsighted. >> >> Mail isnt specific to either of the other classes. I can use Auth >> without Crud. How many tools will be added to tools.py before it >> becomes unmanageable? and then what will you call the overflow file? >> tools2.py? >> It's not that bad. You can convert the module (tools.py) into a package (tools/__init__.py) and then it's just an organization problem. >> 2. All use of Auth seems to be couched in the context of Crud. >> >> It should be (and is) possible to use Auth independent of Crud and >> that should be the primary form of its demonstration. In fact, Crud >> is really about something totally separate: the defining of url >> request formats to avoid writing stub functions. Grouping the two >> together is unnecessary and confusing. Crud, REST and basic cherrypy >> request formats are alternative request formats that have nothing to >> do with authentication per se. >> I agree, Auth should be independent of crud and vice versa. >> 3. So I don't want to use the Crud request format and I want to use >> authentication. >> >> Let's say "the admin user" wants to protect the widget record with >> id=33 from everyone but him/herself. How do I code the app? Do I >> have to code something in every function that could read/list/update/ >> delete that record? and if so what do I code? How do I know whether >> authentication is 'on' and what resources I need to check? >> >> 4. My company already has an authentication framework. >> >> How can I use web2py and link to an existing authentication >> framework. I think this highlights the weakness of the current >> "plugin app" approach. The authentication is the "plugin" and this >> need to be integrated with the core via an API. The pages/functions >> that maintain the authentication database tables are the "app" and >> this doesn't even have to exist to use authentication (if the db >> aspect is maintained elsewhere). >> I use my own authentication currently just because I tie into a database that web2py DAL doesn't support. Can I do this with the new auth? >> (Retires to bunker and puts on tin helmet.) >>
-- Timothy Farrell <[email protected]> Computer Guy Statewide General Insurance Agency (www.swgen.com) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
