Re: ERRest and JSONP?
Re: ERRest and JSONP?
- Subject: Re: ERRest and JSONP?
- From: Jesse Tayler <email@hidden>
- Date: Mon, 19 Mar 2012 20:40:46 -0400
Sounds like I'll be implementing JSONP
Seems like there's two steps
1 implement a callback called 'callback' or make one based on a parameter sent from the client.
2 wrap the whole JSON in some seemingly standard looking javascript tags, such that it can execute as a script on the client.
so, this defined callback function gets called when data arrives at the client and poof! there's some properties to use right there in JSON.
seems like I could properly support JSONP by using an ERRest route .jsonp and look for a callback function name or return callback with the JSON and everyone should be happy, even if they do use some form of IE
suggestions?
On Mar 19, 2012, at 8:13 PM, Pascal Robert <email@hidden> wrote:
>
> Le 2012-03-19 à 20:10, Jesse Tayler a écrit :
>
>>
>> I can see that JSONP is basically just some padding that makes it resemble executable javascript, thus I presume stoking the heap with your properties.
>>
>> I hear that the window.name trick has been deprecated on some newer browsers and no longer works?
>>
>> I don't know about such things, but, I did read a bit here https://developer.mozilla.org/En/HTTP_Access_Control
>
> That's the Same Origin Policy stuff, it's already in ERRest.
>
>> also -- foursquare and google seem to use jsonp extensively - so, I'm not sure why that is.
>
> Probably because they want to support IE 6...
>
>> can anyone point me to anywhere I might learn more about this?
>>
>>
>>
>> On Mar 19, 2012, at 7:58 PM, Pascal Robert <email@hidden> wrote:
>>
>>>
>>> Le 2012-03-19 à 15:55, Jesse Tayler a écrit :
>>>
>>>> Yes, I was reading that earlier.
>>>>
>>>> It seems some suggest jsonp has security issues, but what if a UI programmer really prefers jsonp?
>>>
>>> I don't know why someone would prefer JSONP than Same Origin Policy, who don't require anything on the client side (you only need something server-side to be able to answer the OPTIONS request).
>>>
>>>> Has anyone implemented it or has advice or how I should redirect the technique were using for the ui here?
>>>
>>> I guess JSONP would have to implemented like the window.name support.
>>>
>>>>
>>>>
>>>> Sent from my iPad
>>>>
>>>> On Mar 19, 2012, at 3:41 PM, Pascal Robert <email@hidden> wrote:
>>>>
>>>>> Because nobody added support for it :-) The only thing ERRest supports right now is Same Policy Origin and window.name:
>>>>>
>>>>> http://wiki.wocommunity.org/display/WONDER/ERRest+Framework#ERRestFramework-SameOriginpolicy
>>>>>
>>>>>> Isn't jsonp easy to support via Errest?
>>>>>>
>>>>>> Security problem?
>>>>>>
>>>>>> What to do when we have a JavaScript that must run on external domains?
>>>>>>
>>>>>> Seems that jsonp is what is used most and it seems like a js wrapper that should be easy to put in?
>>>>>>
>>>>>> Sent from my iPad
>>>>>> _______________________________________________
>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>> Webobjects-dev mailing list (email@hidden)
>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>
>>>>>> This email sent to email@hidden
>>>>>
>>>
>>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden