Rendezvous: Difference between revisions

The caller may limit the waiting time to the callee to accept the rendezvous. I.e. a rendezvous request can be aborted if not yet accepted by the callee. When accepted the rendezvous is processed until its completion. During this time the caller and the callee [[task|tasks]] stay synchronoussynchronized. Which context is used to process the rendezvous depends on the implementation which may wish to minimize context switching.

* Rendezvous to different entry pointpoints.

Language mechanism of [[exceptions]] (if any) ishas to be consistent with the rendezvous. In particular when an exception is propagated out of a rendezvous it shall do in both tasks. The exception propagation is synchronous within the rendezvous and asynchronous outside it.

AAn engaged rendezvous can be requeued to by the callee to another entry point of its [[task]] or to another [[task]], transparently to the caller.

Differently to messagingmessages which are usually asynchronous, rendezvous are synchronous, as it was stated before. Therefore a rendezvous does not require marshaling. Itthe isparameters alsoand a buffer to keep them. Further, rendezvous can be implemented without context switch. This makes rendezvous a more efficient than messaging.