Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#7833 closed enhancement (fixed)

Standardize the entity body naming convention for dojo.xhr requests

Reported by: ptwobrussell Owned by: James Burke
Priority: high Milestone: 1.4
Component: Core Version: 1.2.0
Keywords: Cc:
Blocked By: Blocking:

Description

The exposure of dojo.xhr in 1.1 was great, but I think its API (as well as that of rawXhrPut and rawXhrPost) could be a little more consistent and flexible if we checked for 'data' versus 'putData' and 'postData' in the requests when hasBody is set to be true.

Although this seems like an API change, it could be implemented in the current code base with FIXMEs left in place to remove putData and postData support as of 2.0 (which would be warts at that point.)

Change History (3)

comment:1 Changed 11 years ago by James Burke

Milestone: tbdfuture
Owner: changed from anonymous to James Burke

comment:2 Changed 10 years ago by James Burke

Resolution: fixed
Status: newclosed

(In [17469]) Fixes #9219, #8649, #7833 and #8724: allow publication of IO pipeline topics, add dojo.fieldToObject (thanks to foobarfighter, CLA on file), allow generic args.rawBody for setting HTTP request bodies, and if hasBody is not passed to dojo.xhr, make an intelligent guess as to whether the query should be in the http body or as a query string. \!strict for dojo.io.script code has not side effects warning, but it is ok.

comment:3 Changed 10 years ago by James Burke

Milestone: future1.4
Note: See TracTickets for help on using tickets.