Irssi core bugs

Notice: Undefined index: tasklist_type in /var/www/ : eval()'d code on line 85 Notice: Undefined index: tasklist_type in /var/www/ : eval()'d code on line 90
  • Status Unconfirmed
  • Percent Complete
  • Task Type Feature Request
  • Category core
  • Assigned To No-one
  • Operating System Linux
  • Severity Low
  • Priority Normal
  • Reported Version Irssi SVN
  • Due in Version Undecided
  • Due Date Undecided
  • Votes 0
  • Private No
Attached to Project: Irssi core bugs
Opened by Michael Stapelberg (stapelberg) - 2013-11-27

FS#908 - [PATCH] support SRV records specifies SRV records, which (in the case of IRC) look like _irc._tcp.domain, e.g. An SRV record specifies a priority, a weight, a hostname and a port (!), e.g.:

host -t SRV has SRV record 0 0 6667 has SRV record 0 0 6667

This is really handy if you want to run IRC on non-standard ports or just don’t want to bother with configuring SSL ports, which often differ from IRC network to IRC network. Furthermore, it clearly defines an order (by priorities), whereas just pointing one DNS record to multiple IP addresses is round-robin.

The attached patch is a work-in-progress which makes irssi use glib’s asynchronous DNS resolver to first resolve an SRV record, and fall back to normal DNS resolution if that is not possible.

I will continue working on this patch, but I’d like some things clarified first please:

1) Will you merge that patch at all, i.e. are you okay with irssi SRV-resolving?
2) Can we ignore the resolve_prefer_ipv6 setting? Then we could use GSocketConnectable and simplify the code even further.
3) Are there any big style guide violations, architectural problems or other problems with my current patch?


This task does not depend on any other tasks.