[infinispan-dev] Distributed Executors in write mode, need reference to Cache

[Sanne Grinovero]

On 20 December 2011 13:47, Manik Surtani <manik at jboss.org> wrote:
> So you're suggesting that the task is registered as a CDI bean on each remote node, so that requested services can be injected?  Makes sense.  But this would have to be a part of infinispan-cdi, as an extension to what we have in DistExec.  I presume this is what you had in mind?

Yes.
Anyway a first step would be to provide a reference to the Cache, both
to DistExec and MapReduce tasks, this should be doable even without
introducing infinispan-cdi; but we need a cool proposal in terms of
API - especially if @Inject is not supported that makes it harder to
design.

Sanne

> On 20 Dec 2011, at 12:43, Sanne Grinovero wrote:
>
>> On 20 December 2011 13:35, Manik Surtani <manik at jboss.org> wrote:
>>> What else do you think could/should be provided?
>>
>> Whatever people want to do with their data.
>> Imagine you have to update all values by using some external service
>> which provides some needed input, or you want to find all entries by
>> some criteria and send them over to S3 via another service, or are
>> storing movies and want to encode them using some other tool you have
>> - these services could be invoked each time but assuming it has some
>> expensive initialization it's likely one wants to inject references to
>> initialized services and pools of resources.
>>
>> This user is asking for a reference for the Cache, that's the first
>> step, but the next step is obviously to inject anything out of our
>> control; recommending a new JNDI context + lookup per entry is likely
>> not the most usable approach, while CDI should be simple to integrate
>> and provide lot of value.
>>
>>>
>>> On 19 Dec 2011, at 18:57, Sanne Grinovero wrote:
>>>
>>>> Highlighting this use case:
>>>>
>>>> http://community.jboss.org/message/642300#642300
>>>>
>>>> As I replied on the forum, I think we might need to improve the
>>>> DistributedExecutorService by providing access to some context to the
>>>> Future before it's executed remotely, as having a reference to the
>>>> Cache it's being executed on seems very useful, but it might not be
>>>> limited to the Cache only.
>>>>
>>>> I guess to make good use of it, someone might need to access just
>>>> anything: CDI looks like a good fit?
>>>> _______________________________________________
>>>> infinispan-dev mailing list
>>>> infinispan-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>>
>>> --
>>> Manik Surtani
>>> manik at jboss.org
>>> twitter.com/maniksurtani
>>>
>>> Lead, Infinispan
>>> http://www.infinispan.org
>>>
>>>
>>>
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> --
> Manik Surtani
> manik at jboss.org
> twitter.com/maniksurtani
>
> Lead, Infinispan
> http://www.infinispan.org
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev