On Tue, Apr 3, 2012 at 11:25 AM, Jeff Kowalczyk <[email protected]> wrote: > Chris Travers <chris.travers@...> writes: >> The immediate problem is that the old code is not re-run safe. There >> are all kinds of scoping issues there. We need to eliminate it first. > > I learned that Plack offers a handler for legacy CGI code, perhaps it would > provide sufficient isolation to work. > > http://search.cpan.org/dist/Plack/lib/Plack/App/CGIBin.pm > > For example, if your perl-based CGI script uses lots of global > variables and such and are not ready to run on a persistent > environment, you can do: > > my $app = Plack::App::CGIBin->new( > root => "/path/to/cgi-bin", > exec_cb => sub { 1 }, > )->to_app; > to always force the execute option for any files.
I suspect one would have to also find a way to pass the Authorization headers as environment variables. I assume that shouldn't be too hard though. Best Wishes, Chris Travers ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
