Has anyone implemented HTTP Authorization requests within Turbine.
What I am thinking of is a Screen such that all screen extending it would
require Authorization, and would request it with HTTP headers, instead of
displaying a form that the user has to fill out.
I might very well implement this myself, but am not an expert on HTTP, so
any comments would be appreciated.
(Like, possibly, why this is not the default mechanism, I'm guessing there
is a good reason).
----------------------------------
Magnús Þór Torfason
CTO
handPoint
Iceland
e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
office: +354 - 561 0700
mobile: +354 - 699 8799
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
