Date: 2005-02-20T00:31:38 Editor: RolandWeber Wiki: Jakarta-HttpClient Wiki Page: UseCases URL: http://wiki.apache.org/jakarta-httpclient/UseCases
no comment Change Log: ------------------------------------------------------------------------------ @@ -4,27 +4,17 @@ 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. +implement them. If your use case is missing, please have a look at the +UseCases/SandBox or refer to our RequestForUseCases. -The list is divided into three sections. '''Application Uses Cases''' are for -situations where an application 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. +The list is divided into '''Real Life Uses Cases''' and '''Engineered Use Cases'''. +Engineered use cases are created artificially to address some part of the +API or internal workings of the HttpClient. They are inferior to real life use cases. -== Application Use Cases == +== Real Life 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]
