This is not a problem that we have solved yet - as you will be aware, it is a pretty generic problem in Restful systems.
We were experimenting with jsonp in the SinglePageAppViewer that you looked at, but I can't honestly remember whether we had it working or not - I rather doubt it actually. In any event, we don't think that jsonp is the answer, because,
as I understand it, jsonp only works for GET requests anyway.
I think Dan was proposing at one point that the RO spec be extended to cover this scenario, using a tunneling approach, but this was not taken any further forward as I recall.
We think that a more promising angle would be 'CORS' (see e.g. http://en.wikipedia.org/wiki/Cross-origin_resource_sharing ). We have no actual experience of this but,
as we understand it, this would not require any change to the RO spec - we could just implement it within the Restful Objects for .NET server. I'd be interested to hear your views on this? If you (and any others interested) agree then I'll
raise a ticket for it.
Meantime, I'm not sure what else we can do.
1) I'd be happy to put your page on our demo server - but this isn't going to work for development/debugging purposes.
If none of those work then it at least sounds to be that you're doing the right thing in explicitly testing for the RO version and using the appropriate representations.