On Jan 25, 2008 5:26 PM, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> Would it make sense for the ResponseParser to take define:
> public  abstract NamedList<Object> processResponse(InputStream body,
> Charset encoding);
>
> instead of a string for the Encoding?

"encoding" is a superset of CharSet... the future could very well
bring a binary encoding.

> Alternatively, should it throw the UnsupportedEncodingException if it
> does take a String?

Now, it's handled as a runtime exception (same as parsing failures).
But this isn't something a user will normally be providing anyway...
it's obtained from the Solr response and provided by the SolrJ code.

-Yonik

Reply via email to