Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Fri, 15 Jan 2010 18:42:42 -0000
Message-ID: <20100115184242.4101.78041@eos.apache.org>
Subject: 
 =?utf-8?q?=5BHttpcomponents_Wiki=5D_Update_of_=22CodingConventions=22_by_?=
 =?utf-8?q?TonyPoppleton?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Httpcomponents Wiki=
" for change notification.

The "CodingConventions" page has been changed by TonyPoppleton.
http://wiki.apache.org/HttpComponents/CodingConventions?action=3Ddiff&rev1=
=3D2&rev2=3D3

--------------------------------------------------

   * In very rare cases it may be approriate to ignore an exception, in whi=
ch case document it clearly.
   * TODO is there a custom HTTP client exception that is used?
   * Handle exceptional conditions by throwing an exception and not, for ex=
ample, returning null from a method.
-  * Prefer unchecked exceptions (like RuntimeException) over checked excep=
tions.  Only use checked exceptions if it is expected that the caller can h=
andle it or recover from it.  Unchecked exceptions will just be propagated =
back to the general exception handler, which is ideal.
+  * Prefer unchecked exceptions (like RuntimeException) over checked excep=
tions as per [http://www.oracle.com/technology/pub/articles/dev2arch/2006/1=
1/effective-exceptions.html].  In summary, only use checked exceptions if i=
t is expected that the caller can handle it or recover from it.  Unchecked =
exceptions will just be propagated back to the general exception handler, w=
hich is ideal.
  }}}
  =

  =3D=3D Collections =3D=3D

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org