<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 5/3/18 11:50 AM, Cantor, Scott
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:9846A6064BD102419D06814DD0D78DE14A01ED96@CIO-TNC-D2MBX02.osuad.osu.edu">
<blockquote type="cite">
<pre wrap="">It is 'none', if one is using the default internally-constructed HttpClient.
Because of the 1) memory requirements of in-memory and 2) disk
requirements of disk, we didn't want to make assumptions about either of
those defaults being ok.
</pre>
</blockquote>
<pre wrap="">
And because they do their own caching, I believe. I think there was internal logic already to remember a cache tag and use it, just not across restarts</pre>
</blockquote>
<br>
That's true, the HTTP batch ones cache ETag and Last-Modified, so
they can do conditional GETs. They don't however cache the actual
response data, so it's a little different than HttpClient "native"
memory or disk caching.<br>
<br>
<blockquote type="cite"
cite="mid:9846A6064BD102419D06814DD0D78DE14A01ED96@CIO-TNC-D2MBX02.osuad.osu.edu">
<pre wrap="">We didn't need the HttpClient's support for the batch case.
</pre>
</blockquote>
Yes. It probably also makes less sense to do for batch since the
files are very large and you probably on average request/refresh
them less often than you would with dynamic, where you have lots of
smaller files that you might want to (re)fetch more frequently. But
it's an option if people want it.<br>
</body>
</html>