Files.com 1.4.197__tar.gz → 1.4.199__tar.gz

{Files.com-1.4.197 → Files.com-1.4.199}/Files.com.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 1.2
 Name: Files.com
-Version: 1.4.197
+Version: 1.4.199
 Summary: Python bindings for the Files.com API
 Home-page: UNKNOWN
 License: MIT

{Files.com-1.4.197 → Files.com-1.4.199}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 1.2
 Name: Files.com
-Version: 1.4.197
+Version: 1.4.199
 Summary: Python bindings for the Files.com API
 Home-page: UNKNOWN
 License: MIT

{Files.com-1.4.197 → Files.com-1.4.199}/README.md

@@ -39,12 +39,14 @@ To initiate a support conversation, you can send an [Authenticated Support Reque
 
 ## Authentication
 
+There are two ways to authenticate: API Key authentication and Session-based authentication.
+
 ### Authenticate with an API Key
 
 Authenticating with an API key is the recommended authentication method for most scenarios, and is
 the method used in the examples on this site.
 
-To use the API or SDKs with an API Key, first generate an API key from the [web
+To use an API Key, first generate an API key from the [web
 interface](https://www.files.com/docs/sdk-and-apis/api-keys) or [via the API or an
 SDK](/python/resources/developers/api-keys).
 
@@ -63,14 +65,14 @@ Don't forget to replace the placeholder, `YOUR_API_KEY`, with your actual API ke
 
 ### Authenticate with a Session
 
-You can also authenticate to the REST API or SDKs by creating a user session using the username and
+You can also authenticate by creating a user session using the username and
 password of an active user. If the user is an administrator, the session will have full access to
-the entire API. Sessions created from regular user accounts will only be able to access files that
+all capabilities of Files.com. Sessions created from regular user accounts will only be able to access files that
 user can access, and no access will be granted to site administration functions.
 
-API sessions use the exact same session timeout settings as web interface sessions. When an API
+Sessions use the exact same session timeout settings as web interface sessions. When a
 session times out, simply create a new session and resume where you left off. This process is not
-automatically handled by SDKs because we do not want to store password information in memory without
+automatically handled by our SDKs because we do not want to store password information in memory without
 your explicit consent.
 
 #### Logging In
@@ -109,6 +111,8 @@ session.destroy()
 
 ## Configuration
 
+Global configuration is performed by setting atttributes on the `files_sdk` object.
+
 ### Configuration Options
 
 #### Base URL
@@ -155,7 +159,7 @@ files_sdk.open_timeout = 60
 
 #### Read Timeout
 
-Read timeout in seconds. The default value is 80.
+Read timeout in seconds. The default value is 60.
 
 ```python title="Example setting"
 files_sdk.read_timeout = 90

{Files.com-1.4.197 → Files.com-1.4.199}/files_sdk/__init__.py

@@ -208,7 +208,7 @@ session_id = None
 source_ip = None
 base_url = "https://app.files.com"
 base_path = "api/rest/v1"
-version = "1.4.197"
+version = "1.4.199"
 
 __version__ = version