hi
we are also in the middle of the implementation of a system using AddXSLParams::BasicSession which does similar to your (I guess) to keep status info into a session-DB. Between different steps of a pipeline/HTTP-redirects and the like.
On Apr 28, 2005, at 3:21 PM, [EMAIL PROTECTED] wrote:
Obviously this is to do with the way the Axkit plugin is working. It must
only be checking the session variables at the start of the pipeline rather
than before each transformation.
But, is there a way around this? Can I tell it to re-process the session
variables just before the final transformation somehow?
due that Apache::Session module itself, on which AddXSLParams::BasicSession is based on, does not save() automatically vars/keys when you store them (kept into an in-memory hash till you untie/save). But you have to do it explicitly yourself. At least this is what I needed to do before each HTTP redirect to keep my session status consistent between pages, after each session set_attribute() call:
my $session_db;
if( $session_db = tied(%Apache::AxKit::Plugin::BasicSession::session) ) {
$session_db->save;
};
which actually forces the session to be re-read from the backend DB once you "go in from another page/step" (I guess re-tie the DB)
I am not sure this is of any help to you
cheers
Alberto
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
