[jira] Commented: (TS-254) Add INKEscapifyString() and INKUnescapifyString()

["Miles Libbey (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847120#action_12847120 ] 

Miles Libbey commented on TS-254:
---------------------------------

(And don't forget about documentation :) -- can file a jira with:
- Where it should live (for instance, Function Reference/HTTP Functions/  HTTP Transaction Functions)
- suggested text in a similar format to 
http://incubator.apache.org/trafficserver/docs/sdk/HTTPFunctions.html
(ie, what it does; prototype; description; returns, and possibly an example)


> Add INKEscapifyString() and INKUnescapifyString() 
> --------------------------------------------------
>
>                 Key: TS-254
>                 URL: https://issues.apache.org/jira/browse/TS-254
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: InkAPI
>            Reporter: Leif Hedstrom
>            Priority: Minor
>
> It would be very convenient for plugin developers to have SDK APIs that allows for escaping and unescaping of strings. E.g.
> INKEscapifyString("http://www.ogre.com/ogre.png")
>      ->  http%3A%2F%2Fwww.ogre.com%2Fogre.png
> INKUnescapifyString("http%3A%2F%2Fwww.ogre.com%2Fogre.png)
>      -> http://www.ogre.com/ogre.png
> The "unescapify" string is fairly straight forward, bt the "escapify" version might benefit from taking an (optional) table which describes what characters needs to be escaped (e.g. in in some cases you want a / to be escaped, but in others you do not).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.