Opened 15 years ago

Closed 7 years ago

#5229 closed enhancement (wontfix)

Support for alternate URL argument formatting

Reported by: guest Owned by: Bryan Forbes
Priority: high Milestone: 1.11
Component: IO Version: 1.0
Keywords: Cc: [email protected]
Blocked By: Blocking:

Description (last modified by bill)

Currently, the content object passed to xhr[Get|Post] is formatted using ?'s, &'s and ='s, which is generally groovy.

However, in the case of a site which implements MVC style URL's, this isn't very friendly.

Rather than "?param1=value1&param2=value2", it would be useful to be able to have /'s used for each separator, ala "/param1/value1/param2/value2".

My particular case revolves around the use of, but I think that providing the solution at that level is really only a short-term solution.

I'm surprised this hasn't come up before... but I guess the fact that it hasn't may mean I'm a genuine minority. I do realize that this functionality can be implemented by simply eliminating the content argument and generating the full URL by hand, but I can't help but feel that that is a hackish solution.

Change History (10)

comment:1 Changed 14 years ago by dylan

Milestone: 1.3

comment:2 Changed 14 years ago by wolfram

What you are mentioning here is actually pretty easy to do by extending the QueryReadStore?-class and customizing the URL to be used. See and the examples*.html you should see that extending the class "DojoDataSortable?" and customizing the store's URL instead of passing the query/serverQuery parameters in requestRow() would do this task.

comment:3 in reply to:  2 Changed 14 years ago by guest

Replying to wolfram: Yeah, that is in fact what I did... I created a customized class for the QueryReadStore requests.

It just seems to me that it could be really easily done further up the tree, within the scope of the toolkit itself... I may well be mistaken, but that was certainly my thinking at the time.

Thanks for the suggestion.

comment:4 Changed 14 years ago by wolfram

In my opinion the customization of the url can be very extensive that I would see it as a separate thing. Though I would be interested in seeing what you built, if you can show it. May be there could be some kind of dojox.RequestBuilder? or alike, which could take care of something like that ... or may the RequestBuilder? is a stupid idea :-)

I would like to know other people's opinions.


comment:5 Changed 14 years ago by bill

Description: modified (diff)
Milestone: 1.3future

move unowned / abandoned tickets to "future" milestone

comment:6 Changed 11 years ago by Chris Mitchell

Owner: anonymous deleted

comment:7 Changed 10 years ago by bill

Component: GeneralIO
Owner: set to Bryan Forbes

comment:8 Changed 9 years ago by dylan

Milestone: future1.9

Bryan, any thoughts on what to do with this in the context of dojo/request?

Let's address and either close it out or consider something for 2.0.

comment:9 Changed 9 years ago by bill

Milestone: 1.92.0

Since we released the beta for 1.9, presumably this enhancement should be bumped to 2.0.

comment:10 Changed 7 years ago by dylan

Milestone: 2.01.11
Resolution: wontfix
Status: newclosed

If this is still desired, it will be address for dojo 2 ( ). Closing this out.

Note: See TracTickets for help on using tickets.