Mailing-List: contact embperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <02e501c43daa$94802fe0$f90b0b0a@wingr2>
From: "Gerald Richter" <richter@ecos.de>
To: "Doug Rayner" <drayner@savicom.net>,
	"Embperl" <embperl@perl.apache.org>
References: <000f01c43c20$3011cef0$1f00a8c0@Doug>
Subject: Re: Difference between %udat and %sdat?
Date: Wed, 19 May 2004 16:07:11 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

> I would like to share state between the application object and code on
> individual template pages for the duration of a request. I'm not sure
> what the best way to do this is.
>
> I considered using %udat, but this causes an unnecessary storing of
> the session object at the end of the request.  I see there is a
> another "state" object (%sdat), but I'm not sure what the intended
> use of this is, or how %sdat differs from %udat.
>

The differences is that %udat exists only once per users, while %sdat is
copied for every request. The main reason is that when your users clicks on
the browser back button, then %sdat will also go back, while %udat will not
(same when you say new window in IE).

> I don't see any properties on the application object itself that seem
> intended for this purpose.  Is the application object a hahs
> reference? Could one add new hash keys to it if one desired?
>

Yes, both the embperl request object and the embperl application object are
hash refs and you can add any key you like (Embperl it self, does not use
the hash to store any data). The difference is that the application object
will persist between requests (but not between child processes) and the
request object will be cleaned up at the end of the request.

SO for you using the request object might be the best solution.

Gerald


> Any suggestions welcomed...
>
> Thanks and regards,
>
> Doug Rayner
> Senior System Architect
> Savicom: Next Generation eMail Marketing
> http://www.savicom.net
> (415) 617-9006
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
> For additional commands, e-mail: embperl-help@perl.apache.org

---------------------------------------------------------------------------
Gerald Richter            ecos electronic communication services gmbh
IT-Securityl�sungen * Webapplikationen mit Apache/Perl/mod_perl/Embperl

Post:       Tulpenstrasse 5          D-55276 Dienheim b. Mainz
E-Mail:     richter@ecos.de          Voice:   +49 6133 939-122
WWW:        http://www.ecos.de/      Fax:     +49 6133 939-333
---------------------------------------------------------------------------
Besuchen Sie uns auf der KOMCOM 2004 in Mannheim
25. bis 27. Mai 2004  Stand K11a   www.komcom.de

ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
---------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org