Working threads

[leda-ferreira]

First, thank you for this awesome project ! I'll look forward to contribute very soon :-).
That said, I would like to suggest using a library such as ReactPHP, Icicle.io or equivalent in order to permit assynchronous, non-blocking I/O. I think that, since the project its still in the beginning, this change wouldn't impact too much. I can try to work this into the code if necessary.

[danog]

That sounds like a good idea, even if I don't see exactly how can sending/receiving mtproto requests asynchronously improve speed or efficiency.
I might work it into the code later, as soon as I fix the generation of the authorization key.

[leda-ferreira]

Actually the non-blocking async i/o is to allow integration of your code with existing systems such as websocket servers / clients etc.
But thank you very much for considering the idea :-)

[danog]

Implementing threads atm, will take a while, but this will allow the creation of a fast socket wrapper.

[vahidvdn]

@danog Would you please explain more about threads atm?

[danog]

kek
threads = PHP threading here's a nice writeup
atm = at the moment

[danog]

This will only work when the dev of pthreads fixes bugs with nested volatile objects, and the devs of php fix https://bugs.php.net/bug.php?id=74545 (workarounds slow down everything too much)

[danog]

https://github.com/SirSnyder/pthreads/tree/feature/nested_volatiles helps only partially

[danog]

The latest version now supports multiprocessing with pcntl_fork.
It's not threading, but at least it's something.

[albedev]

@danog Nice

[danog]

Finally implemented async in the alpha branch

[giuseppeM99]

async != threaded

[danog]

But async is what OP originally proposed to implement :)