diff options
| author | Sven Gothel <[email protected]> | 2013-11-29 02:24:01 +0100 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2013-11-29 02:24:01 +0100 |
| commit | 586446311ea1ba87f98236d5347955bf99b465d6 (patch) | |
| tree | 2bba93f117ec08bbb3ea96ee6cd2c44d97b04421 /make/lib | |
| parent | cb0afe743d21a3480e2d41744a904ac7d404612d (diff) | |
Bug 907 - Refine DummyDispatchThread (DDT) Handling: Proper OO integration in RegisteredClass; Safe DDT Post/WaitForReady handling and error cases ; ...
Proper OO integration of DDT in RegisteredClass
- DDT is optional to RegisteredClass[Factory],
i.e. NEWT without DDT and DummyWindow with DDT.
- Using native type DummyThreadContext per DDT
passed as DDT handle to java referenced in RegisteredClass
- Passing DDT handle to related native methods,
if not null use DDT - otherwise work on current thread.
The latter impacts CreateDummyWindow0 and DestroyWindow0.
Safe DDT Post/WaitForReady handling and error cases ; ...
- Wait until command it complete using a 3s timeout
- Terminate thread if errors occur and throw an exception
+++
Discussion: DDT Native Implementation
Due to original code, the DDT is implemented in native code.
Usually we should favor running the DDT from a java thread.
However, since it's main purpose is _not_ to interact w/ java
and the native implementation has less footprint (performance and memory)
we shall be OK w/ it for now - as long the implementation IS SAFE.
Diffstat (limited to 'make/lib')
0 files changed, 0 insertions, 0 deletions