Pluggable RPC transports

[dankurka]

Originally reported on Google Code with ID 2224

Found in GWT Release:

1.5

Detailed description:

RPC needs pluggable transports to handle these use cases:

 - <script>-tag cross-site post/pickup requests (post to a hidden 
iframe, pickup result via script)
 - Inter-frame RPC between GWT modules

Based on BobV's note, it should be possible to convert Request to an
interface and allow a pluggable RequestBuilder to return any implementation
under the covers.

Workaround if you have one:

No easy solution.

Links to the relevant GWT Developer Forum posts:

http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_frm/thread/d809d90708914a88

Note some similar issues:

http://code.google.com/p/google-web-toolkit/issues/detail?id=2055&q=rpc&start=100
"Cross-Domain RPC doesn't work because of browser's Same Origin Policy."

Reported by mmastrac on 2008-03-27 21:45:47

[dankurka]

Reported by gwt.team.bobv on 2008-03-27 22:32:18

• Labels added: Type-Enhancement, Category-RPC
• Labels removed: Type-Defect

[dankurka]

This is out of scope for 1.5; scheduling it for later.

Reported by gwt.team.bobv on 2008-04-01 17:22:32

• Labels added: Priority-High, Milestone-Planned
• Labels removed: Priority-Medium

[dankurka]

Placing this here so the requirement doesn't get lost:

Some of the alternate transports will require pluggable serialization streams.

Use cases:

- Interaction with non-server RPC targets.  For example, inter-frame communication
would require JSON-compatible serializers on both sides.
- Interaction with non-GWT server backends.  For example, a simple server written in
mod_python with JSON libraries available.

Reported by mmastrac on 2008-04-02 02:12:05

[dankurka]

Migrating open issues: gwt.team.bobv -> bobv@google.com

Reported by bobv%google.com@gtempaccount.com on 2008-04-10 17:17:53

[dankurka]

This is subsumed by issue 1777.

Reported by bobv%google.com@gtempaccount.com on 2008-07-22 17:44:52

• Status changed: Duplicate