You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Yakov Zhdanov (JIRA)" <ji...@apache.org> on 2015/02/19 14:47:12 UTC
[jira] [Updated] (IGNITE-216) rework future adapter
[ https://issues.apache.org/jira/browse/IGNITE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yakov Zhdanov updated IGNITE-216:
---------------------------------
Description:
1. Rename listenAsync(lsnr) -> listen(lsnr)
1.1 Async listening may be implemented inside listener itself - handling logic will be submitted to some pool. Convenience adapters may be added.
1.2 Async chaining may be implemented in the same way.
1.3 Java8 returns futures from "listening" methods that get done when listener completes. I don's think we should implement it now. Let's postpone it.
2. we can remove context - it will not be used in future any more
3. remove boolean fields that manage async settings
4. remove validity check + externalizable
5. remove listeners collection, but have 1 listener and chain them if needed. I suspect in 99% of cases we have only 1 listener.
was:
1. remove async notification - everyone can create listener that executes in async manner
2. we can remove context - it will not be used in future any more
3. remove boolean fields that manage async settings
4. remove validity check
5. remove listeners collection, but have 1 listener and chain them if needed. I suspect in 99% of cases we have only 1 listener.
> rework future adapter
> ---------------------
>
> Key: IGNITE-216
> URL: https://issues.apache.org/jira/browse/IGNITE-216
> Project: Ignite
> Issue Type: Bug
> Reporter: Yakov Zhdanov
> Assignee: Yakov Zhdanov
>
> 1. Rename listenAsync(lsnr) -> listen(lsnr)
> 1.1 Async listening may be implemented inside listener itself - handling logic will be submitted to some pool. Convenience adapters may be added.
> 1.2 Async chaining may be implemented in the same way.
> 1.3 Java8 returns futures from "listening" methods that get done when listener completes. I don's think we should implement it now. Let's postpone it.
> 2. we can remove context - it will not be used in future any more
> 3. remove boolean fields that manage async settings
> 4. remove validity check + externalizable
> 5. remove listeners collection, but have 1 listener and chain them if needed. I suspect in 99% of cases we have only 1 listener.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)