Mailing-List: contact users-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@felix.apache.org
MIME-Version: 1.0
In-Reply-To: <33162303.post@talk.nabble.com>
References: <33158446.post@talk.nabble.com>
	<4F16B132.4050303@googlemail.com>
	<33162303.post@talk.nabble.com>
Date: Tue, 24 Jan 2012 10:55:15 +0100
Message-ID: 
 <CAKkCf4oLtmXy+A278Hxt0jc6dku8k0w2C-oXLD8WnVtC-g7c2Q@mail.gmail.com>
Subject: Re: EventAdmin Asynchronous/Parallel EventHandler
From: Carsten Ziegeler <cziegeler@apache.org>
To: users@felix.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

we haven't implemented this feature yet but will do once the final
spec is publically available.

I've written a new implementation of the event admin which is in the
felix sandbox atm, this one is significanlty faster than the old
implementation from trunk.

Regards
Carsten

2012/1/18 DBinSD <cdiebner@gmail.com>:
>
> Thanks Holger, this is exactly the info I was looking for. =A0It sounds l=
ike
> the Async Unordered Events might get me the performance I was looking for
> (though the implications of 'unordered' events might be a problem in some
> applications). =A0I will keep an eye out for an implementation of this
> feature.
>
> Thanks again
> Chris
>
>
>
> Holger Hoffst=E4tte-4 wrote:
>>
>> On 18.01.2012 03:35, DBinSD wrote:
>>> Does the felix implementation of the EventAdmin service support the
>>> delivery
>>> of events, asynchronously and in parallel to multiple listeners at once=
?
>>> It
>>
>> This was addressed as part of RFC 157 ("Updates to EventAdmin") sometime
>> in 2010 and accepted, though I don't remember offhand what the
>> implementation status was/is. IIRC it was part of 4.3.
>>
>> The solution added a set of constants that express basic delivery
>> behaviour/expectations. Not really enforceable end-to-end QoS constraint=
s
>> (which are impossible in Java anyway) but better than nothing.
>>
>> --snip--
>>
>> 5.2 =A0 =A0Asynchronous Unordered Events
>>
>> The following constants are added to EventConstants. This allows an Even=
t
>> Handler to indicate that it is willing to relax the event ordering
>> requirements so that Event Admin can optimize delivery.
>>
>> String EVENT_DELIVERY =3D "event.delivery"
>> Service Registration property specifying the delivery qualities requeste=
d
>> by an Event Handler service.
>>
>> Event handlers MAY be registered with this property. Each value of this
>> property is a string specifying a delivery quality for the Event handler=
.
>>
>> The value of this property must be of type String, String[], or
>> Collection<String>.
>>
>> Since:
>> =A0 =A0 =A0 =A0 1.3
>> See Also:
>> =A0 =A0 =A0 =A0 DELIVERY_ASYNC_ORDERED
>> =A0 =A0 =A0 =A0 DELIVERY_ASYNC_UNORDERED
>>
>> String DELIVERY_ASYNC_ORDERED =3D "async.ordered"
>> Event Handler delivery quality value specifying the Event Handler requir=
es
>> asynchronously delivered events be delivered in order. Ordered delivery =
is
>> the default for asynchronously delivered events.
>>
>> This delivery quality value is mutually exclusive with
>> DELIVERY_ASYNC_UNORDERED. However, if both this value and
>> DELIVERY_ASYNC_UNORDERED are specifed for an event handler, this value
>> takes precedence.
>>
>> Since:
>> =A0 =A0 =A0 =A0 1.3
>> See Also:
>> =A0 =A0 =A0 =A0 EVENT_DELIVERY
>>
>> String DELIVERY_ASYNC_UNORDERED =3D "async.unordered"
>> Event Handler delivery quality value specifying the Event Handler does n=
ot
>> require asynchronously delivered events be delivered in order. This may
>> allow an Event Admin implementation to optimize asynchronous event
>> delivery by relaxing ordering requirements.
>>
>> This delivery quality value is mutually exclusive with
>> DELIVERY_ASYNC_ORDERED. However, if both this value and
>> DELIVERY_ASYNC_ORDERED are specifed for an event handler,
>> DELIVERY_ASYNC_ORDERED takes precedence.
>>
>> Since:
>> =A0 =A0 =A0 =A0 1.3
>>
>> See Also:
>> =A0 =A0 =A0 =A0 EVENT_DELIVERY
>>
>> --snip--
>>
>> Also see
>> http://stackoverflow.com/questions/7018762/when-to-use-osgi-eventadmin-a=
nd-when-not
>> for BJ's official answer.
>>
>> hope this helps
>> Holger
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>>
>
> --
> View this message in context: http://old.nabble.com/EventAdmin-Asynchrono=
us-Parallel-EventHandler-tp33158446p33162303.html
> Sent from the Apache Felix - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>


--=20
Carsten Ziegeler
cziegeler@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org