-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tim Hoffman wrote:
> Good points raised and could well be an significant requirement. I > have not yet used repoze.who and have limited experience with wsgi > middleware (Beaker with appengine based memcached session store is it) > so I have wondered how you can hook up any ui to the middleware. > > > On Mon, Jan 25, 2010 at 10:39 PM, Chris McDonough <chr...@plope.com> wrote: >> My experience so far with helping people who want lots and lots of control >> about how a login UI works with r.who has not been stellar; this is the only >> reason I mention being able to cutnpaste code into a BFG authentication >> policy. When you use a custom authentication policy, you can still control >> the horizontal and vertical of login and logout, whereas with r.who, you >> typically have less control. Chris gets pretty weary of answering the "how to I make the login form fit into my application?" question, which is problematic for r.who as middleware. Note that: - - Your requirements (openId, etc.) don't sound like you expect a login form to be an issue. I think it sounds like it might be a pretty good fit for r.who. - - the r.who trunk allows you to re-use the configured set of plugins via an API while still driving the login processs, if needed. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktdsrcACgkQ+gerLs4ltQ41hgCfSmOYFJGudLgs1WDrY+W/+fRu weUAoMMTeqUEtbgcvweYwAjhm1jgAxdh =qKSX -----END PGP SIGNATURE----- _______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
