You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.
ver: 1.0.0
from email thread with: richardpawson, adamhoward
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.
The text was updated successfully, but these errors were encountered:
ver: 1.0.0
from email thread with: richardpawson, adamhoward
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.
The text was updated successfully, but these errors were encountered: