[racket-dev] URL escaping: question for web experts

Not an expert, don't even do much in this area much these days.
 Historically, I have seen a number of REST URL API patterns, more often
then not (when these things were less tepid than they are now) in the
Semantic Web area (e.g. MS OData) where parens, which as I recall is
allowed by the RFC, are lifted to distinguished delimiters in the URI
template.   But REST, HTTP APIs. et al have seen their heyday and shall
remain Web-centric remnants.  5 years from now I doubt any newly minted
mobile device centric TCP/IP Internet APIs will be based on REST, HTTP and
URIs.  But my crystal ball tends to be foggier than even most.

Frankly I doubt you would break anything in the Racket ecosystem if you did
it.  Personally, I'd not do it solely on the merit of copy/paste easing.  I
have felt the pain in the opposite direction where a browser or tool has
somewhat arbitrarily gone out of the way to escape parens when I'm trying
to cut/paste and I've had to restore them.   So FWIW, -1.


On Mon, Dec 17, 2012 at 2:56 PM, Eli Barzilay <eli at barzilay.org> wrote:

> Just now, David Vanderson wrote:
> > No guru here, but my experience has been that every url encoder is
> > slightly different - I don't think there's a broad consensus on edge
> > cases.  I'd say go for it.
>
> The problem is not just being different from others, it's the
> possibility of old code breaking...
>
> --
>           ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
>                     http://barzilay.org/                   Maze is Life!
> _________________________
>   Racket Developers list:
>   http://lists.racket-lang.org/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/dev/archive/attachments/20121217/5259346c/attachment.html>