[Phplib-users] interstitial?

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

;-))

> However, I've lost all interstitial auth/perm.  I know you explained this,
> but I don't find it workable.

This word, interstitial, is becoming popular. Remembers me the dentist.
What do you men here for 'i?ve lost all interstitial auth/perm ?

An interstice is a narrow passage, isn't it? 
An interstite is something so narrow, that you can pass through only one by 
one. 
So i suppose that by  'interstitial' we were speaking about the 
login_in_progress blocking state. 
Where you need a cancel login to get free of a there-but-not-yet-born auth 
object in session



>
> Using different include/require files for parts the application doesn't
> sit well.
>
> I use the interstitial checks to prompt a login for such things as admin

And what is intersitial check?

> One feature needed for interstitial use is the preservation of GET and
> POST variables.

Preservation of get post variables, yes. I got this. 
The splashform model is needed if you want to direct someone to a URL with 
GET (I am not sure POST too) parameters that auth will intercept,, show a 
login form if needed, an pass on to the page that was originally requested.

I think this can be done only with the splashform behaviour. It works like 
that already, as auth did. You point a link to a protected page, and phplib 
splases the login form, and after you successfully login you are taken to the 
real page. All these have the same url, so get and maybe post data too can be 
carried through this login process

Anyway with my auth, a page that contains a form that points to a 
login/register page can be well without  auth class, or an auth class and 
deferred form behaviour (visible, with different contents, by both suthed an 
unauthed users, as default_auth)


>  This can be done by registering them in auth_loginform()
> and restoring in auth_validatelogin() but would be much more elegant
> designed into auth.
>
> Joe