Date: 2005-02-12T14:23:13 Editor: RolandWeber Wiki: Jakarta-HttpClient Wiki Page: UseCases URL: http://wiki.apache.org/jakarta-httpclient/UseCases
no comment New Page: = Uses Cases for HttpClient = The use cases listed here are guiding the design and development of the Apache Jakarta HttpClient, starting with the new [wiki:Self:HttpClientApiRedesign API of version 4.0]. In addition to the use cases themselves, you can find guidance on how to implement them. If your use case is missing, please refer to our RequestForUseCases. The list is divided into three sections. '''Application Uses Cases''' are for situations where an applications uses the HttpClient directly. '''Middleware Uses Cases''' are for situations where components use HttpClient internally to provide some kind of service to applications. '''Engineered Use Cases''' are created artificially to address some part of the API or internal workings of the HttpClient. Engineered Use Cases are inferior to Application or Middleware Use Cases, but can be promoted if they get backed up by real life situations. == Application Use Cases == * [wiki:Self:UseCases/AccessURLs access documents by URL] * (todo): follow redirects == Middleware Use Cases == == Engineered Use Cases == --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
