136 reputation
3
bio website
location
age
visits member for 2 years, 3 months
seen Jan 17 '13 at 7:35

Oct
31
revised Optimistic work sharing on sparsely distributed systems
more detail
Oct
31
comment Optimistic work sharing on sparsely distributed systems
Thank you for your answer. Data is not the problem here - the system has eventual consistency, and leans more toward availability. The problem is how to use whatever data model exists and use that to assign work to distributed units.
Oct
31
revised Optimistic work sharing on sparsely distributed systems
grammar
Jan
16
comment Optimistic work sharing on sparsely distributed systems
The above solution is okay when: 1. Computation creates no side-effects 2. You have immediate access to the state of computation This isn't the case with a sparsely distributed system. But I see your point. I'll look into systems which deal with the concurrency side of it first. Thank you.
Jan
16
comment Optimistic work sharing on sparsely distributed systems
let us continue this discussion in chat
Jan
16
comment Optimistic work sharing on sparsely distributed systems
In a Master-Client setup, how does one ensure actions are not duplicated without locking?
Jan
16
comment Optimistic work sharing on sparsely distributed systems
My friend, I'm looking for a paradigm like Tuple spaces, not a set of programs that I need chain or a database to run on Amazon or Azure.
Jan
16
awarded  Supporter
Jan
15
awarded  Editor
Jan
15
revised Optimistic work sharing on sparsely distributed systems
added 180 characters in body
Jan
15
comment Optimistic work sharing on sparsely distributed systems
All the conventional problems of a Master-Slave architecture, Dan. Single point of failure, bottle-necks due due to load on master, messages required to acquire a lock, reentrancy, task deadlines... I'm looking for a shift which could mitigate classic problems early on.
Jan
15
comment Optimistic work sharing on sparsely distributed systems
I appreciate the honest answer, but it is akin asking for a solution like Operational Transformations for collaborative editing and being told that you should stick to database transactions because it is easy.
Jan
15
comment Optimistic work sharing on sparsely distributed systems
The easiest solution is easy precisely because it puts a set of constraints on the working of the system, reducing the system complexity. E.g., Having event handling code running on the GUI event-loop is the easiest solution. When the code is computationally intensive, you cause the GUI to become unresponsive. You will have traded the easy solution for the constraint that you will have an unresponsive GUI.
Jan
15
awarded  Student
Jan
15
asked Optimistic work sharing on sparsely distributed systems