[ https://jira.jboss.org/jira/browse/ISPN-293?page=com.atlassian.jira.plugi... ] Manik Surtani updated ISPN-293: ------------------------------- Fix Version/s: 4.1.0.BETA1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-293?page=com.atlassian.jira.plugin.s... ] Sanne Grinovero edited comment on ISPN-293 at 1/10/11 9:45 AM: --------------------------------------------------------------- If I could get multiple values at once, that would be good enough for the use cases I met so far and AFAIR what Emmanuel described for OGM. Map<K,V> getAll(Key... keys) ? (assuming this simplifies the implementation) was (Author: sannegrinovero): If I could get multiple values at once, that would be good enough for the use cases I met so far and AFAIR what Emmanuel described for OGM. Map<K,V> getAll(Key... keys) ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-293?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño updated ISPN-293: ---------------------------------- Fix Version/s: 5.0.0.ALPHA3 (was: 5.0.0.BETA1) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-293?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño commented on ISPN-293: --------------------------------------- {code} 4:57:13 PM galderz: so the idea would be for a getAll() which underneath would fire concurrent N calls I suppose? 4:57:28 PM galderz: that sounds like the most sensible thing 4:58:23 PM galderz: manik: updated pull req 4:59:39 PM manik: galderz: no, the idea is for a getAsync() which returns a future. 4:59:40 PM emmanuel: galderz: the problem with getAll is that we need to wait for the data to come back, where as with future, we can go ahead with our algorithm and ask for keys on the fly and pile up the futures 5:00:10 PM manik: galderz: getAllAsync() could also be implemented as syntactic sugar over multiple calls to getAsync() 5:00:23 PM galderz: indeed 5:00:23 PM manik: but IMO I'd prefer that we don't add getAllAsync() to the API 5:01:20 PM galderz: ok, we can discuss this further tomorrow AM {code} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-293?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño commented on ISPN-293: --------------------------------------- Update: I've got an implementation for this but need to sort out some issues with the context to use to update the L1 cache. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-293?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño commented on ISPN-293: --------------------------------------- https://github.com/infinispan/infinispan/pull/160 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-293?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño commented on ISPN-293: --------------------------------------- TODO: Create a unit test where the main thread commits the transaction before getAsync() has the chance to create the invocation context (2 cases here: when getAsync() is first call in the tx, and when it's 2nd inv or after) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira