perl-embperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hall, Philippe" <philippe.h...@augustachronicle.com>
Subject RE: Re: object life
Date Tue, 28 Feb 2006 17:59:50 GMT
My understanding is that modules are kept in a namespace determined by
package name.  The solution is to name and call your modules separately
using a different namespace, ie:

Use Project1::db;

And 

Use Project2::db;


Also, I would recommend using startup.pl to load your packages before
there is ever a request.  This will reduce load time on the first
request for each thread and prevent inconsistent behavior from thread to
thread if you are developing or tweaking the modules.


Philippe Hall




-----Original Message-----
From: Daniel [mailto:embperl@7thfire.com] 
Sent: Tuesday, February 28, 2006 12:53 AM
To: RobertCZ
Cc: embperl mailinglist
Subject: Re: Re: object life

On Mon, Feb 27, 2006 at 05:24:55PM +0100, RobertCZ wrote:
> not very clear what exactly you are doing - you have two apache
virtual 
> servers both using Embperl::Object and they clash? you use 
> Embperl_App_Name, right?

hm, no, not quite.
> 
> if I dont understand, would you mind showing us some simplified code?

let me try.

index.epl has a use statement.
use db;

That loads a Class::DBI database abstraction class.

I have two instances of my application running.

they live in two different paths, but the db module exists in both.
...

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


Mime
View raw message