close Warning: Failed to sync with repository "(default)": [Errno 12] Cannot allocate memory; repository information may be out of date. Look in the Trac log for more information including mitigation strategies.
Modify ↓

Opened at 2006-08-26T10:44:22Z

Last modified at 2007-02-18T20:52:13Z

#199 closed enhancement (fixed)

Jabber protocol should use SRV records to find the server

Reported by: berni@… Owned by:
Priority: wishlist Milestone:
Component: Jabber Version: 1.0.3
Keywords: Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro:

Description

bitlbee tries to resolve the domain part of the jabber username and connect there directly. It should rather try to use _xmpp-client._tcp.domain SRV record (see RFC2782 for SRV records)

Attachments (0)

Change History (2)

comment:1 Changed at 2006-08-27T20:54:03Z by wilmer

It indeed should, and I intend to fix that in the new Jabber module (#9). I already did some research about how to do it exactly, and it seems libresolv allows one to do this without affecting portability too much.

Fortunately with any recent version of BitlBee you can at least specify the right servername by hand. So this is fortunately indeed a wishlist bug. :-)

comment:2 Changed at 2006-10-07T22:45:59Z by wilmer

I just added code for this to the new Jabber module, which can be found at: ​http://code.bitlbee.org/wilmer/new-jabber/

Seems to work pretty well. :-) It doesn't handle the priority- and weight values (yet?) because this is not really trivial to implement in a program that does all I/O asynchronously. (Has to save states, lists of hosts it tried so far, stuff like that. To be honest I don't feel like doing all that...)

Modify Ticket

Action
as closed The ticket will remain with no owner.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.