apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mladen Turk <mt...@apache.org>
Subject Re: [PATCH] "Global" vs. "Local" prefix on named mutexes and named shm on Windows
Date Tue, 15 Oct 2013 05:01:14 GMT
On 10/15/2013 02:27 AM, Jeff Trawick wrote:

> Or in a more APR-like fashion, add apr_shm_create_ex() and apr_shm_attach_ex() which
have a special processing flag (bitmap).  For Windows,  APR_SHM_NS_LOCAL and APR_SHM_NS_GLOBAL
would be respected.  That could be used by an app that can't with with APR's
> imperfect attempts to manage global vs. local.  I don't think there is a perfect anyway.
> As 1.5.x hasn't been released yet, the _ex() functions could be in it.

Replacing Global with Local would basically limit the apr_shm API and it won't
allow IPC using shm across sessions. With services running in Session0 shm is one
of the effective IPC mechanisms. Using _ex() api and making _create() and _attach()
as macros should do the trick. Although not sure what should be default (global or local)
I'd go for backward compatibility (no sudden surprises when changing version)


View raw message