[Phplib-users] blocking mode vs default_auth

[Giancarlo <gia...@na...>]

Il 05:43, mercoled=EC 25 settembre 2002, hai scritto:
>
> I currently have a large application which uses the old blocking Auth
> method and it is the right thing for that application -- all users must
> be authenticated and there are no default facilities.
>

Then what you want is:
wherever I instantiate the auth feature, if the user bears no authenticat=
ion,=20
a splash login page is shown by auth itself, your script does not have to=
=20
check anything. Just instantiating the auth class will do it. You don't=20
really want blocking mode. You wat a splash form behaviour handled by aut=
h=20
itself.

Others, or you in other apps,  my want:

whenever I instantiate the auth feature, auth returns me a value that say=
s if=20
the user bears authentication or not. And my script, not auth, decides wh=
at=20
to do, when to do it. You don't want blocking mode here either. You want =
to=20
handle the situation by yourself knowing if the user is logged or not. Th=
a=20
auths class outputs nothing, it just returns you a value that says if he =
is=20
logged in or not

They are two different things, but they eat the tail one each other, as i=
t is=20
now.

My auth class, with the splashform behaviour, suits your need perfectly t=
he=20
same as before.=20
The 'form' aim (preveting registration with a single POST, maybe from a b=
atch=20
script), is not needed once we are sure, for example, that a new session =
can=20
be obtained by simply appending ?Example_session=3Dfoo to the URL request=
. The=20
effect is the same as that of having previously requested a login form:=20
prevents single POST registration


Gian