Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-httpclient Wiki" for change notification.
The following page has been changed by RolandWeber: http://wiki.apache.org/jakarta-httpclient/UseCases/SingleAsyncRequest ------------------------------------------------------------------------------ == Related / Out of Scope == + * [wiki:Self:UseCases/SingleAsyncRequestNotify single asynchronous request with notification] * [wiki:Self:UseCases/MultiAsyncRequests multiple asynchronous requests] * sequences of requests, like chasing redirects * fire and forget @@ -20, +21 @@ This is the most basic case of asynchronous communication, possibly useful if the request includes a large body or if the server is expected to respond with a huge delay. It can be used to interlock HTTP communication with something else, but eventually the application has to receive + the response synchronously, which limits the applicability. - the response synchronously, which limits the applicability. However, a separate notification mechanism can be - designed to indicate to the application that the response is available. The focus of this use case is the design of an interface for sending the request asynchronously, and for receiving the response synchronously. An initial implementation of that interface could spawn a background --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
