Chris Dennis
unread,Apr 29, 2015, 5:39:28 PM4/29/15Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jsr...@googlegroups.com
Hi All,
As I discussed in the thread on the new async branch, I think it would be
a good idea to try and organize a BoF session at JavaOne to discuss the
future direction(s) and features that should or might be included in a
JCache 2.0 JSR. As such I had planned on trying to do a decent job of
proposing something today so that it would be in before the JavaOne
deadline. Now that the deadline has been extended until May 6th however
it would appear there is time to attempt to get something hashed out on
the list so that it represent everyones thoughts as well as is possible.
This is what I currently have:
Title: Jcache 2.0 : Where do we go from here?
Abstract (721 characters):
The Java caching standard (JSR-107) was finally released in 2014 after 13
years of on-and-off work. The caching community has already started to
move on, however. There is already discussion of what is missing from the
current standard, and what could or should be included in a JCache 2.0.
The JSR-107 Specification Leads and Expert Group members would like to
engage the community in an open discussion on JCache 2.0. What important
features are missing from JSR-107? What usecases should a future JCache
2.0 support? What features would be required to support those usecases?
Attend, get your voice heard, and engage directly with the rest of the
caching community to help define the genesis of a JCache 2.0 standard.
Presentation Summary (this is only visible to the program committee):
The JSR-107 standard was pushed through to final in 2014, but many among
the spec leads, expert group and engaged community were unhappy that many
features had to be ignored or abandoned in order to achieve
standardization in a reasonable timeline. There is desire amongst the
community to start work on a version 2.0 of the API that includes many of
these feature that were left out of scope in 107, and potentially other
features that would allow for a richer specification overall. Examples of
features that are being discussed or considered by various parties are:
asynchronous operations, richer distributed caching support, capacity
constraints, and (XA) transactions. We, the JSR-107 Spec Leads and EG
would like to use this BOF slot as an opportunity to engage with
interested members of the community to help define a strong and cohesive
high level direction for JCache 2.0.
I’d be interested in any input people have to help refine what I’ve
started with, or even just +1’s if you agree so that I can more honestly
use the term “caching community”.
Thanks,
Chris Dennis
Terracotta/Software AG EG Member