Linked by Hadrien Grasland on Fri 27th May 2011 11:34 UTC
General Development After having an interesting discussion with Brendan on the topic of deadlocks in threaded and asynchronous event handling systems (see the comments on this blog post), I just had something to ask to the developers on OSnews: could you live without blocking API calls? Could you work with APIs where lengthy tasks like writing to a file, sending a signal, doing network I/O, etc is done in a nonblocking fashion, with only callbacks as a mechanism to return results and notify your software when an operation is done?
Thread beginning with comment 474872
To view parent comment, click here.
To read all comments associated with this story, please click here.
Alfman
Member since:
2011-01-28

JAlexoid,

"Well you then know not much about how Java and C# synchronisation mechanisms work. If you're into Java I suggest watching some of Cliff Click's tech talks on concurrency and memory model."

Well that's just not fair, your trying to make fun of me and I'm trying to have a serious discussion... I won't go to your level.

"Reentrant mutex or lock works by allowing the same thread to acquire it more than one time. Also requires it to be released the number of times it was acquired. It essentially has the owning thread + counter."

You're echoing what I had said... in any case, it wasn't applicable to the problem being discussed.

Reply Parent Score: 2

JAlexoid Member since:
2009-05-19

Well that's just not fair, your trying to make fun of me and I'm trying to have a serious discussion... I won't go to your level.

And I take it you don't plan to address that gap in your knowledge?

Reply Parent Score: 2

Alfman Member since:
2011-01-28

JAlexoid,

"And I take it you don't plan to address that gap in your knowledge?"

What gap in my knowledge? I didn't know a certain keyword, I looked it up before responding back. I learned something, so I thank your for having brought it up.

But you are a vicious troll.

Reply Parent Score: 2