interesting... beaconpush actually offers pretty much exactly what I'm
looking for.

There's just one big problem, that the Channels API (and probably
beaconpush as well) have for me: I'm working on a security-focused service,
and the last thing that I can afford to do is have my page open random
non-https requests to any domains other than the one from the main page.
Especially not TALKGADGET.google.com. Even though "beaconpush.com" already
sounds a lot less gossipy, I still don't think it would be a good idea. At
least I would find such a page highly suspicious if I cared about my data
being safe with them. Even including external javascript libraries is
something I'd really like to avoid.

--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/3SUBVUny9a0J.
To post to this group, send email to google-appengine@xxxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to
google-appengine+unsubscribe@xxxxxxxxxxxxxxxxx
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.