>
> I'm using these quite differently though - my include Executes are
> typically simple and never use the EMBPERL_OBJECT* parameters - they
> feel like Embperl::Executes within an EmbperlObject search path context.
> My 'new' request, on the other hand, is setting all the EMBPERL_OBJECT
> parame
On Mon, Jul 09, 2001 at 12:22:10PM +0200, Gerald Richter wrote:
> > 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
>
> 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. %u
Hi Gerald,
On Sun, Jul 08, 2001 at 03:06:37PM +0200, Gerald Richter wrote:
> That's the intented behaviour, because the Embperl Request object is
> the way how different pages can communicate (pass data back and
> forth). That's the same for %fdat, %udat etc. (and the %ENV is always
> a Perl glob
Hi,
>
> Not sure if this is a bug or me simply making assumptions about how
> EmbperlObject would work ...
>
That's the intented behaviour, because the Embperl Request object is the way
how different pages can communicate (pass data back and forth). That's the
same for %fdat, %udat etc. (and the
