it wouldn't really be useful to send the guid in an HTTP header. pushing works (as i understand it) by the clients storing tables of who routed them what GUID.. so, if i send a browse-host push-request to any of my connections, they haven't necessarily seen the GUID of this host, and the push request would be rather futile.

that said, sending the browse-host status would be useful... but i didn't want to get into specs and also because there's a lot of hosts on the network that currently do support browse-host but wouldn't send the header. maybe in the future the header will be added, and after a bit of time when it settles in, it'll make more sense to look at the header instead of something else.