- From: Mario Jeckle <mario@jeckle.de>
- Date: Thu, 07 Aug 2003 21:36:53 +0200
- Cc: www-ws-arch@w3.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Let me throw in an additional word, perhaps it clarifies another viewpoint to these issue (or just opens up room for more confusion ;-) ~From my point of view sync/async is not a question of the underlying transport protocol and it's features like correlation etc. at the first place. I think sync/async execution of a Web Service is merely a runtime issue. If the receiver *waits* for the message (i.e. blocking it's thread of execution) it's synchronous since both partners are needed to synchronize (to my best recollection this is also the semantic behind rendezvous). For doing so the receiver has to reserve space only for the message to receive. If the receiver does not wait for the message but there is a third instance offering space for buffering the receiver can continue its work independently from the sender. Hence the message exchange process is not synchronized. Bottom line: From my point of view async/sync is a question of blocking or not, and completely separated from the underlying protocol. It just has to provide sufficient ways to handle the message exchange in the way desired by the application. Ideas? Mario -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/MqpV46tt20EwGqwRArCGAKDLZPD+Kalz6B2cbVqvSW+iUX+lfACggsia /bDpWdkaefhmtQnRCHJlReI= =Pff7 -----END PGP SIGNATURE-----
Received on Thursday, 7 August 2003 15:37:06 UTC