Difference between revisions of "Creating Multithreaded Skyrim Mods Part 3 - Callbacks"

Creating Multithreaded Skyrim Mods Part 3 - Callbacks (edit)

Revision as of 17:25, 22 January 2015

1,940 bytes added , 17:25, 22 January 2015

no edit summary

Anonymous user

imported>Chesko

@@ Line 11: / Line 11: @@
 == Pattern Overview ==
+To recap the Pros and Cons of this approach:
+==== Callback Pros ====
+* '''Push-based:''' Using callbacks is a ''push'' pattern, where results are returned to you as soon as they're available instead of having to request them.
+* '''Anyone can access results:''' The results of a thread are available to anyone who registered for the event that returns them.
+* '''Results received without delays:''' Unlike Futures, you do not have to block your script pending results being available. Just register for the appropriate event and react to it.
+* '''No polling:''' You no longer have to potentially poll for whether or not your results are ready.
+* '''Easier to understand:''' The concepts in a Callback pattern are nothing new to anyone who knows how to use Mod Events.
+* '''Easier to implement:''' Their are comparatively fewer things to deal with when using a Callback pattern.
+* '''Less overhead (faster):''' Using a callback pattern can be a bit faster than a Future-based approach.
+==== Callback Cons ====
+* '''...Anyone can access results:''' You have no control over who is able to consume your results.
+* '''No control when results are retrieved:''' You have no control over when a result will be retrieved, or in what order. You must be able to react to the result events that are raised, and you must assume that threads can finish in any order.
+* '''More difficult to trace execution order:''' A callback pattern can make the script flow more difficult to follow and debug, since the function where a thread is started and the event that it returns results to will be in two (or more) different places.
+* '''Locks required:''' Locks are required if you have two threads that may write to the same variable.
+* '''Requires more state management:''' You can receive result callbacks at any time, which may make it necessary for you to re-evaluate the script's current state each time you receive one, depending on your application.
 Here is a diagram of how the Callback pattern works.