Re: [boost] [stratified] library for micro-/userland-threads

Subject: Re: [boost] [stratified] library for micro-/userland-threads
From: Oliver Kowalke (oliver.kowalke_at_[hidden])
Date: 2012-07-03 03:50:41

> Please do not use 'strand'. It's an existing different concept in Asio
> which will majorly confuse any user if you go with it.

OK

> I'd recommend 'fiber', not getting stuck up on platform specific names.
> After all, you've got things like the Windows mutexes which are IPC
> primitives, while the 'mutex' in Boost.Thread is intra-process.

hmm - boost.stratified does not contain IPC primitives - mutext, conditon_variable, ... use only context swapping (from boost.context).
the kernel is never involved.

what boost.stratified tries to solve is:

- cooperativly schedule strata (a stratum is more or less equivalent to a coroutine)

- provide synch. primitives to coordinate communication/access between strata (same as synch. primitives do in boost.thread)

> I'm opposed to the "Stratified" and "stratum" names, as they do not
> really mean anything relevant, and as far as I know, have never been
> used in literature to mean user-level threading.

the name was used in order to refer to 'Stratified JavaScript' http://onilabs.com/stratifiedjs.

regards,
Oliver