[OASIS Issue Tracker] Issue Comment Edited: (CMIS-662) Specify acallback parameter

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21976#action_21976 ] 

Florent Guillaume edited comment on CMIS-662 at 10/7/10 5:32 AM:
-----------------------------------------------------------------

Thanks for the JSONP links, I wasn't aware that this pattern was in wide use.
I'm happy with allowing this technique to be used, I was just wary of having the parameter just be named "callback".  Note that the JSONP example uses ?jsonp=  , Google uses ?alt=json-in-script&callback= and Yahoo uses ?output=json&callback=
We could use ?jsonp= for instance.

Note that this technique still has drawbacks: it's usually synchronous and stalls the loading of the rest of the web page (unless the modern async or defer attributes are used). So it's still useful to process the JSON asynchronously (using AJAX), and whenever several asynchronous calls are in progress there is a need to distinguish the different results returned, therefore my proposal to allow an arbitrary opaque token to be passed with the request and then returned with the response. The name "callback" in this case is a misnomer, we could just name it "token" or "clienttoken".


      was (Author: florent.guillaume):
    Thanks for the JSONP links, I wasn't aware that this pattern was in wide use.
I'm happy with allowing this technique to be used, I was just wary of having the parameter just be named "callback".  Note that the JSONP example uses ?jsonp=  , Google uses ?alt=json-in-script&callback= and Yahoo uses ?output=json&callback=
We could use ?jsonp= for instance.

Note that this technique still has drawbacks: it's usually synchronous and stalls the loading of the rest of the web page (unless the modern async or defer attributes are used). So it's still useful to process the JSON asynchronously (using AJAX), and whenever several asynchronous calls are in progress there is a need to distinguish the different results returned, therefore my proposal to allow an arbitrary opaque token to be passed with the request and then returned with the response. The name "callback" in this case is a misnomer, we could just name is "token" or "clienttoken".

  
> Specify a callback parameter
> ----------------------------
>
>                 Key: CMIS-662
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-662
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Browser Binding
>    Affects Versions: Browser Binding Proposal
>         Environment: All
>            Reporter: Gregory Melahn
>            Priority: Minor
>
> Recognizing that the Browser Binding proposal is not a proposal for a JavsScript API (as decided in our first meeting of the Browser Binding subcommittee), still it would be convenient if browser clients could handle the returned JSON data directly using a JavaScript function.   For example, if I had a JavaScript function that understood how to parse and render the JSON representation of the contents of a CMIS folder answered by getChildren, then I could specify this function directly in the GET request for getChildren.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira