Hacker News new | past | comments | ask | show | jobs | submit login

Thanks.

I think the thread here, really means it is a conceptually independent 'processing unit' on its own, which reads the global state of some sort, then make the modification to it. They have multiple such 'threads', each corresponding to some particular task, but with no explicit locks.

Now it makes more sense to me. Threads here are more logical isolation of functionalities, not really parallel execution workers.

I was automatically associating threading with parallelism, but this makes sense for 'concurrency' even if there is only one of them are working at the time.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: