On 12-07-16 08:20 , Patrick McManus wrote:
On Mon, 2012-07-16 at 11:07 +1000, Mark Nottingham wrote:
I suppose this could be mitigated by making it a boolean; i.e. if any of the
HTML on a site has the boolean flag, go look in the well-known location (and
remember that that site has a hints file).
This would remove the unnecessary requests without making things *too* complex
(although personally I dislike the two-step, as well as the dependency on HTML…
I suppose it could be HTML OR a header…).
Thoughts?
that's kind of how I was seeing it.. just a bool sign that any origins
referenced in this transaction or related sub resource transactions can
be checked for hints.. I'd probably just make it a sticky bit on the
internal host entry.
If all that's needed is a bool, does it make sense to define a new DNS
record type for this sort of thing? It seems like a pretty near-perfect
fit to me. It can be prefetched at DNS resolution time, so that all
connections to the host are optimized, and you don't have to make a
transaction (and parse the HTML) to then realize that other connections
to the site can be optimized. It eliminates the potential minefield of
different pages pointing to different hint files, and caching semantics
could be maintained either at the HTTP request level or by putting
something in the DNS record value. It shouldn't be that hard to deploy
either.
kats
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
