xml-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven McDowall" <...@aptest.com>
Subject RE: i18n (was: rpcrouter servlet committed)
Date Tue, 08 Aug 2000 19:53:15 GMT
RE: i18n (was: rpcrouter servlet committed)

Great suggestion.. Which is how I actually implemented it in the reference
code I submitted :-)

I was commenting on any OTHER way to do it :-)  Sanjiva didn't seem to like
my (or now yours..)
and thus didn't implement it at all in the code that got committed..


  -----Original Message-----
  From: Jean-Noel Gadreau [mailto:jngadreau@activcard.com]
  Sent: Tuesday, August 08, 2000 12:59 PM
  To: 'soap-dev@xml.apache.org'
  Subject: RE: i18n (was: rpcrouter servlet committed)

  If you want to send the response length, what you could do is write
everything in a ByteArrayOutputStream, then get the length, and finally send
it to the client (by setting the response length first). I not sure this is
really a good solution because it takes some memory... That's how I would
probably do it.

  I can probably send you a patch for this if you think it is worth it.

  Jean-Noel Gadreau

  Jean-Noel GADREAU
  Software Engineer, ActivCard Inc.(http://www.activcard.com )
  E-mail: jngadreau@activcard.com
  Tel (main): 510-574-0100
  Tel (direct): 510-574-1736

  -----Original Message-----
  From: Steven J. McDowall [mailto:sjmcdowall@uswest.net]
  Sent: Tuesday, August 08, 2000 6:44 AM
  To: soap-dev@xml.apache.org
  Subject: RE: i18n (was: rpcrouter servlet committed)


  3) Since all HTTP headers MUST be emitted first, if anyone can think of
  another way to figure out the reply size before it's done, I'm all ears!
  The only other option is to store the response to a file first, then read
  in back..but that's almost worst IMHO.


View raw message