You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Kevin Brown (JIRA)" <ji...@apache.org> on 2008/03/06 09:01:58 UTC

[jira] Updated: (SHINDIG-35) Create a demo of a server side container

     [ https://issues.apache.org/jira/browse/SHINDIG-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Brown updated SHINDIG-35:
-------------------------------

    Component/s:     (was: Gadgets Server - Java)
                 Wishlist
       Assignee:     (was: John Hjelmstad)
       Priority: Minor  (was: Major)

Unassigning and recategorizing this one since the bulk of this discussion is being broken into separate issues, and because a final implementation decision for how OAuth is going to work hasn't been made yet. We'll want to revisit this at some point in the future. We may want to just close this issue and focus on oauth for now.

> Create a demo of a server side container
> ----------------------------------------
>
>                 Key: SHINDIG-35
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-35
>             Project: Shindig
>          Issue Type: New Feature
>          Components: Wishlist
>            Reporter: Brian Eaton
>            Priority: Minor
>         Attachments: oauth.patch, sillyoauthgadget.js, testgadget.xml
>
>
> I'd like Shindig to have a sample implementation of a server-side container.
> I definitely don't want to build any type of robust or scalable user registry to go along with this work.  I'd like to see scaffolding, not a lot of implementation.
> The ability to store user preferences on the server rather than the client would be a reasonable first milestone.  A next milestone would be support for OAuth in gadgets.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.