cmpil...@apache.org wrote on Wed, Aug 03, 2011 at 14:00:39 -0000: > + (As an aside, Serf's potential as a platform for future > + improvement remains unproven and doubtful. For example, HTTPv2 > + removes canonical resource URLs, which works against the caching > + proxy concept that seems to be the strongest argument in favor of > + Serf's approach. But that's not strictly germane here.)
That sounds odd for caching not to be taken into consideration in HTTPv2's design. And glancing at the httpv2 design notes suggests that it was explicitly a goal. Are you saying that somehow HTTPv2 actually made the cacheability situation worse in some cases? Or just that it doesn't make the situation as as good as it promised to?
