> -----Original Message----- > From: Kimbro Staken [mailto:[EMAIL PROTECTED] > Sent: 19 February 2002 12:49 > To: [EMAIL PROTECTED] > Subject: Re: Some delving into XML-RPC > > > > On Tuesday, February 19, 2002, at 04:35 AM, Kimbro Staken wrote: > > > > SOAP should have the same issue, as should any solution > that is used from > > non-unicode languages. I'm sure the CORBA impls for > something like PHP > > would have the same problem (I'm assuming PHP still doesn't support > > unicode but I really don't know). The question, is it safe > within the > > scope of unicode languages? > > I just took a look at the spec, (my connection was down before) it > explicitly defines a string as an ASCII string. So your concern is > probably legitimate. It also says "A string can be used to > encode binary > data.", which implies to me it's saying to treat it like an > array of bytes. > If that's true then we may be OK. It's rather ambiguous > though. There's > base64 too, of course. >
I think when they say "a string can be used to encode binary data", they are referring to a bytestream-to-ASCII conversion such as base64. That's what O'Reilly's book sais anyways. I'm in the process of trying out Apache XML-RPC's behaviour on the strings issue. I'll get back when I have some definite results. James > >> > Kimbro Staken > XML Database Software, Consulting and Writing > http://www.xmldatabases.org/ > > > >
