> Or do I continue to run it as an Apache::Registry script, and > call SetupSession some other way? >
Yes, you continue with Apache::Registry and use SetupSession to get the session data (and CleanupSession to close it). The other possibility would be to run gbroswe under Embperl (with EMBPERL_SYNTAX Perl), that %udat will be available anyway, but in case parameter are POSTed to that script they are already read in by Embperl. You might need to disable this in EMBPERL_OPTIONS. Gerald > Allen > > On Thu, Mar 10, 2005 at 02:56:58PM +0100, Gerald Richter wrote: > > > Here is what I would like to do: > > > > > > There is a script called 'gbrowse', which I didn't write, > but which > > > I need to call from within my embperl application. This > script works > > > by printing to STDOUT. > > > > > > So why not just keep it in my Apache::Registry directory > and call it > > > like an ordinary mod perl script? The reason is that gbrowse will > > > use a library which I _did_ write, called Plugin.pm. > > > > > > Now, I would like Plugin.pm to have access to %udat. > > > > > > > You need to call SetupSession (see session handling in the > docs) from > > your Plugin.pm. > > > > Unfortunately you need Embperl 2.0rc3 for this to work, > which will be > > release during the next days. If you like I can send you a copy by > > private email or you can fetch it from the CVS > > > > Gerald > > > > -- > > > The more stupid of the old peasants came to the pasture to > wag their tongues with him; village women ran to him to > recover from their men's fits of craziness, and they were > never angry with Sashka for his love or his disease. > > -isaac babel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
