03-26-2012 10:38 AM
@DFGray wrote:
...
For those of you who are following it, this design is similar to the actor framework, but is more efficient for file I/O (fewer data copies).
Now just playing along...
As i understand it an Actor Framework is a design pattern whre Active Object are instaciated and used. An Active Object is a fancy term for a "background process" or Daemon that offers methods by which other classes can interact with it.
Ben
03-26-2012 11:10 AM
That about sums it up, Ben. The actor framework I linked to is a LabVIEW implementation of this idea that does not inherently depend on globally available data (i.e., no DVRs, globals, or action engines needed). My file I/O framework will be similar.