There's an HTTP extensions mechanism proposal at
<URL:http://www.ics.uci.edu/pub/ietf/http/draft-kristol-http-extensions-00.txt>
This is seen as preferable to adding "X-" headers when one wishes to
extend the capabilities of HTTP - it also gives the browser and server
the power to negotiate based on capabilities. (i.e. "Can you do this?"
"No, I can't" "Then I won't waste time and bandwidth sending you this
info.")
But I suppose for the time being there's nothing wrong with encoding it
as X-Geolocation: 118 24 34 21 34 43 or something, while we're
experimenting. I think at this point one should look at Mark Pesce's CP
proposal, at <URL:http://hyperreal.com/~mpesce/www.html>.
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
[email protected] [email protected] http://www.hotwired.com/Staff/brian/