On Tue, Mar 10, 2009 at 6:02 AM, Marc Worrell <[email protected]> wrote: > And keeping it simple might mean transcoding all your UTF-whatever > into an octet stream before pushing it into your transport-layer-with- > oauth-signing. > > Which makes it completely according to the specs, but without the > complications for the library.
This is undoubtedly the easiest way to go, assuming that the receiving application has access to the transport layer. Not all receiving apps do. For example, most web development platforms parse out form encodings well before the application gets a chance to peek at the raw octets. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
