Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: Shared var between processes
To: modperl@perl.apache.org
References: <9821FF17-7196-4644-B04B-18824978916C@gmail.com>
 <0fdeb6bf-3036-7359-e42b-035dafaeeca2@utoronto.ca>
 <8738480F-BB7E-4160-AF5C-5871E2603266@gmail.com>
 <CAC5eUSsz3FjijfnvM9McKTgAAmbwLdm0xw6Gm1aGNpFSFMLthQ@mail.gmail.com>
 <59E9B621.5020206@ice-sa.com>
 <F2079CA4-AAC4-4A75-9271-AE3C45201BC1@gmail.com>
 <59E9BF45.6090903@ice-sa.com>
 <15d27b7c-03b0-f7dc-4c57-0ee0110478a2@utoronto.ca>
 <59EAEED3.4090304@ice-sa.com>
 <E0F1C273-DCC6-4D4D-9AB5-B58707B64BFF@gmail.com>
 <59EC730B.8070000@ice-sa.com>
 <CAC5eUSswom=gUi0vz8yYwhtnrTSZdo0-typusGZY4SrJEZopNw@mail.gmail.com>
From: =?UTF-8?Q?Andr=c3=a9_Warnier_=28tomcat=29?= <aw@ice-sa.com>
Message-ID: <59ED0A62.3070505@ice-sa.com>
Date: Sun, 22 Oct 2017 23:15:14 +0200
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <CAC5eUSswom=gUi0vz8yYwhtnrTSZdo0-typusGZY4SrJEZopNw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
archived-at: Sun, 22 Oct 2017 21:15:31 -0000

On 22.10.2017 18:59, John Dunlap wrote:
> In our case, we do not use Windows for anything. Even our desktops are Linux. We already
> employ Redis, which performs the same function as memcache, however, this doesn't really
> solve the problem because each virtualhost also relies on its own redis database so, even
> in that case, we would still need a per virtualhost configuration mechanism to tell us
> which redis database to use.
>
> At present, I kinda like Ben Rubson's suggestion of a read only hash in a startup script
> which is keyed by hostname

Yes, no doubt about that. But this does not answer the question : where do you store this 
hash (or a reference to it), so that a handler, later, would have access to it ?

startup_script :

my $big_hash = {
	hostname1 => { ... },
	hostname2 => { ... },
	};
# save $big_hash "somewhere"
exit;

... later ...

sub handler {
# how do I access $big_hash ? (where is it ?)

return OK;
}


>
> On Sun, Oct 22, 2017 at 6:29 AM, André Warnier (tomcat) <aw@ice-sa.com
> <mailto:aw@ice-sa.com>> wrote:
>
>     On 22.10.2017 09:45, Ben RUBSON wrote:
>
>         On 21 Oct 2017 08:53, André Warnier (tomcat) wrote:
>
>             On 20.10.2017 17:15, Adam Prime wrote:
>
>                 On 17-10-20 05:17 AM, André Warnier (tomcat) wrote:
>
>                     On 20.10.2017 10:50, Ben RUBSON wrote:
>
>                         On 20 Oct 2017 10:38, André Warnier (tomcat) wrote:
>
>                     I believe that there is much more of a performance hit, when asking
>                     the server to set up
>                     an environment ($ENV) for sub-processes, than via the PerlSetVar
>                     mechanism.
>
>
>                 You don't need to use $ENV. If you're using handlers you could use
>                 $r->server()->server_hostname.
>
>                 You could certainly create a big hash at startup and grab stuff out of it
>                 that way, where
>                 the top level key is the hostname.
>
>
>             Assuming that you wanted to do this, where would you put this big hash, so
>             that it is
>             persistent across requests, and can be accessed by mod_perl handlers ?
>
>
>         If it's a read-only hash, then a startup script (PerlPostConfigRequire) as Adam
>         proposed
>         before seems to be the right way.
>
>
>     Yes, but where exactly do you keep that hash, so that it is accessible later on by
>     mod_perl handlers ? (across requests)
>
>
>
>
> --
> John Dunlap
> /CTO | Lariat/
> /
> /
> /*Direct:*/
> /john@lariat.co <mailto:john@lariat.co>/
> /
> *Customer Service:*/
> 877.268.6667
> support@lariat.co <mailto:support@lariat.co>