Re: [Htmlparser-developer] version 1.3

[Sam J. <sa...@ne...>]

Hi Derrick,

Some responses of my own.

Derrick Oswald wrote:

> POST constructor.
> The basically two constructors that HTMLParser has either take a 
> string URL or a HTMLReader.  This shifts the onus on performing HTTP 
> to the API user for POST operations.  It might be good to have a 
> HttpURLConnection or URLConnection argument constructor, where a 
> primed and loaded connection is passed to the parser. 

I very much agree (thanks for your previous suggestions on this topic BTW)

> Tables
> The current version flattens tables, pushing the onus on the API user 
> to syntactically walk through the table data to get to a certain table 
> entry.  It may be useful to nest table entries, similar to what the 
> the FORM tag does now, but have it correctly generate rows and columns. 

Have you looked at HTTPUnit? http://httpunit.sourceforge.net/

They have to deal with a lot of similar problems and there may be synergies.

> Logging
> The use of a feedback object is adequate, but JDK version 1.4 has a 
> rich API, java.util.logging, that we might want to emulate (presuming 
> we don't want to force JDK 1.4 usage).

I would be against forcing JDK 1.4 usage.  I would recommend log4j 
http://jakarta.apache.org/log4j/docs/index.html

> charset
> Currently the charset directive within the HTML page is ignored. There 
> may be a need to honour this parameter on the Content-Type field. 

Agreed

CHEERS> SAM