I think you will agree that HTTP requires a reliable transport (ie dropped
packet recovery) and, whenever the requested object is more than modest size,
flow control.
Pushing these functions up into the network application layer (ie libwww)
seems inappropriate and asking for trouble. Afterall, its all that TCP
really does.
Maybe the connection overhead concerns can be solved another way such
as with MGET, lookahead, smarter caching etc. ?
On the otherhand, it might be reasonable to implement HEAD with a datagram
if that would help.
Mike
-----------------------------------------------
Michael A. Dolan <mailto:miked@cerf.net>
TerraByte Technology (619) 445-9070, FAX -8864