A while back I wrote an authentication module to use with Dancer. I called it accounts.pm in which I initialized the $dbh using a sessions_db declared in config.yml. Then, I inherited from accounts.pm in my Dancer app with `use base` and all was good. Well, now it turns out, I have another sub-app, and I want to use accounts for that as well, but how do I tell accounts to use a different sessions store? In other words, I want one set of auth for http://myapp.com/foo and another set of auth for http://myapp.com/bar. Because I am using SQLite, I have separate db for foo and bar, so I would like to store the sessions info for foo and bar in their respective db. Of course, someone with an account to access foo, but not for bar should not be able to get into bar, and vice versa. Ideas? -- Puneet Kishor