[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [uddi-spec] Proposed changes to UDDI Version 2 specificationsrelated to UTF-8 / UTF-16 issue
Max, I think a registry MAY regard the encoding of incoming request message as a preferred encoding. Please note that, if we update v2 spec to support both encodings, it means that both client and server have to support both encodings. Response encoding is left upto the Operator. Regards, -- Keisuke Kibakura FUJITSU LIMITED >>>>> On Wed, 02 Oct 2002 07:16:22 +1200, >>>>> Max Voskob <mvoskob@msi.com.au> wrote : > Keisuke, > > I would agree with you, but how are we going to determine what encoding the > response should be in any particular case? Is it left upto the Operator > Site? > The response must be of the same encoding or otherwise, the client must > indicate what encoding it prefers. > > Max Voskob, > MSI Business Solutions NZ
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC