<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><div class="gmail_quote">2015-03-18 13:55 GMT+01:00 Jozef Hartinger <span dir="ltr"><<a 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">
<div text="#000000" bgcolor="#FFFFFF"><span class="">
<br>
<div>On 03/18/2015 01:46 PM, Romain
Manni-Bucau wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div>
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr"><br>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="gmail_quote">2015-03-18 13:35 GMT+01:00 Jozef
Hartinger <span dir="ltr"><<a 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">
<div text="#000000" bgcolor="#FFFFFF"><span> <br>
<div>On 03/18/2015 01:28 PM, Romain Manni-Bucau wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div>
<div>
<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 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><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>
</span> break what?<span><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"> </div>
</div>
</div>
</blockquote>
</span></div>
</blockquote>
<div>don't wait behavior, own thread model by call which is
what async means most of the time</div>
</div>
</div>
</div>
</blockquote></span>
Well, the thread firing an event won't wait for the observers to
complete so I cannot see how it breaks your "original async
need/wish". Or do you associate "async" with splitting the work into
as many parallel threads as possible? If so then we have a mismatch
in terminology.<span class=""><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div></div></div></div></div></blockquote></span></div></blockquote><div><br></div><div>well about terminology maybe but I more think about expected behavior as a user. Think we now both get what we each of us put behind async and question is what's the most common case. Depending where you put async (fireAsync vs @Async/@ObserveAsync) it is not the same thing at all.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><span class=""><blockquote 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">
<div text="#000000" bgcolor="#FFFFFF"><span>
<blockquote 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><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>
</span> what common model?<span><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
</div>
</blockquote>
</span></div>
</blockquote>
<div>callbacks one which is the only one making async usable
and prod compatible</div>
</div>
</div>
</div>
</blockquote></span>
Which part is not aligned? In the current proposal you get a
callback when all observers complete or an exception occurs. In what
order the observers are called does not change anything about that.</div></blockquote><div><br></div><div>you don't control the timeout and exception from the callback. I mean in the observer chain which is what is needed most of the time (it helps me to think to it with a javascript example but maybe my personal feeling).</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><span class=""><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra"> </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>
</span></div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</span></div>
</blockquote></div><br></div></div>