[snip]
> 
> Note that HTTPSocket is going away - since mir's Network 
> rewrite, the proper way to implement protocols is to use 
> Clients. So a better direction might be to help implement the 
> HTTPClient for the new framework in a way that can be 
> controlled so that the problem you describe doesn't happen.
> 
> I'm not sure whether Michael still intends to implement 
> HTTPClient on his own
[snip]

FYI, I asked Michael about this a few days ago; he said:

"I took [HTTP migration to network rewrite] out as too many
modifications and innovations are happening 
in Comanche and Seaside in that area.  And it won't really help to just
rewrite the HTTPSocket. The URI package 
came out of the initial attempt to rewrite the HTTP related stuff."