Hello, developer of MadelineProto here!
Thank you so much for using my library in your project, it's really awesome!
I wanted to rewrite my old PWRTelegram HTTP API for the new MadelineProto for a long time, and now you come up with a simple alternative, just perfect!
If you want to, I could make TelegramSwoole the official successor of PWRTelegram.
Reading the comments here, I see people saying that swoole is pretty useless in a blocking, non-async context; that's why I suggest you try to use the new async MadelineProto API based on amphp: I'm currently rewriting the whole library to fully support async operation, and most of the automatically-wrapped API methods are already fully async.
The async API is still rather alpha, and I haven't written proper docs yet, but you can take a look at the bot.php in the main repo or ask me in the groups for help, if you want to.
P.S. amphp is an extremely powerful set of coroutine-based libraries, with async clients/servers for TCP, UDP, HTTP, redis, MySQL, websocket, DNS, windows registry API, and many async backends supported (native PHP or extension-based), as well as hybrid multi-threaded async worker support for blocking operations that simply cannot be done using the amphp libraries (and even if I highly dislike and recommend against using anything multi-threaded in PHP, be it the extremely buggy pthreads or just the simple glitchy forks (both supported by amphp), or even the web-request multithreaded backend supported by amphp, it's cool that you can do so many amazing async things in PHP with a simple user-space library), I suggest you check it out)
Thank you so much for using my library in your project, it's really awesome!
I wanted to rewrite my old PWRTelegram HTTP API for the new MadelineProto for a long time, and now you come up with a simple alternative, just perfect!
If you want to, I could make TelegramSwoole the official successor of PWRTelegram.
Reading the comments here, I see people saying that swoole is pretty useless in a blocking, non-async context; that's why I suggest you try to use the new async MadelineProto API based on amphp: I'm currently rewriting the whole library to fully support async operation, and most of the automatically-wrapped API methods are already fully async.
The async API is still rather alpha, and I haven't written proper docs yet, but you can take a look at the bot.php in the main repo or ask me in the groups for help, if you want to.
P.S. amphp is an extremely powerful set of coroutine-based libraries, with async clients/servers for TCP, UDP, HTTP, redis, MySQL, websocket, DNS, windows registry API, and many async backends supported (native PHP or extension-based), as well as hybrid multi-threaded async worker support for blocking operations that simply cannot be done using the amphp libraries (and even if I highly dislike and recommend against using anything multi-threaded in PHP, be it the extremely buggy pthreads or just the simple glitchy forks (both supported by amphp), or even the web-request multithreaded backend supported by amphp, it's cool that you can do so many amazing async things in PHP with a simple user-space library), I suggest you check it out)