Chrome changes to support cached form submissions....

Chrome changes to support cached form submissions.

The solution is to add a user-defined identifier to UploadData.
If that identifier is set, and if the request method is POST,
then HttpCache will enable caching for the response.  (The cache
key will be a composition of the identifier and the URL.)  A
subsequent POST request to the same URL with the same identifier
will "hit" the previously generated cache entry.  Reuse from the
cache is subject to all of the standard rules.

For reference, here are the corresponding net changes:
http://codereview.chromium.org/52028

Here are the corresponding WebKit changes:
http://trac.webkit.org/changeset/41919

BUG=2636
R=sky

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=12485

[sky, 2009-03-24 20:34:40]

LGTM with one suggestion.

http://codereview.chromium.org/52040/diff/2019/1010
File webkit/glue/glue_serialize.cc (right):

http://codereview.chromium.org/52040/diff/2019/1010#newcode90
Line 90: int64 tmp;
should you set this to 0, just in case ReadInt64 fails? I guess same comment for
ReadInteger.

[darin (slow to review), 2009-03-24 21:12:15]

http://codereview.chromium.org/52040/diff/2019/1010
File webkit/glue/glue_serialize.cc (right):

http://codereview.chromium.org/52040/diff/2019/1010#newcode90
Line 90: int64 tmp;
Good idea!