A "little" rewrite about elephant.io HOT 8 CLOSED

Hi,

There are some ideas (I like the fact that the Socket part is decoupled from the Client part), but it seems promising. Even though we try to stick close to PSRs standards, and also have some remarks to make (like the Debug trait... I don't think this should be each times included), but I did not went deeper in your refactoring yet.

But as I said, there seems to be some good ideas. :)

from elephant.io.

Thanks !

It was just a try, i'm not a composer expert neither a user of namespaces in Socket.IO, so I think that it will have some strange behaviours in particular conditions.

I'm sure you will do better as soon as you'll get time :)

from elephant.io.

Hi,
I was not aware of PSR standards since today (yup, shame on me.), I'll do my best to stick to them. Thanks @Taluu to highlighted this to me.

from elephant.io.

@Taluu all of your methods declarations aren't PSR-3-compliant ;-)

from elephant.io.

PSR-3 is just logging interface, which doesn't concern us. :)

And if you meant PSR-2, this lib was made way before the PSRs, but this problem should be solved in 3.0. :)

from elephant.io.

Yep, it was a typo ! Any idea about release date of that 3.0 version (with socket.io 1.0 support I imagine) ?

from elephant.io.

Just started working on it (like 10 minutes ago). But I don't have any insights on when we'll do the release, as I have a small window of time to do that, but I'll try to get some POC done next week.

It should have 0.x and 1.x support.

from elephant.io.

As the 3.0 was released as a beta, and as I based my work on what you did, I think it is safe to close this ticket.

Thanks ! :)

from elephant.io.