The key for a cached
Token2.0 comes from hashing the endpoint, app, and
scopes. For the
Gargle2.0 subclass, the identifier or key is expanded to
include the email address associated with the token. This makes it easier to
work with Google APIs with multiple identities.
Gargle2.0 tokens are cached, by default, below
"~/.R/gargle/gargle-oauth", i.e. at the user level. In contrast, the
default location for
./.httr-oauth, i.e. in current working
Gargle2.0 behaviour makes it easier to reuse tokens across
projects and makes it less likely that tokens are accidentally synched to a
remote location like GitHub or DropBox.
Gargle2.0 token is cached in its own file. The token cache is a
directory of such files. In contrast,
Token2.0 tokens are cached as
components of a list, which is typically serialized to
An R6 class object.