ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Setrakyan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-59) Support lock, lockAll
Date Mon, 19 Jan 2015 19:03:34 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282870#comment-14282870

Dmitriy Setrakyan commented on IGNITE-59:

* The idea behind the {{IgniteAsyncSupport}} is that majority of API invocations are synchronous.
Async APIs are only invoked in advanced use cases and it is OK if they are a bit more complex.
Otherwise we would have 2x the number of methods, one for sync and one for async APIs.
* As far as exception handling, there should not be any checked exceptions thrown in Ignite.

> 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

View raw message