On Tue, Dec 9, 2008 at 12:38 PM, Kevin Brown <[EMAIL PROTECTED]> wrote: > It seems that everyone is agreeing on this conceptually. Where we're running > into problems is with character data, which is of course the common case. If > we mandate that the content's encoding be included in the Content-Type > header, we can probably address this. This way, for encodings like UTF16 it > can be specified. Alternatively, mandate UTF8.
Why do we need special handling of text content-types at all? We can treat them as raw byte streams for the purposes of the crypto, and worry about converting to characters in application level code. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
