Re: [phplib] iis, frames and page_close From: Kristian Koehntopp (kris <email protected>)
Date: 10/27/00

In netuse.lists.phplib you write:
>in one frame you have navigation, the other you have an application, you
>cannot use page close in both, so if you get a submit in navigation,
>screw the application post data which there shouldn't be any, and if you
>get submit in the application, don't screw with the navigation data,
>because in any other scenario, i don't see any thing working right?

Right. There is another solution to this, and this is to use locking and
effectively serialize both frame operations, that is,

navigation content
  page_open() -> aquire lock
                                page_open()-> try to get lock,
                                              fail,
                                              wait

  page_close()-> release lock
                                           -> aquire lock

                                page_close()-> release lock

The locking code has never been activated in PHPLIB, and has
never been tested thoroughly. Also, I believe Sascha has
introduced a bug during the migration from 6 to 7.x, due to a
misconception on the range of the lock: The lock must span the
whole page, from open to close, not the operations during
page_open() or the operations during page_close.

You could have a look at the locking code in ct_sql.inc and/or
session.inc and try to activate it in order to serialize your
page operations. I do not recommend it, though, as it makes your
pages even slower than they are. This is the reason why it never
has been activated in PHPLIB before.

>i'm just trying to get a thumbnail sketch, i don't use frames because of
>the thread i'm reading now, and the thread i've read in the past.

This is the most beautiful solution, as frames such anyway.

Kristian

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>