You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sdk/core/azure-core/README.md
+26-19Lines changed: 26 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@
4
4
5
5
## Pipeline
6
6
7
-
The Azure Core pipeline is a re-strucuting of the msrest pipeline introduced in msrest 0.6.0.
7
+
The Azure Core pipeline is a re-structuring of the msrest pipeline introduced in msrest 0.6.0.
8
8
Further discussions on the msrest implementation can be found in the [msrest wiki](https://github.com/Azure/msrest-for-python/wiki/msrest-0.6.0---Pipeline).
9
9
10
10
The Azure Core Pipeline is an implementation of chained policies as described in the [Azure SDK guidelines](https://github.com/Azure/azure-sdk/tree/master/docs/design).
11
11
12
-
The Python implementation of the pipeline has some mechanisms specific to Python. This is due to the fact that both synchronous and asynchronous implementations of the pipeline must be supported indepedently.
12
+
The Python implementation of the pipeline has some mechanisms specific to Python. This is due to the fact that both synchronous and asynchronous implementations of the pipeline must be supported independently.
13
13
14
14
When constructing an SDK, a developer may consume the pipeline like so:
15
15
@@ -22,26 +22,28 @@ from azure.core.pipeline.policies import (
For asynchronous pipelines a couple of transport options are available. Each of these transports are interchangable depending on whether the user has installed various 3rd party dependencies (i.e. aiohttp or trio), and the user
154
-
should easily be able to specify their chosen transport. SDK developers should use the `aiohttp` transport as the default for asynchronous pipelines where the user has not specified as alternative.
158
+
should easily be able to specify their chosen transport. SDK developers should use the `aiohttp` transport as the default for asynchronous pipelines where the user has not specified an alternative.
155
159
```
156
160
from azure.foo.aio import FooServiceClient
157
161
from azure.core.pipeline.transport import (
158
-
# Identical implementation as the synchronous RequestsTrasport wrapped in an asynchronous using the
162
+
# Identical implementation as the synchronous RequestsTransport wrapped in an asynchronous using the
159
163
# built-in asyncio event loop.
160
164
AsyncioRequestsTransport,
161
165
162
-
# Identical implementation as the synchronous RequestsTrasport wrapped in an asynchronous using the
166
+
# Identical implementation as the synchronous RequestsTransport wrapped in an asynchronous using the
163
167
# third party trio event loop.
164
168
TrioRequestsTransport,
165
169
@@ -176,16 +180,19 @@ Some common properties can be configured on all transports, and can be set on th
176
180
classConnectionConfiguration(object):
177
181
"""Configuration of HTTP transport.
178
182
179
-
:param connection_timeout: The connect and read timeout value, in seconds. Default value is 100.
180
-
:param verify: SSL certificate verification. Enabled by default. Set to False to disable, alternatively
181
-
can be set to the path to a CA_BUNDLE file or directory with certificates of trusted CAs.
182
-
:param cert: Client-side certificates. You can specify a local cert to use as client side certificate, as a single file (containing the private key and the certificate) or as a tuple of both files’ paths.
183
+
:param int connection_timeout: The connect and read timeout value. Defaults to 100 seconds.
184
+
:param bool connection_verify: SSL certificate verification. Enabled by default. Set to False to disable,
185
+
alternatively can be set to the path to a CA_BUNDLE file or directory with certificates of trusted CAs.
186
+
:param str connection_cert: Client-side certificates. You can specify a local cert to use as client side
187
+
certificate, as a single file (containing the private key and the certificate) or as a tuple of both files' paths.
188
+
:param int connection_data_block_size: The block size of data sent over the connection. Defaults to 4096 bytes.
0 commit comments