<p>Probably better suited for the mailing list. Also have a look at the <a href="http://arxiv.org/pdf/1406.4806v1.pdf" rel="nofollow">paper</a> for some of these topics.</p>

<blockquote>
  <p>When/how do sessions expire?</p>
</blockquote>

<p>The default expiration for temporary sessions in the server implementation is 24h.</p>

<blockquote>
  <p>Can session expire time be configured on the server?</p>
</blockquote>

<p>You could edit the <code>/usr/lib/opencpu/scripts/cleanocpu.sh</code> script, which get triggered through <code>/etc/cron.d/opencpu</code>. But if you want persistence it is usually better to store things in a database (RMySQL, mongolite, etc) or in a package on the server, or in the client.</p>

<blockquote>
  <p>Can session expire time be changed at runtime?</p>
</blockquote>

<p>No, expiration of resources is up to the server.</p>

<blockquote>
  <p>Are sessions saved on-disk or in-memory?</p>
</blockquote>

<p>The current implementation saves on disk (with a bit of in-memory cache), but the API is agnostic.</p>

<blockquote>
  <p>Do sessions work with the nginx opencpu proxy?</p>
</blockquote>

<p>Yes, they are no different than anything else on the server.</p>
Sessions in OpenCPU: what are the specifics?
<p>After reading <a href="https://www.opencpu.org/posts/opencpu-release-1-4-4/" rel="nofollow">this blog post on OpenCPU</a>, I have questions about Sessions:<br>
* when/how do sessions expire?<br>
* can session expire time be configured on the server?<br>
* can session expire time be changed at runtime?<br>
* are sessions saved on-disk or in-memory?<br>
* do sessions work with the nginx opencpu proxy?</p>

<p>Thanks in advance!</p>