The standard library for C++ gives us a very robust set of options for creating/forking threads and joining them. The Ngen Framework will provide this same functionality, but more inline to the current model using RTI. This means that the framework will provide an Application domain where each Task will have its own reflection of referenced RTI assemblies. This will allow for applications to have a personal context when using RTI. Where one application may be referencing the "Ngen|Ngen:Ngen:IO" namespace, another application may not; so the application referencing "Ngen|Ngen:Ngen:IO" can use short-names ("IO") when attempting to identify code symbols or execute functions using pure RTI.
Instead of having to reference "Ngen|Ngen:Ngen:IO#FileStream", the application could just reference "#FileStream", or "FileStream". This will be the per-cursor for providing code
domains for personal variable space between applications/threads.
The standard library for C++ gives us a very robust set of options for creating/forking threads and joining them. The Ngen Framework will provide this same functionality, but more inline to the current model using RTI. This means that the framework will provide an Application domain where each Task will have its own reflection of referenced RTI assemblies. This will allow for applications to have a personal context when using RTI. Where one application may be referencing the "Ngen|Ngen:Ngen:IO" namespace, another application may not; so the application referencing "Ngen|Ngen:Ngen:IO" can use short-names ("IO") when attempting to identify code symbols or execute functions using pure RTI.
Instead of having to reference "Ngen|Ngen:Ngen:IO#FileStream", the application could just reference "#FileStream", or "FileStream". This will be the per-cursor for providing code domains for personal variable space between applications/threads.