Mailing-List: contact embperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (nike.apache.org: local policy)
Date: Fri, 7 Jan 2011 15:12:32 -0500
From: Matt J Cwanek <mcwanek@fourddev.com>
To: embperl@perl.apache.org
Subject: Handler example?
Message-ID: <20110107201232.GC8064@fourddev.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
X-DCC-sonic.net-Metrics: sol; whitelist
X-Virus-Checked: Checked by ClamAV on apache.org

Hello:

Is there an example somewhere of using a custom handler that eventually
calls Embperl to process the page? I'm working from some old code that
used HTML::Embperl to do this, and am having trouble getting fdat to
work properly with my handler under Embperl/MP2.

The HTML::Embperl handler that I'm working from (and that works fine
with HTML::Embperl) would take care of creating fdat on it's own using
CGI, and eventually would call HTML::Embperl::Execute to process the
page (optDisableFormData was enabled).

As I try to port this forward to Embperl/MP2, I'm having problems with
fdat being clobbered later by subsequent nested Embperl::Execute calls,
which wasn't a problem with HTML::Embperl/MP1. It's almost like a scope
problem, but it only seems to shows up if I have nested Execute calls.


Thanks for any help.

Matt


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