[
https://issues.apache.org/jira/browse/MNEMONIC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453731#comment-15453731
]
ASF GitHub Bot commented on MNEMONIC-60:
----------------------------------------
GitHub user lcy0816 opened a pull request:
https://github.com/apache/incubator-mnemonic/pull/19
MNEMONIC-60:Apply Transaction, Retrievable interfaces to class
VolatileMemAllocator
> The current implementation of class VolatileMemAllocator does not support
retrieval operations so it is not possible to temporarily forget cached durable
objects efficiently like class NonVolatileMemAllocator does, logically,
volatile memory should be retrievable for durable object graphs in a
applications/frameworks run-time session.
> In addition, durable native computing must based on retrievable
interface, therefore the VolatileMemAllocator should implement retrievable
interface to support forgettable object graphs and durable native computing.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lcy0816/incubator-mnemonic master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-mnemonic/pull/19.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #19
----
commit d0975c9f16c9928582c77b90f24a78b24f6282d8
Author: lcy0816 <lcy0...@hotmail.com>
Date: 2016-08-31T23:34:36Z
MNEMONIC-60:Apply Transaction, Retrievable interfaces to class
VolatileMemAllocator
----
> Apply Transaction, Retrievable interfaces to class VolatileMemAllocator
> -----------------------------------------------------------------------
>
> Key: MNEMONIC-60
> URL: https://issues.apache.org/jira/browse/MNEMONIC-60
> Project: Mnemonic
> Issue Type: New Feature
> Components: Computing-Service, Core
> Affects Versions: 0.2.0-incubating
> Reporter: Wang, Gang
> Assignee: Chenyang Li
> Fix For: 0.3.0-incubating
>
>
> The current implementation of class VolatileMemAllocator does not support
> retrieval operations so it is not possible to temporarily forget cached
> durable objects efficiently like class NonVolatileMemAllocator does,
> logically, volatile memory should be retrievable for durable object graphs in
> a applications/frameworks run-time session.
> In addition, durable native computing must based on retrievable interface,
> therefore the VolatileMemAllocator should implement retrievable interface to
> support forgettable object graphs and durable native computing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
