Jordi Salvat i Alabart <[EMAIL PROTECTED]> wrote:
+0 on keeping htmlparser code in our codebase -- at least for the time being. +0 on switching default parser to htmlparser. Performance-wise, I would vote for the regex one, but I don't really trust its accuracy (although it is working very well for me so far, I usually work with sites that have fairly clean HTML). Anyway, I'm thinking about making the parser a configuration component. I just doubled checked and it looks, HTMLParser is the default. private final static String DEFAULT_PARSER = "org.apache.jmeter.protocol.http.parser.HtmlParserHTMLParser"; we should change it back to JTidy. I prefer the idea of making it configurable, so that users can select which one they want to use in the GUI. that way it doesn't require changing the properties file. +1 on switching to HTTPClient -- as far as performance is good, which I'm sure will be. -- Salut, Jordi. I'll report my findings once I am done. peter lin --------------------------------- Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online
