On Oct 31, 2007 9:44 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > +1 for the interface. > > Maybe "writeTo" is better than "write" (the first thought when I read > write(StringBuffer) is that the method write the content of StringBuffer > somewhere and not viceversa).
+1 > I'm not sure I understand the size in octect. You write a StringBuffer, > so it is an unicode string, how can you calculate the real octects if > you don't know the charset/encoding that will be used when the buffer > will be written out? the content must be prior encoded into US-ASCII. probably should be javadoc'd. IMO use of StringBuffer is a poor design choice (but some work would be required to change it) but has no negative practical effects. should probably deprecate. > Do we need to know the charset and the transfer encoding from the header > of this content to be able to correctly evaluate the content or the > content has already been correctly "decoded" ? the content needs to be appropriately prior encoded. if the content has been decoded by the backend then it needs to be appropriately re-encoded. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
