>
> 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
> parameters, creating a whole new EmbperlObject context.
>
ok, I see where the difference is
> How are other people using these? My guess would be most people never
> mess with the EMBPERL_OBJECT* parameters from their Executes at all.
>
that will be true for most cases
> > I guess a flag would be neccessary to tell Embperl that this should be s
> > separate request and not an include of another page.
>
> Or you could split Execute into a simpler
> Execute-In-Current-EmbperlObject-Context and a more complex
> Create-New-EmbperlObject-Context if there was any simplicity or
> performance benefit that way.
>
I put it on the TODO list
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]
