Hi, > > I've been trying to use Embperl::Object offline (from within > some other perl code) and I'm finding it difficult to pass > the correct options. > > There is %Embperl::initparam, but this is only good for > global initialisation. I would have expected to also be able > to pass any config option in the relevant constructor or > using a method on the object before it was executed, but that > seems not to be the case. > > In particular - I can't work out how to create/configure/use > an Application object across multiple requests simply from > the perl API (without going through environment variables and > %Embperl::initparam). > There doesn't seem to be any "create a request object from > this application object" method - although the reverse exists > (Embperl::Req::InitRequest(...)->app). > > Is this possible currently or should it be considered a > feature request? >
At the moment there is no real object orientation interface to Embperl::Object, there is only one entry point Embperl::Object::Execute. On the first call it will create the application object and (as long as you don't give a different appname) will reuse it on subsquent requests. You can pass all your configuration to Embperl::Object::Execute. The application configuration will be ignored on the second and any further calls (as long as appname is the same). Does this help or you have different needs? Gerald --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
