<HTML><HEAD><META content="text/html; charset=UTF-8" http-equiv="Content-Type"></HEAD><BODY>You guessed correctly! Unless there is a bug in Netty, specifying the bufferFactory should be all you need to do. You'll have to be careful to use the ChannelBufferFactory you specified when you create a buffer though.<BR>
<BR>
HTH<BR>
<BR>
Replicator wrote:<BR>
> Would that answer both of the questions above:<BR>
><BR>
><BR>
> clientBootstrap.setOption( "bufferFactory",<BR>
> new HeapChannelBufferFactory(<BR>
> ByteOrder.LITTLE_ENDIAN ) );<BR>
><BR>
><BR>
> Or will I still need to do anything in addition to make sure the client is<BR>
> reading / writing in LITTLE_ENDIAN?<BR>
><BR>
> Thank you!<BR>
><BR>
> --<BR>
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Global-Config-Little-Endian-tp6893711p6893744.html<BR>
> Sent from the Netty User Group mailing list archive at Nabble.com.<BR>
> _______________________________________________<BR>
> netty-users mailing list<BR>
> netty-users@lists.jboss.org<BR>
> https://lists.jboss.org/mailman/listinfo/netty-users</BODY></HTML>