For anyone who might have an interest in how we resolved this, here's the
deal:
We provide an intranet ASP.NET app that does forms and Windows
authentication. In a production environment, the AD domain's availability
is
assured during installation and through customer education; for
development
scenarios, however, developers' machines aren't always joined to the
domain
(specifically, contractors who provide their own laptops) and the issues
this causes can be avoided once we know the machine is a standalone. In
our
own development environment, at least, any performance gain realized from
Joe or Richard's solutions would be small -- the timeout is quite
tolerable
for us -- and wouldn't justify the added complexity, however slight.
|
