Hmm, after a little thought, it seems like an even smoother solution would be
to leave pre-fetching up to the server completely. I.e., if someone requests
a page from my server, I return to them not only that page but the first n
bytes (or all) of each subpage in a multipart message. That leaves it up to
me, the page designer/server administrator, to decide exactly what parts of
my site can be optimized in such a way, and it lets me tune the prefetching
algorithms to my liking.
It may be both a protocol and UI challenge to model the act of a server
"throwing" unrequested content at a client... perhaps left for HTTP-NG?
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
[email protected] [email protected] http://www.[hyperreal,organic].com/