Streaming and backend conditional requests

[Geoff Simmons]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/12/12 06:29 PM, Artur Bergman wrote:
> I have no idea why all this complexity exist, and I have no idea why it is exposed to VCL.
> 
> It seems to me that an IMS patch can be fairly transparent, and very very simple.

Fair enough. But actually the considerations here don't involve VCL at all.

One way or another, streaming and IMS will want to co-exist in Varnish.
We could avoid the complexity by leaving it as it is now -- then IMS
will never attempt to validate an object while it's still streaming.

But it doesn't seem unreasonable to want to take advantage of IMS to
avoid fetching a large object that Varnish already has. Especially when
new streaming arrives, which IIUC aims to make a streaming object
available to more than one client at a time.

If we want to have that, then the simple solution in place now won't
work. We'll have to work out how IMS interacts with streaming and
storage. Any working solution that keeps things simple would certainly
be preferable.


Best,
Geoff
- -- 
** * * UPLEX - Nils Goroll Systemoptimierung

Schwanenwik 24
22087 Hamburg

Tel +49 40 2880 5731
Mob +49 176 636 90917
Fax +49 40 42949753

http://uplex.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJPDyeiAAoJEOUwvh9pJNURtq4P/1soeHZb7ROz6rkmrZ8wigvE
ti4KMybz0rz7gYfDMtj57Bra3+Ti2Pig5mrN9eHNMsPwOFprrXy8kI6f/akRHKLh
JbaPuEH3QMqPC68AdNyExyt6nkbFy4LkzcZ+qmq3r5LN3GSM7jF2gXXiuvQmdAce
NWwqg58HD9BqyOBjQ/hC4Wp0SfGUaCQPslSBebk2W6m6r4/6tE/+tPMjtj2ROHRj
yaM/7CzBVunqzCmZs+JkjNGNE2kF11/LIBAQbeeap4R70iXmgmiPcZnlsDAxBIbx
17iMFBPoFNVXRhaEAv5GGbob5AoQzcHUtKY1oyYrjlN2dFzcy7bzYxoenBMwSTOf
8SuJDw88PkSl58dq65GJj0WHX68eeW95lOa4ZN/tIFOIvrnHN8GvQYCoe5Gjskrf
UdOqdlrrai8rBXtIJS/JaWcIGhxeowdoFJAYPmoJr2dlAih8hRrLgOKepB1QDeMm
ijWhCH72Oapb0rW7I1mHSPRllQyou9IqbjS4G+SNr1UW78d8y+X+ZkHmlzI+DE44
9C6mQXKj3zsscejl1u8j1rc04t/kwvAZDsb8+g0rXtw7Qch/A+bL0Tv+Fp/pAV8M
YLK9aVG5nXgB4Ht5s2o279pUMJlOU98ROD+IfrYfnnL1WzpkgqchcDCCXtEeuFgx
q0jPAdHpekVNDO5Je1zF
=1rZP
-----END PGP SIGNATURE-----