Thanks for the pointer re: Safari. I'll fix that. What this is doing is twofold: letting HTTP push be used consistently, with long-polling pushed out to the ed

Thanks for the pointer re: Safari. I'll fix that. What this is doing is twofold: letting HTTP push be used consistently, with long-polling pushed out to the edges of the network, where it belongs; and making it less of a burden to spin up and shut down HTTP-based services. The registration and management aspect -- enrollment, in short -- is to HTTP as DHCP is to IP, if you like. It lets you avoid the equivalent of manually assigning IP numbers.