|
⇤ ← Revision 1 as of 2005-02-12 22:55:50
Size: 1622
Comment:
|
← Revision 2 as of 2009-09-20 21:46:18 ⇥
Size: 1622
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| [[BR]] | <<BR>> |
| Line 17: | Line 17: |
| [[BR]] | <<BR>> |
| Line 24: | Line 24: |
| [[BR]] | <<BR>> |
| Line 32: | Line 32: |
| [[BR]] | <<BR>> |
| Line 40: | Line 40: |
| [[BR]] | <<BR>> |
| Line 49: | Line 49: |
| [[BR]] | <<BR>> |
Use Case: ''title''
Stuff in italics is meant to be deleted when you fill out the respective section on the new page.
Start by entering a title above, then delete this paragraph you are reading.
Description
Describe your use case. This section is required.
Background
Provide supplementary information. Like how you got the idea, or why the use case is not handled nicely by HttpClient. Or anything else you feel should be mentioned but does not belong to the actual description of the use case.
This section is optional. If you don't have background information, please remove the whole section.
Variations
Add variations of the original use case that are not different enough to merit a separate use case.
This section is optional. If you don't want to provide variations, please leave it empty but don't remove it.
Related / Out of Scope
Provide links to other use cases with similarities, or describe situations that are not addressed by this use case.
This section is optional. If you don't have anything to put here, please remove the whole section.
Discussion
Discussion of the technical aspects and consequences of the use case.
This section is required, but can be left empty when the use case is created.
Solution
sample code, algorithmic descriptions, or other pointers and guidelines on how to implement this use case.
This section is optional. If you can't provide a solution, please leave it empty but in the document.