<div dir="ltr"><div class="gmail_default" style="font-size:small">Hi all,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">for me the question is: do we need a RequestContext? We have the Event payload, which is shared (and AFAIK also still mutable) and can be used to represent the common context as well, for both synch or asynch event cases. Adding a parallel "context" does not necessarily make things easier IMO, because you have to exactly define what a request in that sense is, when does it start, where does it end, how it is propagated/stacked etc. So my question is: what is the benefit of defining the request scope additional to the event payload already in place?</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Anatole</div><div class="gmail_default" style="font-size:small"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-18 15:10 GMT+02:00 Antoine Sabot-Durand <span dir="ltr"><<a href="mailto:antoine@sabot-durand.net" target="_blank">antoine@sabot-durand.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi guys,<br>
<br>
We should finally decide how to manage normal scope context (other than application context ) in SE and during Async Event for EDR1.<br>
<br>
Having only RequestContext active during async event as Martin suggest in the PR makes sense and would be consistent with its behavior during async EJB call.<br>
<br>
Mark asked twice to activate Request Context all the time in SE (making it a new Application Context). I’m not found of it, but I’ml not the only one to decide here.<br>
<br>
What is you feeling about this ?<br>
<span class="HOEnZb"><font color="#888888"><br>
Antoine<br>
</font></span><br>_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><span style="font-family:arial;font-size:small"><b>Anatole Tresch</b></span><div style="font-family:arial;font-size:small">Java Engineer & Architect, JSR Spec Lead<br>Glärnischweg 10<br>CH - 8620 Wetzikon</div><div style="font-family:arial;font-size:small"><br></div><div style="font-family:arial;font-size:small"><i>Switzerland, Europe Zurich, GMT+1</i></div><div style="font-family:arial;font-size:small"><i>Twitter: @atsticks</i></div><div><i style="font-family:arial;font-size:small">Blogs: </i><font face="arial" size="2"><i><a href="http://javaremarkables.blogspot.ch/" target="_blank">http://javaremarkables.blogspot.ch/</a></i></font></div><div style="font-family:arial;font-size:small"><i>Google: atsticks<br>Mobile +41-76 344 62 79</i></div></div></div>
</div>