I just went through the PR one more time. It seems like these are the areas of open discussion still:
- The name of the class "ActiveContext" needs to be decided. I'm in agreement its a bad name, but switching to past tense doesn't help IMHO.
- Disassociating the thread model and the context model. This is the first change that supports this initiative, so I'm not sure if there are any concerns with that change.
- The fact that contexts have IDs. To me it makes sense, but it seems like this is not generally agreed (we need some unique identifier to make sure we can bridge from existing)
John
I'm on PTO until Jun 29 :-(
However, we've already discussed this with Antoine so I think my
presence is not required.
Martin
Dne 21.6.2016 v 16:23 John D. Ament napsal(a):
> Unfortunately, my schedule's turned south this week and Friday as of now
> is the only day I have open.
>
> What about next week? Monday?
>
> John
>
> On Tue, Jun 21, 2016 at 4:42 AM Martin Kouba <mkouba@redhat.com
> <mailto:mkouba@redhat.com>> wrote:
>
> Any day except for Friday is ok for me.
>
> I have a feeling that it will be a tough discussion ;-)
>
> What I particularly dislike:
> * ActiveContext.associate(Thread thread)
> * the concept of the context id
> * scopeType as a method param (I would prefer a specific method/class
> for each supported scope)
>
> Anyway, if you look at Weld Context Management API [1] you'll find out
> that it's pretty powerful but also quite complex. And I don't believe we
> will be able to achieve the same level of funcionality with less complex
> API (without sacrificing correctness).
>
> Martin
>
> [1]
> http://docs.jboss.org/weld/reference/latest/en-US/html/contexts.html#_managing_the_built_in_contexts
>
>
> Dne 21.6.2016 v 09:22 Mark Struberg napsal(a):
> > Somewhen this week in the evening (CEST).
> > I’ll have a low availability for the following 2 weeks.
> >
> > LieGrue,
> > strub
> >
> >> Am 20.06.2016 um 16:55 schrieb Antoine Sabot-Durand
> <antoine@sabot-durand.net <mailto:antoine@sabot-durand.net>>:
> >>
> >> Hi all,
> >>
> >> We launched the idea to organize a meeting regarding John's
> proposal regarding CDI-30:
> >> https://github.com/cdi-spec/cdi/pull/291
> >>
> >> I wasn't available last week (going to a conference) but I am
> this week.
> >>
> >> So what are your favorite slots for this meeting ?
> >>
> >> Antoine
> >> _______________________________________________
> >> cdi-dev mailing list
> >> cdi-dev@lists.jboss.org <mailto:cdi-dev@lists.jboss.org>
> >> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>
> >> 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@lists.jboss.org <mailto:cdi-dev@lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/cdi-dev
> >
> > 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.
> >
>
> --
> Martin Kouba
> Software Engineer
> Red Hat, Czech Republic
> _______________________________________________
> cdi-dev mailing list
> cdi-dev@lists.jboss.org <mailto:cdi-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
> 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.
>
--
Martin Kouba
Software Engineer
Red Hat, Czech Republic