Opened 11 years ago

Closed 11 years ago

#6253 closed enhancement (wontfix)

Cross-domain GET/POST extend from dojox/rpc/Service

Reported by: carrie.zhxj@… Owned by: Dustin Machi
Priority: high Milestone: 1.3
Component: RPC Version: 1.0
Keywords: Cc: alex
Blocked By: Blocking:

Description (last modified by Dustin Machi)

I have written two new dojox.rpc.transportRegistry components, XDGet and XDPost, for cross-domain rpc, using dojo.io.iframe and dojo.io.script .
Could you please review it, and point out the fault or defect for me.
Thanks, Carrie

The attached files includes:
1, dojoroot/dojox/rpc/XDomain.js
2, dojoroot/dojox/rpc/demos/xdomain.html (demo)
3, dojoroot/dojox/rpc/demos/templates/xdomain.html (demo template)
4, dojoroot/dojox/rpc/SMDLibrary/xdomain.smd (demo smd)

Attachments (4)

XDomain.js (5.1 KB) - added by guest 11 years ago.
xdomain.smd (1.6 KB) - added by guest 11 years ago.
xdomain.html (2.2 KB) - added by guest 11 years ago.
demo html
xdomain.2.html (769 bytes) - added by guest 11 years ago.
demo template

Download all attachments as: .zip

Change History (10)

Changed 11 years ago by guest

Attachment: XDomain.js added

Changed 11 years ago by guest

Attachment: xdomain.smd added

comment:1 Changed 11 years ago by Robert Coup

Cc: alex added
Component: GeneralRPC
Milestone: 1.2
Owner: changed from anonymous to Dustin Machi
Reporter: changed from guest to carrie.zhxj@…
Summary: Beg review for cross-domain GET/POST extend from dojox/rpc/ServiceCross-domain GET/POST extend from dojox/rpc/Service

Alex, apparently you chatted to carriezh on IRC about this? I've pointed out the style-guide requirements already.

Changed 11 years ago by guest

Attachment: xdomain.html added

demo html

Changed 11 years ago by guest

Attachment: xdomain.2.html added

demo template

comment:2 Changed 11 years ago by kriszyp

We already have a cross-domain GET capability with the existing JSONP transport. As far as cross-domain POST, the SMD spec has tentatively included the IFRAME transport (which it appears is what you are implementing). However, as far as I can tell, the inclusion of the IFRAME transport is still an open issue with the SMD spec. There needs to be a solid definition of what IFRAME means in terms of communication on the wire, so that it can be defined in the SMD spec (I don't know what that definition is). Using iframes as the mechanism is a pointless definition, SMD definitions are not intended to define mechanisms, they are intended for servers to define how to access services. The SMD does not care about how you accomplish this communication.

comment:3 Changed 11 years ago by Dustin Machi

Description: modified (diff)
Milestone: 1.21.3

As Kris mentioned, thre is already cross-domain request with the existing JSONP transport. I don't mind adding a version of the XDPost transport. However the code here appears to implement a subclass of dojox.rpc.Service. This is something i'm trying to avoid. We want to impelment plugins that work so an smd can be written and based on the smd the appropriate transports and envelopes will be used. A good example of creating these plugins would be dojox.rpc.JsonRPC.

comment:4 Changed 11 years ago by Dustin Machi

Test Comment for batch edit

comment:5 Changed 11 years ago by Dustin Machi

(In [15954]) test commit to test some updates. Refs #6253

comment:6 Changed 11 years ago by Dustin Machi

Resolution: wontfix
Status: newclosed

Already Exists.

Note: See TracTickets for help on using tickets.