On 30/11/2008, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote: > On Mon, 2008-12-01 at 12:54 +0000, sebb wrote: > > Various HttpClient methods currently return null instead of an array > > under some circumstances. > > > > This means that the calling code has to check for null before > > processing the result, whereas in most cases the code would work just > > as well if there was an empty array, thus saving the null check. > > > > For example: > > private String[] org.apache.http.conn.ssl.AbstractVerifier.getSubjectAlts() > > > > int[] org.apache.http.impl.cookie.BasicClientCookie.getPorts() > > > > Any thoughts on this? > > > > > This is obviously wrong and should be fixed.
OK, I'm happy to do it. It will slightly change the behaviour for some public methods. > Oleg > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
