Opened at 2007-06-13T16:39:54Z
Closed at 2008-01-06T13:44:20Z
#294 closed enhancement (fixed)
Support for XMPP ping, XEP 0199
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | wishlist | Milestone: | |
| Component: | Jabber | Version: | devel |
| Keywords: | ping | Cc: | |
| IRC client+version: | Client-independent | Operating System: | Linux |
| OS version/distro: |
Description
Here is a patch against the release branch ( http://code.bitlbee.org/bitlbee/ ) to handle xmpp ping reply part of http://www.xmpp.org/extensions/xep-0199.html .
Attachments (2)
Change History (6)
Changed at 2007-06-13T16:42:09Z by
| Attachment: | bitlbee.support_ping.diff added |
|---|
comment:1 Changed at 2007-06-16T14:02:39Z by
The previous patch was incomplete, i have redone one against new jabber branch ( http://code.bitlbee.org/wilmer/new-jabber/ ). I have added a check on namespace, and the dicovery support.
comment:2 Changed at 2007-06-16T15:07:21Z by
Oh, this is so depressing .... what's the deal with those XMPP guys?
Every damn <iq> packet contains a <query> element so you can just read its xmlns attribute to see what to do it. But no, for pings it has to use a special <ping> tag. DRUGS ARE BAD, MMMKAY?
But thanks for the patch. I know you didn't invent the standard. ;-) Which clients send this kind of requests so far and why? Haven't heard of this before...
comment:3 Changed at 2007-06-16T16:35:13Z by
So far, no client or server send it. I have seen some server (jabberd14, or ejabberd, i am not sure) that send new line to keep connection alive, or to check the client is still here, but that not really good.
I proposed the patch because no one will use the xep if no client support it ( chicken and egg problem ).
comment:4 Changed at 2008-01-06T13:44:20Z by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This was actually submitted in changeset:devel,288
patch for xep-0199