I will write my own if I have to. But before I do, I'd like to understand as
many details as possible about the specifics of Twitter's RFC 3986 behavior.
In my experience with RFC specs, they usually provide a lot of detail but
they almost always leave some of those details to be interpreted by
implementors and those interpretations are not always the same. No spec is

On Thu, May 20, 2010 at 1:28 PM, Cameron Kaiser <spec...@floodgap.com>wrote:

> > FYI - I am writing a .Net based library and so I currently use
> > System.Uri.EscapeDataString<
> http://msdn.microsoft.com/en-us/library/system.uri.escapedatastring.aspx
> >to
> > do my escaping
> I don't know what that routine is, but if it's not RFC 3986 compliant, it
> won't work. You might want to roll your own, it's a couple lines of code
> and a regex.
> --
> ------------------------------------ personal:
> http://www.cameronkaiser.com/ --
>  Cameron Kaiser * Floodgap Systems * www.floodgap.com *
> ckai...@floodgap.com
> -- "EH! STEVE!"
> ---------------------------------------------------------------

Reply via email to