RE: [Public WebCL] Synchronous waitForEvents?

[Simon Gibbs - Samsung <sgibbs@sisa.samsung.com>]

You're right, the reason was mainly to mirror the OpenCL API.
However, non-blocking use is also supported by OpenCL. In WebCL, one can use, for example, WebCLEvent.setCallback(...)

Simon Gibbs

-----Original Message-----
From: owner-public_webcl@khronos.org [mailto:owner-public_webcl@khronos.org] On Behalf Of Jens Nockert
Sent: Sunday, April 15, 2012 11:51 AM
To: public_webcl@khronos.org
Subject: [Public WebCL] Synchronous waitForEvents?


What is the reason for waitForEvents being blocking except for mirroring the OpenCL API?
Inside of a normal browser context (non-worker) it seems like a bad idea to me, shouldn't it instead
a) Have a non-blocking variant waitForEvents(WebCLEvent[] eventWaitList, callback) ?
b) Have the blocking variant limited to workers (or similar) ?

-- Jens Nockert



-----------------------------------------------------------
You are currently subscribed to public_webcl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with the following command in the body of your email:
unsubscribe public_webcl
-----------------------------------------------------------


-----------------------------------------------------------
You are currently subscribed to public_webcl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webcl
-----------------------------------------------------------