Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AppEngineCredentialStore should use MemcacheService #47

Closed
wonderfly opened this issue Jan 9, 2015 · 11 comments
Closed

AppEngineCredentialStore should use MemcacheService #47

wonderfly opened this issue Jan 9, 2015 · 11 comments
Assignees
@wonderfly
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@wonderfly
Copy link
Contributor

From yan...@google.com on July 12, 2012 13:40:49

External references, such as a standards document, or specification? http://javadoc.google-oauth-java-client.googlecode.com/hg/1.10.1-beta/com/google/api/client/extensions/appengine/auth/oauth2/AppEngineCredentialStore.html https://developers.google.com/appengine/docs/java/javadoc/com/google/appengine/api/memcache/MemcacheService Java environments (e.g. Java 6, Android 2.3, App Engine, or All)? App Engine Please describe the feature requested. Implement CachedAppEngineCredentialStore that extends AppEngineCredentialStore and uses com.google.appengine.api.memcache.MemcacheService to store credential information in the memcache.

Original issue: http://code.google.com/p/google-oauth-java-client/issues/detail?id=47
@wonderfly wonderfly added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. imported priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Jan 9, 2015
@wonderfly wonderfly self-assigned this Jan 9, 2015
@wonderfly
Copy link
Contributor Author

From yan...@google.com on July 14, 2012 04:43:59

Status: Accepted
Cc: -mlin...@google.com

@wonderfly
Copy link
Contributor Author

From yan...@google.com on July 26, 2012 07:39:54

Labels: -Milestone-Version1.11.0 Milestone-Version1.12.0

@wonderfly
Copy link
Contributor Author

From yan...@google.com on September 26, 2012 05:18:29

Owner: ngmic...@google.com
Cc: rmis...@google.com
Labels: -Milestone-Version1.12.0 Milestone-Version1.13.0

@wonderfly
Copy link
Contributor Author

From yan...@google.com on December 01, 2012 09:31:43

Labels: -Milestone-Version1.13.0 Milestone-Version1.14.0

@wonderfly
Copy link
Contributor Author

From yan...@google.com on January 23, 2013 22:29:43

Labels: -Milestone-Version1.14.0 Milestone-Version2.1.0

@wonderfly
Copy link
Contributor Author

From yan...@google.com on February 06, 2013 16:05:32

Labels: -Milestone-Version2.1.0 Milestone-Version1.16.0

@wonderfly
Copy link
Contributor Author

From yan...@google.com on April 19, 2013 18:51:48

Owner: yan...@google.com
Cc: -rmis...@google.com pele...@google.com ngmic...@google.com
Labels: -Milestone-Version1.16.0 Milestone-Version1.15.0

@wonderfly
Copy link
Contributor Author

From yan...@google.com on April 20, 2013 06:34:29

Why don't we just directly add MemcacheService into AppEngineStore by default. We can perhaps provide an option in the Builder to disable the memcache if the developer really doesn't want it.

Summary: AppEngineCredentialStore should use MemcacheService (was: CachedAppEngineCredentialStore that uses MemcacheService)
Owner: pele...@google.com
Cc: -pele...@google.com yan...@google.com

@wonderfly
Copy link
Contributor Author

From yan...@google.com on April 22, 2013 14:28:29

Labels: -Milestone-Version1.15.0 Milestone-Version1.16.0

@wonderfly
Copy link
Contributor Author

From yan...@google.com on June 10, 2013 06:18:12

https://codereview.appspot.com/9881043

Status: Started

@wonderfly
Copy link
Contributor Author

From yan...@google.com on June 18, 2013 17:22:01

Status: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wonderfly wonderfly

Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wonderfly