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

Subject: Re: [boost] [stratified] library for micro-/userland-threads
From: Thomas Heller (thom.heller_at_[hidden])
Date: 2012-07-03 03:56:25

On 07/03/2012 09:50 AM, Oliver Kowalke wrote:
>> 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)
Just for clarification, how is stratified related to your proposed 
coroutine library?
>
>> 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
>
> _______________________________________________
> Unsubscribe&  other changes: http://lists.boost.org/mailman/listinfo.cgi/boost