Although I've been deploying apps that rely on it for a while, I still feel like a bit of a newbie as far as the architectural options for DBIx::Class are concerned. I'd love to get the opinion of the list on one of these architectural topics, as I'm just getting started on a new project and have a chance right now to do things 'right'.
So, like many folks, I'm writing an application that relies on DBIx::Class as its ORM, which will be accessible through a web application but also from other clients (a command line client, for example). As a matter of best practice, should I attempt to implement authentication and authorization in DBIC, so that all my clients are automatically made to endure authN/authZ, no matter their implementation; or should I force all interaction with the application to go through the web app (ie, command-line client just makes HTTP calls) and centralize my authN/authZ there? I appreciate any and all insight you can provide! Cheers, Jeff Albert
_______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
