Menu
Sometimes I see people invoke web API using requests.Session object:
client = requests.session() resp = client.get(url='...') But sometimes they don't:
resp = requests.get(url='...') Can somebody explain when should we use Session and when we don't need them?
620
So "request. session. get("name",False):" statement returns the value of the 'name' items if it exists in the session if it doesn't then a default of False is returned.
The get() method sends a GET request to the specified url.
Unlike cookies, Session (session) data is stored on the server. The session is the interval at which the client logs on to the server and logs out the server. The data that is required to be saved in the session is stored in a temporary directory on the server.
We specify the stream = True in the request get method. This allows us to control when the body of the binary response is downloaded.
Under the hood, requests.get() creates a new Session object for each request made.
By creating a session object up front, you get to reuse the session; this lets you persist cookies, for example, and lets you re-use settings to be used for all connections such as headers and query parameters. To top this all off, sessions let you take advantage of connection pooling; reusing connections to the same host.
See the Sessions documentation:
The Session object allows you to persist certain parameters across requests. It also persists cookies across all requests made from the Session instance, and will use urllib3‘s connection pooling. So if you’re making several requests to the same host, the underlying TCP connection will be reused, which can result in a significant performance increase (see HTTP persistent connection).
95
To quote the documentation
The Session object allows you to persist certain parameters across requests. It also persists cookies across all requests made from the Session instance.
45
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
