I have to read this multiple times to understand this.but overall the scheme looks very similar to OOPS concept.
"The alternative to locking at the time data is accessed, is to lock at the time execution is scheduled". How does the scheduler keep track of the lock used inside the program..Does it look for any specific "lock or synchronization object" tags and make sure threads sharing them are not accessing them simultaneously ...May be the threads are of same priority, otherwise wouldnt this cause deadlocks?
You are viewing a single comment's thread from:
I realize lot of information is available in github.Will read up the documents and provide any comments and concerns we have.My team started out with Ethereum.But scalability and parallelism offered by EOS is very intriguing. For now exploring both