diff options
Diffstat (limited to 'rotord')
| -rwxr-xr-x | rotord/rotor.h | 5 | ||||
| -rwxr-xr-x | rotord/rotord.cpp | 4 |
2 files changed, 9 insertions, 0 deletions
diff --git a/rotord/rotor.h b/rotord/rotor.h index 4a0c540..4961b98 100755 --- a/rotord/rotor.h +++ b/rotord/rotor.h @@ -64,6 +64,11 @@ messaging - http factory includes a poco notication center when it creates the rotor session it registers it session messages are posted thus and consumed +best way to control the rendering process? work queue isn't bad as it means we keep concurrency +also need to: +find out what the renderer is doing +get progress + */ #include <unordered_map> diff --git a/rotord/rotord.cpp b/rotord/rotord.cpp index 6ea61df..22e2e9f 100755 --- a/rotord/rotord.cpp +++ b/rotord/rotord.cpp @@ -193,6 +193,10 @@ HTTPRequestHandler* RotorRequestHandlerFactory::createRequestHandler(const HTTPS //pass a message object with the command type and contents selected? //every action will have a seperate work function in the render_context //some of these functions have to return data immediately- maybe a queue isn't the ideal model + //what's the best way to seperate these? + //could have a seperate mutex for the graph + //all the get methods want to get something from the render context and express it in xml. + //what is the best way... if (command[1]=="audio") { if (request.getMethod()=="PUT") { //get audio file location and initiate analysis |