[Ietf-caldav] Notifications [was Re: Client work]
Mike Shaver
mike.shaver at gmail.com
Fri Aug 13 09:57:50 PDT 2004
On Fri, 13 Aug 2004 09:06:24 -0700, Lisa Dusseault
<lisa at osafoundation.org> wrote:
> It's my opinion that we can do much better than HTTP for notifications
> if we're willing to work a little harder!
That sounds pretty good, though I think one of the great things about
an HTTP-driven protocol is the firewall-transit capabilities. Perhaps
we can use corkscrew[1]-like techniques to establish a long-lived XMPP
connection over an HTTP proxy, but I would be much happier to see some
sort of "what's new since [opaque server token returned at last update
fetch]?" poll command included as well, similar to the POP extensions
along those lines.
Strong language to encourage clients to use XMPP with HTTP layering
before falling back on polling would be very welcome in the standard,
of course, but I think it's important to be able to get some sort of
periodic update even if you can only use HTTP for a given
configuration.
[1]: http://www.agroman.net/corkscrew/
Mike
More information about the Ietf-caldav
mailing list