[
https://issues.apache.org/jira/browse/IGNITE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282857#comment-14282857
]
Sergey Evdokimov commented on IGNITE-59:
----------------------------------------
I've replaced lockAsync() method with IgniteAsyncSupport API and changed all
tests that check lockAsync().
IMHO We should not to remove all somethingAsync(...), because in some cases
calling of somethingAsync(...) is more useful then IgniteAsyncSupport API,
because IgniteAsyncSupport has some problems:
1.) IgniteAsyncSupport.future() is not typesafe, if I will change method return
type It's will be difficult to find all IgniteAsyncSupport.future() invocation
corresponding that method.
2.) If method throws a checked exception I have to cache it despite the fact
that calling async method can not throw an exception.
3.) IgniteAsyncSupport API generates long code, because calling async method
take 2 lines
4.) Method implementation does not match method signature this may produce
errors.
> Support lock, lockAll
> ---------------------
>
> Key: IGNITE-59
> URL: https://issues.apache.org/jira/browse/IGNITE-59
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
> Reporter: Semen Boikov
> Assignee: Sergey Evdokimov
> Fix For: sprint-1
>
>
> Implement methods on IgniteCache: 'Lock lock(K key)', 'Lock lockAll(Set<?
> extends K> keys)', note: in new design method return Lock instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
