Thank you for providing us with feedback on the need and direction for a new Khronos® open standard for Heterogeneous Communications!

You can find more information on the motivation and direction of a potential standard, the process we are following to see whether we should establish a standards initiative, and context for these questions here

The survey will remain open for 14 days. After we have gathered industry feedback, we will anonymize and aggregate the received responses and send a summary report - and resulting actions and outcomes - to all respondents.

Your personal information will not be used for any other purpose unless you request to be added to our newsletter list.

Thank you again for your time and feedback!

Question Title

* 1. What industry do you work in? (select all that apply)

Question Title

* 2. What type of software do you develop? (select all that apply)

Question Title

* 3. What type of hardware does your software deploy on? (select all that apply)

Question Title

* 4. What types of communication are important to you? (select all that apply)

Question Title

* 5. What key communication features are important to you? (select all that apply)

Question Title

* 6. What low level communication and signaling APIs have you used? (select all that apply)

Question Title

* 7. What high level communication and signaling APIs have you used? (select all that apply)

Question Title

* 8. Is more than one communication & signaling API needed in your typical application? (e.g. sockets or MPI for inter-process, and mutexes and conditional variables for inter-thread)

Question Title

* 9. Is the communication in your typical application:

Question Title

* 10. Do you think there is a need for a new open communication standard to unify low-level communication into a simple API?

Question Title

* 11. Of the communication APIs you've used, what were the notable benefits that you would like to see in a new standard?

Question Title

* 12. Of the communication APIs you've used, what were the notable pain points that should be avoided in a new standard?

Question Title

* 13. What programming language bindings would you like to see supported if a new standard is developed? (select all that apply)

Question Title

* 14. Do you think the Takyon proposal provides a suitable basis for a new standard? 

Question Title

* 15. Would you have a different proposed starting point than Takyon for this initiative? 

Question Title

* 16. Would you be interested in participating in the development of a new communications standard?

Question Title

* 17. Responder Information (Your personal information will not be used for any other purpose unless you request to be added to our newsletter list.)

Question Title

* 18. Would you like to be added to the Khronos Newsletter email list?  

T