Loading ...
Sorry, an error occurred while loading the content.

Re: [soapbuilders] XML encoding options

Expand Messages
  • Simon Fell
    ... I see no reason why anything outside of utf-8 or utf-16 is needed, PocketSOAP will decode the 4 encodings that expat supports (utf8,utf16, us-ascii,
    Message 1 of 2 , Jul 7 3:59 PM
    • 0 Attachment
      On Mon, 07 Jul 2003 15:24:13 -0700, in ws you wrote:

      >
      >There is some work underway in axis land to fix the (inefficient,
      >sporadically broken) XML marshalling in Axis1.1.
      >(see http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19327 )
      >
      >It looks like the fix will simplified if the system *only* supports UTF8
      >and UTF16 encodings, which are what WS-I basic profile say you must use.
      >
      >But there is some pressure to add support for other encodings, depending
      >upon what the client sends in.
      >
      >So I have a question. It is: what are other people going to do?
      >
      >(a) only handle UTF8 or UTF16
      >(b) let people select alternate encodings if they want.
      >
      >I am strongly in favour of (a) as if some impl suddenly starts handing
      >obscure encodings, but everyone else's doesnt, then you dont get the
      >option of switching back ends without exposing yourself to the risk that
      >clients suddenly break.

      I see no reason why anything outside of utf-8 or utf-16 is needed,
      PocketSOAP will decode the 4 encodings that expat supports
      (utf8,utf16, us-ascii, iso-8859-1) but will only ever send utf-8.

      Cheers
      Simon
      www.pocketsoap.com
    Your message has been successfully submitted and would be delivered to recipients shortly.