Re: What about optional components?

[Jeffrey Dever]

 - a Cache (mentioned a while ago on the list)

A possibility, but likely more re-usable as a seperate project (there is currently the beginnings of a cache in the sandbox, but appears idle)

 - Proxy-Detection

Another possibility

- 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 is definately outside the scope of httpclient. Remember that HttpClient is HTTP (which is complex enough). HTML parsing and handling would be a seperate project.

I guess the generic User-Agent-part might become the next bigger
project that leverages HttpClients functionality. Although it will
need a lot of discussion to be generic & usefull enough for many
people.

Cool idea. Think through the functionality that is required, and divide into packages.
1) http connectivity
2) cache
3) html parsing
4) javascript parsing


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