nope - peaberry doesn't hold any locks during the actual service call, it
only
has a small amount of synchronization to properly manage internal records
when setting up and tearing down a service call
Yup. I figured that would be the case after Richard's replay. Now the lock
holding mode
Hello,
Seems I have been chewing on the service dynamics issue forever. Just as I
though I got a workable concept about tracking and releasing services I stumble
on a contradicting concept. The problem is this:
According to my understanding it is not acceptable importer behavior to ever
call
On 6/14/09 5:08 PM, Todor Boev wrote:
Some say we should never call out from the bundle while holding a lock but I
think we are safe if we use a dedicated private lock for every tracked service.
In any case I can't think of any other way to be safe at all times. Lately
however I have been
Richard S. Hall wrote:
Yes. iPOJO is of the philosophy that service departures will likely lead
to errors, so you are better off being prepared to catch them and fail
gracefully, sort of like errors in distributed computing. Even if you
hold a dedicated lock, there is no guarantee that
Todor Boev wrote:
Richard S. Hall wrote:
Yes. iPOJO is of the philosophy that service departures will likely lead
to errors, so you are better off being prepared to catch them and fail
gracefully, sort of like errors in distributed computing. Even if you
hold a dedicated lock, there is no
5 matches
Mail list logo
