Mailing-List: contact celix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: celix-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of a.broekhuis@gmail.com
 designates 209.85.215.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <52356979.1040002@sundevil.de>
References: <5213C63A.1050002@gmail.com>
	<E825BCB2-EAFD-4E97-88C0-B1BB1085506A@luminis.nl>
	<52150460.7070606@gmail.com>
	<CA+T-u8e2tvMgKdj9FjQ6h5ACQFmT11k8RpvKJ-Ci64HoW9fYEw@mail.gmail.com>
	<52356979.1040002@sundevil.de>
Date: Mon, 16 Sep 2013 10:00:57 +0200
Message-ID: 
 <CA+T-u8fOd9TbY5W2h4PYxrLJzo1-mM09c3=CbOMEQ8TLio-Rqw@mail.gmail.com>
Subject: Re: Remote service using shared mem
From: Alexander Broekhuis <a.broekhuis@gmail.com>
To: celix-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=089e01493e42b4295204e67b9a3e

--089e01493e42b4295204e67b9a3e
Content-Type: text/plain; charset=ISO-8859-1

Hi,


I just created JIRA issue CELIX-81, including a patch which adds several
> components allowing CELIX to use Shared Memory for remote services
> (discovery_shm, remote_service_admin_shm and example_proxy_shm). Besides,
> two new deployment targets are added, which can be used to locally test the
> shared memory implementation using the already existing example_service.
>

Thanks for this work! If Pepijn hasn't started working on this, I will test
and add it to the build tomorrow.

>
> Netstring support (see JIRA issue CELIX-80 for according patch) is
> required to get the this shm implementation working.


Out of curiosity and for compatibility with Java, is there also some java
support for it? I am still interested in writing a java version as well.
Maybe you could provide some technical details on the working of it.


> Also note that shared memory segments or semaphores might be left in the
> system and needs to be removed manually (see ipcs, ipcrm) when CELIX does
> not shutdown as expected.
>

Did you use APR for this? Or doesn't APR support semaphores etc? I haven't
looked at it at all, but using APR would be great.

Also, does the code check if there is anything left when starting again?

Either way, making Celix robust so that is doesn't shutdown as expected is
the best solution ;).


-- 
Met vriendelijke groet,

Alexander Broekhuis

--089e01493e42b4295204e67b9a3e--