Context Navigation

Changes between Version 2 and Version 3 of AsynchronousServicesFirstDay

v2	v3
28	28	* [attachment:ticket:1:True-Asynchronous-Model-from-Gent.png The flow of a true asynchronous, callback model], where the asynchronous client can be actively notified by the service when this last one has finished.
29	29	* And [attachment:ticket:1:Polling-Asynchronous-Model-from-Gent.png a polling mechanism], where the asynchronous client sends status update queries to the server, until the result is prepared or the service has failed.
	30	[[Image(ticket:1:Asynchronous-Roles-from-Gent.png,25%)]] [[Image(ticket:1:True-Asynchronous-Model-from-Gent.png,25%)]] [[Image(ticket:1:Polling-Asynchronous-Model-from-Gent.png,25%)]]
30	31
31	32	??? asked if it would be worth the model followed by some AJAX applications to be able to have an active service notification. This model maintains an open socket sending echo messages to avoid HTTP timeouts, but it was discarded because it was not reliable (once the connection is lost, the client should reconnect to the service, sending the job identifier. Then ??? told us about [http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.itame.doc/am60_webseal_admin119.htm a way to send/set job identifier as an HTTP header], so it is an out-of-band parameter (it does not need to be set as an explicit call parameter to the web service).