From: christopher.g.dorosky++at++lmco.com
Date: 04/25/2000 19:03:46
I have a question regarding who does the work with a pfFlux.
In a pfBuffer, a process can schedule requested additions or deletions to a
pfNode by doing bufferAddChild or bufferRemoveChild. This acts as a request
only and doesn't get run until pfFrame (or pfSyncFrame) or something like
that in the app. It is actually the app that "does the work" of removing and
deleting all the children.
How does this work with a pfFlux? Although you don't need to do buffer
scheduling, and manipulate the data directly, there are calls like
writeComplete and getCurData. Does this either wait for the next pfFrame (or
Sync) or cause any appreciable extra work to happen there, or is all the
work done immediately by the calling process?
Thanks,
Chris
Christopher Dorosky
Senior Electronic Systems Engineer - Real Time Simulation
Lockheed Martin Missiles and Fire Control - Dallas
christopher.g.dorosky++at++lmco.com
972-603-2349
This archive was generated by hypermail 2b29 : Tue Apr 25 2000 - 19:04:04 PDT