Opened 14 years ago
Closed 13 years ago
#6253 closed enhancement (wontfix)
Cross-domain GET/POST extend from dojox/rpc/Service
| Reported by: | Owned by: | Dustin Machi | |
|---|---|---|---|
| Priority: | high | Milestone: | 1.3 |
| Component: | RPC | Version: | 1.0 |
| Keywords: | Cc: | alex | |
| Blocked By: | Blocking: |
Description (last modified by )
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)
Change History (10)
Changed 14 years ago by
| Attachment: | XDomain.js added |
|---|
Changed 14 years ago by
| Attachment: | xdomain.smd added |
|---|
comment:1 Changed 14 years ago by
| Cc: | alex added |
|---|---|
| Component: | General → RPC |
| Milestone: | → 1.2 |
| Owner: | changed from anonymous to Dustin Machi |
| Reporter: | changed from guest to [email protected]… |
| Summary: | Beg review for cross-domain GET/POST extend from dojox/rpc/Service → Cross-domain GET/POST extend from dojox/rpc/Service |
comment:2 Changed 14 years ago by
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 14 years ago by
| Description: | modified (diff) |
|---|---|
| Milestone: | 1.2 → 1.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.
Alex, apparently you chatted to
carriezhon IRC about this? I've pointed out the style-guide requirements already.