[squeak-dev] Server timeouts and 504 return codes

Tobias Pape Das.Linux at gmx.de
Mon Jan 28 08:13:42 UTC 2019

> On 28.01.2019, at 04:04, Chris Muller <ma.chris.m at gmail.com> wrote:
>> But the caching scheme I described in this thread would make the UX a lot
>> quicker too, because data would not have to be transferred when you
>> already have it.
> I assume you mean "data would not have to be transferred" from andreas
> to alan... from within the same data center..!   :)

No, that is not the point. When nginx knows the data that the image wants, and the image says so, it just can answer 304 not modified and does not send anything. Thats extremely handy.
Also, we know that the data center is not the limiting factor here but (server-side) squeak is.


More information about the Squeak-dev mailing list