Differences between revisions 1 and 2
Revision 1 as of 2005-12-29 18:48:59
Size: 1418
Editor: RolandWeber
Comment:
Revision 2 as of 2009-09-20 21:46:20
Size: 1382
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
[[BR]] <<BR>>
Line 12: Line 12:
[http://mail-archives.apache.org/mod_mbox/jakarta-httpclient-dev/200512.mbox/%3c4397B320.8020101@opensource.lk%3e Saminda Abeyruwan] [[http://mail-archives.apache.org/mod_mbox/jakarta-httpclient-dev/200512.mbox/%3c4397B320.8020101@opensource.lk%3e|Saminda Abeyruwan]]
Line 14: Line 14:
[[BR]] <<BR>>
Line 16: Line 16:
[http://www.w3.org/TR/ws-desc-usecases/#N10173 fire-and-forget]. [[http://www.w3.org/TR/ws-desc-usecases/#N10173|fire-and-forget]].
Line 20: Line 20:
 * [wiki:Self:UseCases/SingleAsyncRequest single asynchronous request]
 * [wiki:Self:UseCases/SingleAsyncRequestNotify send a single request asynchronously, with notification]
 * [wiki:Self:UseCases/AsyncRequestSequence send a request asynchronously, with automatic follow-up requests]
 * [wiki:Self:UseCases/MultiAsyncRequests multiple asynchronous requests]
 * [[UseCases/SingleAsyncRequest|single asynchronous request]]
 * [[UseCases/SingleAsyncRequestNotify|send a single request asynchronously, with notification]]
 * [[UseCases/AsyncRequestSequence|send a request asynchronously, with automatic follow-up requests]]
 * [[UseCases/MultiAsyncRequests|multiple asynchronous requests]]
Line 30: Line 30:
[wiki:Self:UseCases/AsyncRequestSequence generating follow-up requests], [[UseCases/AsyncRequestSequence|generating follow-up requests]],

Use Case: Send Asynchronous Request And Ignore Response

Description

I want to send a request without blocking the application.
I don't care about the response to the request.

Background

The requirement for ignoring the response was raised by Saminda Abeyruwan on the developer mailing list.
It originates from the Web Services scenario fire-and-forget.

Discussion

Even though the response is ignored by the application, something has to be done for releasing the connection over which it is sent from the server. If the connection should be re-used, the response must be read. This raises basically the same questions about threads and responsibilities as does generating follow-up requests, except that the thread is needed to consume the response.

UseCases/AsyncFireAndForget (last edited 2009-09-20 21:46:20 by localhost)