You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Paul Lindner (JIRA)" <ji...@apache.org> on 2009/06/06 02:16:07 UTC
[jira] Commented: (SHINDIG-1065) osapi (oslite) should support user
mediated requests.
[ https://issues.apache.org/jira/browse/SHINDIG-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716806#action_12716806 ]
Paul Lindner commented on SHINDIG-1065:
---------------------------------------
The concept and the patch look pretty good. Before I dive in too deep here can others comment?
> osapi (oslite) should support user mediated requests.
> -----------------------------------------------------
>
> Key: SHINDIG-1065
> URL: https://issues.apache.org/jira/browse/SHINDIG-1065
> Project: Shindig
> Issue Type: New Feature
> Components: Javascript
> Reporter: Sachin Shenoy
> Attachments: ui-introspected.patch, ui.patch
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> According to osapi spec any request can be user mediated. (there is no more osapi.ui.*). Shindig to support mechanism for user mediated requests.
> Changes:
> - Containers can via configuration let shindig JS know which requests it want to be user mediated.
> - Predefined hooks are used to pass the request to the container and get the response back.
> - A new type of request, osapi.newUiRequest is defined to handle user mediated case. Even though this is in global space, it need not be visible to the developer directly. Developer uses the osapi as today.
> - batch.js is modified to allow handling of user mediated requests.
> - So that developer can know which request may get user mediated, every request exposes a boolean field userMediated (this is not part of standard but could be good to have something like this for future version). This would allow developers to write code like below,
> var r = osapi.activites.create();
> if (r.userMediated) {
> // skip creating activity, as I don't want to bug the user.
> } else {
> r.execute();
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SHINDIG-1065) osapi (oslite) should support
user mediated requests.
Posted by Louis Ryan <lr...@google.com>.
Paul
See the osapi over rpc codereview I sent out. It subsumes this. Comments
welcome as I'd like to get that checked in soon. Assigning this to myself.
-Louis
On Fri, Jun 5, 2009 at 5:16 PM, Paul Lindner (JIRA) <ji...@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/SHINDIG-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716806#action_12716806]
>
> Paul Lindner commented on SHINDIG-1065:
> ---------------------------------------
>
> The concept and the patch look pretty good. Before I dive in too deep here
> can others comment?
>
>
> > osapi (oslite) should support user mediated requests.
> > -----------------------------------------------------
> >
> > Key: SHINDIG-1065
> > URL: https://issues.apache.org/jira/browse/SHINDIG-1065
> > Project: Shindig
> > Issue Type: New Feature
> > Components: Javascript
> > Reporter: Sachin Shenoy
> > Attachments: ui-introspected.patch, ui.patch
> >
> > Original Estimate: 72h
> > Remaining Estimate: 72h
> >
> > According to osapi spec any request can be user mediated. (there is no
> more osapi.ui.*). Shindig to support mechanism for user mediated requests.
> > Changes:
> > - Containers can via configuration let shindig JS know which requests it
> want to be user mediated.
> > - Predefined hooks are used to pass the request to the container and get
> the response back.
> > - A new type of request, osapi.newUiRequest is defined to handle user
> mediated case. Even though this is in global space, it need not be visible
> to the developer directly. Developer uses the osapi as today.
> > - batch.js is modified to allow handling of user mediated requests.
> > - So that developer can know which request may get user mediated, every
> request exposes a boolean field userMediated (this is not part of standard
> but could be good to have something like this for future version). This
> would allow developers to write code like below,
> > var r = osapi.activites.create();
> > if (r.userMediated) {
> > // skip creating activity, as I don't want to bug the user.
> > } else {
> > r.execute();
> > }
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
Re: [jira] Commented: (SHINDIG-1065) osapi (oslite) should support
user mediated requests.
Posted by Louis Ryan <lr...@google.com>.
Paul
See the osapi over rpc codereview I sent out. It subsumes this. Comments
welcome as I'd like to get that checked in soon. Assigning this to myself.
-Louis
On Fri, Jun 5, 2009 at 5:16 PM, Paul Lindner (JIRA) <ji...@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/SHINDIG-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716806#action_12716806]
>
> Paul Lindner commented on SHINDIG-1065:
> ---------------------------------------
>
> The concept and the patch look pretty good. Before I dive in too deep here
> can others comment?
>
>
> > osapi (oslite) should support user mediated requests.
> > -----------------------------------------------------
> >
> > Key: SHINDIG-1065
> > URL: https://issues.apache.org/jira/browse/SHINDIG-1065
> > Project: Shindig
> > Issue Type: New Feature
> > Components: Javascript
> > Reporter: Sachin Shenoy
> > Attachments: ui-introspected.patch, ui.patch
> >
> > Original Estimate: 72h
> > Remaining Estimate: 72h
> >
> > According to osapi spec any request can be user mediated. (there is no
> more osapi.ui.*). Shindig to support mechanism for user mediated requests.
> > Changes:
> > - Containers can via configuration let shindig JS know which requests it
> want to be user mediated.
> > - Predefined hooks are used to pass the request to the container and get
> the response back.
> > - A new type of request, osapi.newUiRequest is defined to handle user
> mediated case. Even though this is in global space, it need not be visible
> to the developer directly. Developer uses the osapi as today.
> > - batch.js is modified to allow handling of user mediated requests.
> > - So that developer can know which request may get user mediated, every
> request exposes a boolean field userMediated (this is not part of standard
> but could be good to have something like this for future version). This
> would allow developers to write code like below,
> > var r = osapi.activites.create();
> > if (r.userMediated) {
> > // skip creating activity, as I don't want to bug the user.
> > } else {
> > r.execute();
> > }
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>