Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of trawick@gmail.com designates
 209.85.214.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGKR+EDRJx52G0T+Oe9AcmnrFuo-kHj8q-Z2K0JXHXF1YzKdNA@mail.gmail.com>
References: 
 <CAGKR+EASiYmGGR+gKg+skh4BFXCZ1rJVqr398scWi5ArdZ6g-Q@mail.gmail.com>
	<CAKUrXK5PJkbDYEv4wmob6qpLNnyzONGjohgD0viTpof-6Ax_cA@mail.gmail.com>
	<CAGKR+EC4nR7-CODaxoDkC+7iL9erfTxZLvw0Ejec12-UuESjuQ@mail.gmail.com>
	<CAGKR+ECHG1pTdP9S67HC2U2CRBETKjS5hrHaZXSH5zP2OPvk8g@mail.gmail.com>
	<CAKUrXK7EKqvuh9D_g=OzH+Cs2LF5q-d1DJt86fzBXQNjdkJQpA@mail.gmail.com>
	<CAGKR+EDGpyE0fdnzm1MKe1=w68vSjRArGeYuUR57hBhV-WaazA@mail.gmail.com>
	<CAHQurc9aODETeeOoSXtOQFYZONcbAS1=5uqiQb=afc3skoUsBg@mail.gmail.com>
	<CAGKR+EB-NG9=LG=_3WYt-oK7TS345aV-aerS-D6mX1cuf8+UHw@mail.gmail.com>
	<CAHQurc_pzOQH3esaBY_-vVTmvZBOmgnk0ZfGRNG1D6Mb03HpgA@mail.gmail.com>
	<CAGKR+EDRJx52G0T+Oe9AcmnrFuo-kHj8q-Z2K0JXHXF1YzKdNA@mail.gmail.com>
Date: Thu, 27 Sep 2012 11:24:15 -0400
Message-ID: 
 <CAKUrXK5=WHt94+M9sKFy5CdhVHyJ-jqGO3fHEYGu-xdxAzyQqw@mail.gmail.com>
Subject: Re: aprmemcache question
From: Jeff Trawick <trawick@gmail.com>
To: Joshua Marantz <jmarantz@google.com>
Cc: "modules-dev@httpd.apache.org" <modules-dev@httpd.apache.org>,
 dev <dev@apr.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Sep 27, 2012 at 11:15 AM, Joshua Marantz <jmarantz@google.com> wrote:
> On Thu, Sep 27, 2012 at 10:58 AM, Ben Noordhuis <info@bnoordhuis.nl> wrote:
>>
>>   If dlsym() is called with the special handle NULL, it is interpreted as
>> a
>>   reference to the executable or shared object from which the call is
>> being
>>   made.  Thus a shared object can reference its own symbols.
>>
>> And that's how it works on Linux, Solaris, NetBSD and probably OpenBSD as
>> well.
>
>
> Cool, thanks.
>>
>> > Do you have a feel for the exact meaning of that TTL parameter to
>> > apr_memcache_server_create?
>>
>> You mean what units it uses? Microseconds (at least, in 2.4).
>
>
> Actually what I meant was what that value is used for in the library.  The
> phrase "time to live of client connection" confuses me.  Does it really mean
> "the maximum number of seconds apr_memcache is willing to wait for a single
> operation?  Or does it mean *both*, implying that a fresh TCP/IP connection
> is made for every new operation, but will stay alive for only a certain
> number of seconds.

TCP/IP connections, once created, will be retained for the specified
(ttl) number of seconds.  They'll be created when needed.

The socket connect timeout is hard-coded to 1 second, and there's no
timeout for I/O.

>
>
> It is a little disturbing from a module-developer perspective to have the
> meaning of that parameter change by a factor of 1M between versions.  Would
> it be better to revert the recent change and instead change the doc to match
> the current behavior?

The doc was already changed to match the behavior, but I missed that.
The caller I know of used the wrong unit, and I'll submit a patch to
fix that in the caller, as well as revert my screw-up from yesterday.

>
> -Josh
>


-- 
Born in Roswell... married an alien...
http://emptyhammock.com/