Max Voelkel wrote:
  - a Cache (mentioned a while ago on the list)
  - Proxy-Detection
okay

  - Some kind of "User-Agent" on top of HttpClient which:
     - handles Framesets (return urls of subframes)
     - possibly parses FORM-Tags
     - eventually handles JavaScript-Code and
       return the complete page (with document.write()-statements
       executed).
     - many more dreams here ...
This has *nothing* to do with HTTP (the focus of HttpClient) at all - that is only HTML. HTTP is much more than transporting HTML!

HTML Parsers are already available for Java. No need for us to build one into HttpClient. If anything then a HTTP Parses should go as a new project under Commons or even Jakarta.

Odi


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to