From: Ovidiu F. <ovi...@jb...> - 2006-03-01 22:57:39
|
User: ovidiu Date: 06/03/01 17:57:38 Modified: src/main/org/jboss/jms/server/remoting JMSWireFormat.java Log: minor reformatting Revision Changes Path 1.5 +7 -10 jboss-jms/src/main/org/jboss/jms/server/remoting/JMSWireFormat.java (In the diff below, changes in quantity of whitespace are not shown.) Index: JMSWireFormat.java =================================================================== RCS file: /cvsroot/jboss/jboss-jms/src/main/org/jboss/jms/server/remoting/JMSWireFormat.java,v retrieving revision 1.4 retrieving revision 1.5 diff -u -b -r1.4 -r1.5 --- JMSWireFormat.java 21 Feb 2006 07:44:01 -0000 1.4 +++ JMSWireFormat.java 1 Mar 2006 22:57:38 -0000 1.5 @@ -48,16 +48,13 @@ * * A JMSWireFormat. * - * For some invocations, e.g. message sends, acknowledgements and activations it - * is vital that we minimise the amount of data sent in the invocation so that we - * can maximise performance. - * By default, Invocations and return values are sent over the wire as serialized Java - * objects. - * This adds considerable overhead in terms of the amount of data sent - * (It adds class information plus block data information) - * which significantly degrades performance. - * Therefore for the invocations where performance is paramount we define a customer wire - * format that minimises the amount of data sent. + * For some invocations, e.g. message sends, acknowledgements and activations it is vital that we + * minimise the amount of data sent in the invocation so that we can maximise performance. + * By default, Invocations and return values are sent over the wire as serialized Java objects. + * This adds considerable overhead in terms of the amount of data sent (it adds class information + * plus block data information) which significantly degrades performance. Therefore for the + * invocations where performance is paramount we define a customer wire format that minimises the + * amount of data sent. * * @author <a href="ti...@jb...">Tim Fox</a> * @version 1.1 |