The Khronos Group - a non-profit industry consortium to develop, publish and promote open standard, royalty-free media authoring and acceleration standards for desktop and handheld devices, combined with conformance qualification programs for platform and device interoperability.

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Regarding Event mechanism

Dear OpenKODE team,

First of all thank to all who have been a part of the development of OpenKODE..

Let me know about the khronos Grp view point on the following:

How will be the OpenKODE event mechanism coexists with other existing event mechanism ?
Is it necessary that all the applications in the system should use the OpeKODE event mechanism and system mechanism as a gateway by making the existing mechanism as its subset?

I am confused, isn't threading optionally supported in openKode? BTW, how is threading implemented? and what is the threading model? is there a soft memory copy or a hard one, does the system spawn or does it use lightweight processes for threading?

Yes, OpenKODE does have threading. The model is a subset of POSIX threads. Each thread has its own event queue; for events from a window, socket or timer, OpenKODE posts the event to the queue for the thread that created the window, socket or timer.