Thank you very much for your response, I think that at abstract level it is
true.
When we go into more detail, we will that GO optimize to have Routine context (
that some kind of Thread context), I think that at the conception level it some
kind of yeild (conception ) to start to GORoutine.
B
On Wed, 22 Jun 2016 00:34:56 -0700 (PDT)
tu.p...@zalora.com wrote:
> I think that the idea of Goroutine come from
> [https://en.wikipedia.org/wiki/Coroutine],
This is hardly true: coroutines imply cooperative scheduling, where
each coroutine explictly relinquishes control to some other coroutine
I think that the idea of Goroutine come from
[https://en.wikipedia.org/wiki/Coroutine], the number of Goroutines are
mapped to OS Threads. In my own opinion, Go maintain the Thread pool and
task queue to dispatch the job.
This pattern has been implemented in some modern JEE container.
Hope that
