Smarter connection handling

[Jonas Häggqvist]

The connection handling is a bit half-baked at the moment. A few things are not currently possible (some more useful than others):
1. Non-ssl connections
2. Connecting to different channels on different networks

When fixing the config-side of this, be VERY CAREFUL not to reinvent the irssi config syntax.

[Space Hobo (spacehobo)]

I wonder if a URL syntax would be useful here, such as:

    ircs://<email address hidden>/#yardbird

[Space Hobo (spacehobo)]

Relevant doom:

  http://www.mozilla.org/projects/rt-messaging/chatzilla/irc-urls.html

[Jonas Häggqvist (rasher)]

> I wonder if a URL syntax would be useful here, such as:

That looks slightly simpler to set up. On the other hand, you'll need to do a bunch of parsing code. I assume you'd do something like this for multiple channels?

    ircs://<email address hidden>/#yardbird,#example

> http://www.mozilla.org/projects/rt-messaging/chatzilla/irc-urls.html

There really is no way to win this game, it seems.

[Space Hobo (spacehobo)]

Of course, parsing URLs is something that django gives us many tools to help with!

I definitely think I'll NIH rather than adopt the chatzilla brainworms.

I'm not sure about the comma-separated list of channels, though. URLs define unique resources, and each channel is a resource. I will need some kind of caching logic to make sure I only open one connection per server, but that shouldn't be too onerous.

[Space Hobo (spacehobo)]

I've merged early, so people following trunk are in for a rude surprise. This no doubt will need fixing, but I think once we get the details of how this interacts with the privileged channel stuff ironed out it'll be a great time for a new release with packages and all.

[Space Hobo (spacehobo)]

tested with bindlestiff using passwords. the only wrinkle now is that if you specify the port once you have to for all your URLs. this isn't so bad, but it'd be cool if we found a way to make them implicit after the first one