Jump to: navigation, search

Difference between revisions of "TaskFlow/Architectures"

(Why)
(Architectures)
Line 8: Line 8:
  
 
=== Architectures ===
 
=== Architectures ===
 +
 +
[[File:Cue-architecture.png|200px|thumb|left|alt text]]

Revision as of 20:19, 17 November 2014

Revised on: 11/17/2014 by Harlowja

Why

Since taskflow creates a path toward stable, resumable, and trackable workflows it is helpful to have a small set of architectures (that have been implemented) to help in establishing best practices to make sure you as a user of taskflow (the library) maximize the benefit you receive from using taskflow. Certain common patterns of those architectures will be listed below to show the what, why and how so that you can maximize your taskflow experience and minimize the pain associated with understanding some of the taskflow key primitives.

Note: this list will likely continue growing as new usages of taskflow emerge (and new features are introduced into taskflow), please feel free to add any of your own below.

Architectures

alt text