Add irc transport wrapper.

[shulard]

A specific Hoa\Irc\Socket definition has been added which contains the transport factory method.

The Socket is autoloaded through composer.json. The Client and Node have been updated to avoid class collision with Hoa\Socket.

The method used here is the same than in Hoa\Websocket. I checked that the default port for irc is 6667 so this is the fallback one.

[Hywan]

2016 Did you start from a fresh master?

[shulard]

@Hywan, the source Socket.php file have not been updated before the copy...

I've cleaned the PR :

• Remove the commit about construct from string behaviour
• Fix copyright date
• Fix exception message

[shulard]

Any news on that PR, is that change necessary ?

[Hywan]

Please, fix CS with hoa devtools:cs.

[Hywan]

Did you read https://tools.ietf.org/html/rfc7194. Maybe we can support irc-u:// (if this is a correct scheme)?

[shulard]

I've applied code style and read RFC7194.

About irc-u:// what the u means for you ? Is it for IRCU ports assignment ? I think irc-u can be considered as a valid scheme.

[Hywan]

See #22 (comment) for more general considerations.

[Hywan]

This PR is definitively useful. Please, continue!

[Hywan]

Did you read https://tools.ietf.org/html/rfc7194. Maybe we can support irc-u:// (if this is a correct scheme)?

[Hywan]

Here is the scheme I have found about IRC:

• https://www.w3.org/Addressing/draft-mirashi-url-irc-01.txt for the irc://… URI, you must read this one even this is a draft, you might find interesting links,
• https://tools.ietf.org/html/draft-butcher-irc-url-04, actually much better than the previous link because it defines the whole irc://… URI, and we discover the ircs:// scheme!
• And finally, as always, I consult this page http://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml, and we discover that irc and ircs are official schemes.

I guess it's enought information so far :-).

[shulard]

I think it is 😄 I'll take a look at these two schemes and implement them. Thanks for the docs !

[Hywan]

Thanks for your work!

[shulard]

Hello,

I've pushed the ircs transport wrapper implementation. Like the Hoa\Websocket, the secure state of the socket is determined using transport wrappers.

I've read the docs and have some questions about the required implementation.

Default port

The port number to connect to. If  :<port> is omitted,  the 
default IANA assigned IRC port 194 is used. Clients may use port 
6667 as an alternate port in case connection to the default 
port fails. Clients should also maintain a default port number,
as well as associations of port numbers with specific hosts. 

Seems that the standard port today is 6667 but do we need to fallback to 194 when the first connection fails ?

For me it's not the goal of an Irc library to handle that case but...

Question: Is 6667 the default port we must use because it's the most used and not the official default ?

URL Command analysis

The Irc connection URL can contains a lot of details about the connection that must be done : nickname, password, channel...

Do we need retrieving detailed URI informations and store them in the connection ? Maybe it's not in this PR that we need to address these questions...

Just that for the moment we are throwing away all additional informations given (authentication, channel...).

[Hywan]

About default port, I guess it's safe to assume 6667 is the default one today. Maybe Freenode or EFNet accept port 194 too. You should try. But if they not, then add a comment to explain why we have chosen 6667 over 194 as the RFC stipulates.

About the URL command analysis, you are totally right, this is out of the scope of this PR. You should open an issue to not forget to address this point, but this is an interesting feature!

[shulard]

I've created a new issue to address URI analysis: #25

I've also checked freenode and EFNet connection on port 194 with this script :

<?php
require_once 'vendor/autoload.php';

$uri    = 'tcp://chat.freenode.org:194';
$client = new Hoa\Irc\Client(new Hoa\Socket\Client($uri));

$client->run();

Got that error on freenode :

Uncaught Hoa\Socket\Client::_open(): (1) Client returns an error (number 65): No route to host while trying to join tcp://chat.freenode.org:194

And this one on EFNet :

Client returns an error (number 60): Operation timed out while trying to join tcp://irc.du.se:194

So I've added a comment to explain why we choose 6667 as default.

[Hywan]

I would have written: “Regarding the RFC, the recommended port is 194, however…”.

[shulard]

I've updated the comment 👍

[Hywan]

I have starting this review 11 days ago, but because of a network issue (probably), it has never been sent… sorry!

[Hywan]

I had to commit this patch too, 668b622. Nothing important but the API documentation was incorrect.

Thank you very much for your work! The README.md file has been updated too ab380eb.