openstack/python-keystoneclient
Code Issues Proposed changes

Correct typos in using-sessions

Browse Source 
Fixed typos in using-sessions.

Change-Id: Id931bfdb8eb8bf214ca538673e727c6bf1e06280
This commit is contained in:
Brant Knudson
2014-10-10 19:16:43 -05:00
parent 89dc951f7d
commit 3cf7f94815
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/using-api-v2.rst
View File

@@ -13,7 +13,7 @@ The main concepts in the Identity v2 API are:
* services
* endpoints
The client v2 API lets you query and make changes through
The V2 client API lets you query and make changes through
managers. For example, to manipulate tenants, you interact with a
``keystoneclient.v2_0.tenants.TenantManager`` object.

10
doc/source/using-sessions.rst
View File

@@ -75,13 +75,13 @@ fashion by passing the Session object to the client's constructor.
Migrating keystoneclient to use a Session
-----------------------------------------
By using a session with a keystonclient Client we define that you have opted in
to new behaviour defined by the session. For example authentication is now
on-demand rather than on creation. To allow this change in behaviour there are
a number of functions that have changed behaviour or are no longer available.
By using a session with a keystoneclient Client we presume that you have opted
in to new behavior defined by the session. For example authentication is now
on-demand rather than on creation. To allow this change in behavior there are
a number of functions that have changed behavior or are no longer available.
For example the
:py:meth:`keystoneclient.httpclient.HTTPClient.authenticate` command used
:py:meth:`keystoneclient.httpclient.HTTPClient.authenticate` method used
to be able to always re-authenticate the current client and fetch a new token.
As this is now controlled by the Session and not the client this has changed,
however the function will still exist to provide compatibility with older