<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 03/18/2015 01:28 PM, Romain
Manni-Bucau wrote:<br>
</div>
<blockquote
cite="mid:CACLE=7PH1ekEz=+rwXj=HgCUz1pOx0oBO0rOgq7+oCLthH05Lg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div>
<div class="gmail_signature">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr"><br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">2015-03-18 13:15 GMT+01:00 Jozef
Hartinger <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jharting@redhat.com" target="_blank">jharting@redhat.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class=""><br>
On 03/18/2015 11:16 AM, Romain Manni-Bucau wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
sequentializing them arbitrarily just makes it not
async anymore<br>
</blockquote>
</span>
the event firing thread won't wait for event delivery so
it is still async</blockquote>
<div><br>
</div>
<div>well doesn't change the fact you break original async
need/wish doing it.</div>
</div>
</div>
</div>
</blockquote>
break what?<br>
<blockquote
cite="mid:CACLE=7PH1ekEz=+rwXj=HgCUz1pOx0oBO0rOgq7+oCLthH05Lg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
(+ think to the case you dont really have priorities
you are just breaking the whole concept).<br>
</blockquote>
</span>
If you do not have priorities (or they are the same) then
it is most likely fine to notify the observers in
parallel. If you however do have priorities then it makes
sense IMO to take them into account. Doing otherwise just
complicates the entire concept by adding an artificial
constraint.<br>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">point is you are introducing a model
concept which is not aligned on the common model + doesn't
even match correctly the async needs (what about onFailure()
and onTimeout() which are mandatory when doing async)</div>
</div>
</blockquote>
what common model?<br>
<blockquote
cite="mid:CACLE=7PH1ekEz=+rwXj=HgCUz1pOx0oBO0rOgq7+oCLthH05Lg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">I tend to join Mark saying we should
just do the minimum instead of wanting to do to much and
providing something highly broken we'll need to fix in next
version with more broken patterns. What's the need is the real
question, not what would be cool to implement.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Don't forget an async spec smells more
and more strong with real async semantic and solutions so I
guess the less we put in CDI now better it is.</div>
</div>
</blockquote>
<br>
</body>
</html>