gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GORA-409) JCache Datastore
Date Fri, 05 Aug 2016 09:18:20 GMT

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

Lewis John McGibbney commented on GORA-409:

Whenever you submit a pull request at the Apache Software Foundation via Github, our workflow
is that you make a branch with the issue number you log over at the Apache Jira. That way,
the Github hooks make sure that the traffic is forwarded towards the Gora community on dev@gora.
Does that make sense?
I am merging your code and testing it now. I will update here shortly.

> JCache Datastore
> ----------------
>                 Key: GORA-409
>                 URL: https://issues.apache.org/jira/browse/GORA-409
>             Project: Apache Gora
>          Issue Type: Sub-task
>            Reporter: Alparslan Avcı
>            Assignee: Kevin Ratnasekera
>              Labels: gora-jcache, gsoc2016, jcache
>             Fix For: 0.8
>         Attachments: JavaCaching.pdf
> Implementation of JCache datastore. 
> According to the [JSR-107|https://jcp.org/en/jsr/detail?id=107], the JCache caching API
is specified by the Java Community Process (JCP). JCache datastore should be implemented to
provide usage of any JCache provider like Hazelcast.

This message was sent by Atlassian JIRA

View raw message