You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ok, so I have the choice of using the default ZK thread inside curator
and doing handoff manually in my callbacks, or I can pass the
CuratorFramework instance an Executor that it will use for callbacks.
Are all of the recipes written in a thread-safe manner that would
allow me to pass in a 10 thread pool or something, or is the
synchronization model similar to Swing's in that there's only one
thread updating state at a time?
The text was updated successfully, but these errors were encountered:
For any recipe that has a listener/callback mechanism: The listener is called by a single thread owned by the recipe instanced. In all cases you can provide an Executor with your listener so that you can use a different threading model.
Re-posting from Eric Tschetter:
Ok, so I have the choice of using the default ZK thread inside curator
and doing handoff manually in my callbacks, or I can pass the
CuratorFramework instance an Executor that it will use for callbacks.
Are all of the recipes written in a thread-safe manner that would
allow me to pass in a 10 thread pool or something, or is the
synchronization model similar to Swing's in that there's only one
thread updating state at a time?
The text was updated successfully, but these errors were encountered: