Christopher H. Laco wrote: > Long story longer, I'm finally working on Mango. This week I'm focusing > on the general bits...auth, roles, sessions, etc. > > I'm currently using Store::DBIC to get auth/db up and running. Now that > it is running, I want to ditch the use of Schema classes directly in > favor of a full domain model for auth. > > In theory, this should be nothing more than writing: > > ::Store::Mango > ::Store::Mango::Backend > ::Store::Mango::User > > which turn uses the real Mango::User(s)/Mango::Role(s) classes to do its > evil bidding. Any words of wisdom? > > Can those three packages be in the same file, or need they be seperate > files? > > -=Chris >
Actually, I've decided to write my own rather than mess with a Store::Model sidetrack at this point. The reasons were because: 1. The code to write my own is minimal. There's not a lot for Store::Model to do IMHO other than store a lot of config about which methods to interact with on the Model. 2. I want to do custom caching of users/roles so I'm not hitting the database again for every call to from_session/get_user 3. I needed to write at least on store anyway so I could grock how they work internally. 4. -dev was a ghost town, and I needed to make some progress before I go mad. :-) -=Chris
signature.asc
Description: OpenPGP digital signature
_______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
