<li>Don&#x27;t we set the session variable to resp.cookies? And can&#x27;t we also create a session object to do sessions? One of the readings mentioned that. What are the differences between the answer options for Q3?
<div class="ans">
<p>Here's the question again:</p>
<pre>How do we do sessions using the requests module?
a. create a session object
b. set the session variable
c. create a cookie
d. send back cookies it sent us
</pre>
<p>For (a) and (b) there is a session object (variable) in Flask, but not in the <code>Requests</code> module. You only have the cookies to work with.
<p>For (c), it's the cookie created by Flask that really holds our session information.
<p>So the answer is (d).
</div></li>

<li>How would we handle multiple concurrent requests to the same server using the requests module, and would that cause any threading issues? Also what&#x27;s the difference between using resp.text and resp.json()?
<div class="ans">
    <p>What a great question! Yes, we could combine threading and the requests module to do asynchronous requests. Very clever!
    <p>If they were all to the same server, we would definitely be
    stress-testing its handling of concurrency. We might not gain much
        in speed/latency depending on where the bottlenecks are.
    <p>If they were to different servers (some kind of web crawler),
    then we might gain a lot in concurrency.
</div></li>