News for hackers. Stuff that matters.

A comment on Building a concurrent TCP server with libmill. Parent comment

Re:Building a concurrent TCP server with libmill by rumcajz on Saturday July 25, 2015 @05:04PM (#9949004)
Using that definition, libmill is definitely coroutine-based. It does the scheduling itself.
[ Parent | on HN ]
Re:Building a concurrent TCP server with libmill by btrask on Saturday July 25, 2015 @05:19PM (#9949056)
I think it's mainly a fiber library, actually. The TCP and channel functions yield and resume automatically based on when the underlying operation blocks.

They have yield(), but I don't see the opposite, the ability to explicitly resume a stopped context.

Edit: for a "pure" coroutine library, I'd recommend libco from BSNES. It only has 4 functions: active, create, switch and delete. I wrote a fiber library using libco plus libuv, which was fairly easy.

https://web.archive.org/web/20140209005854/http://byuu.org/p... (unfortunately he still hasn't rebuilt his site)

[ Parent | on HN ]