You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since function calls in Corto can be executed on a remote node, having to do a blocking wait for a response (in order to mimic 'traditional' function behavior) could hurt application performance. To address this, Corto should support calling functions asynchronously.
It would be nice if the user could decide whether to call a certain function asynchronously or not. Therefore, the language binding should allow for an extra way to call a method asynchronously. For example, the following corto definition:
int32 add(int32 a, int32 b)
could result in the following generated code (simplified- not showing casting macro's):
Since function calls in Corto can be executed on a remote node, having to do a blocking wait for a response (in order to mimic 'traditional' function behavior) could hurt application performance. To address this, Corto should support calling functions asynchronously.
It would be nice if the user could decide whether to call a certain function asynchronously or not. Therefore, the language binding should allow for an extra way to call a method asynchronously. For example, the following corto definition:
could result in the following generated code (simplified- not showing casting macro's):
Another option could be to allow for the function result to be posted to a dispatcher:
The latter would be more flexible, since it would allow the result of the function to be dispatched to a specific thread.
The text was updated successfully, but these errors were encountered: