>
> Yes, they're globals, but aren't they re-initialised at the beginning
> of each request?
They are initialized at the beginning of each request
> So that the Request object is used to pass data around
> between objects in a single page, rather than between pages? Likewise
> %fdat and %ENV. %udat and %mdat are probably different because their
> whole purpose is to provide persistence between pages ...
>
One page (as viewed by the user) may consist out of many files (as you know
:-)
> If that's correct, then I was thinking of my embedded
> EmbperlObject::Execute as a (logical) new request, and expecting that
> $req would be empty like it is if I access that page directly.
>
How should Embperl determinate that this Execute call is a new request,
while when you simply include another file e.g. a header, it isn't a new
request ?
>
> Can you have an embedded call to EmbperlObject::Execute take a copy of
> $req, %fdat, and %ENV, for example, and then reset $req and %fdat to
> empty hashes before you begin the Execute, so they look just like I'd
> see if I called the embedded page directly? After the Execute you'd
> restore all three with your copies, effectively discarding whatever
> changes have happened with the embedded page. (This could be a flag to
> Execute in case people also want the current behaviour.)
>
I guess a flag would be neccessary to tell Embperl that this should be s
separate request and not an include of another page.
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
