reza_rahman at lycos.com
Thu Mar 10 14:10:13 EST 2016
To save time I suggest looping in someone knowledgable and level headed from the Servlet EG if they are not here already. I can certainly vouch for either Ed, Shingwai or Greg.
> On Mar 10, 2016, at 1:43 PM, Mark Struberg <struberg at yahoo.de> d wrote:
> Back from JavaLand conference, so sorry for not kicking in earlier.
> I not quite get the argumentation chain. It’s that all triggered by async servlet requests? And isn’t the servlet spec also saying that all the request param etc may max be assigned to a single thread AT A TIME!
> Means that it might not be on multiple threads in parallel, but the data is allowed to get moved from one thread to another (disapearing from the first one), right?
> Would really need to dig into the wording of the async servlets spec again, maybe has this in the back of his head?
>> Am 08.03.2016 um 14:43 schrieb Romain Manni-Bucau <rmannibucau at gmail.com>:
>> Hi guys,
>> following request scope thread and to center the discussion on the thread safety part: do we work on this?
>> Background: @RequestScoped is often used as a ThreadLocal instance solution. A lot of SE or Batch implementations rely on it from what I saw as well as async implementations reusing existing business logic with this thread safety constraint.
>> Proposal: providing a @ThreadScoped implementation is cheap for CDI and implemenation and would avoid the headache we can have with @RequestScoped. Will also remove the quite dark side of the spec regarding servlet request and request scope since now we would have a more natural solution for all of these situation so @RequestScoped goals wouldn't collide as much.
>> - is it automatically started as request scoped is (JMS, @Async, ...)? Alternative could be some configuration in beans.xml (merged accross the app):
>> - start/stop API (this is typically an API the user should be able to control for its own threads)
>> - CDI 2.*0*?
>> Romain Manni-Bucau
>> @rmannibucau | Blog | Github | LinkedIn | Tomitriber
>> cdi-dev mailing list
>> cdi-dev at lists.jboss.org
>> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.
More information about the cdi-dev