opensocial-samplecontainer and opensocial-reference shouldn't be features either (the feature dependency should be "opensocial-0.6" or "opensocial-0.7", or whatever we actually have support for), it should be a gadget, and state should be stored in the parent site. Right now this means you'd have to use inter frame communication to pass the data, but when/if we get an SignedDataServlet in place the open social code can use that to just do an XHR.
You may want to save cookies, but we explicitly don't do it on purpose, because it's a big security vulnerability. You can never rely on cookies being available between page renders (on igoogle the domain changes every time you move a gadget on your page and on orkut the domain changes every month or so), and when gadgets are cajoled writing cookies will be disabled completely. Gadget developers are told to use setprefs for storing data (and with open social we'll have the infinitely more robust appdata to rely on). The parent site may store / read cookies to implement setprefs and appdata, but actual cookie interaction is intentionally not a part of the gadget spec for these reasons. ~Kevin On Jan 23, 2008 9:57 AM, Cassie <[EMAIL PROTECTED]> wrote: > I was the one who wanted cookies. > I disagree that you will never want to save cookies from within the > iframe. > I need to do it from within the iframe in the sample container (for the > state file) and so it seems like we should come up with a clean way to do > this. (I also don't think it is too far fetched that other libraries may > need it in the future but we can table that for now) > > I can of course copy the cookies.js code into the sample container > features > folder but that is just a gross code duplication issue. Is there a way I > can > reference the cookies.js file from within the samplecontainer feature.xmlas > it stands right now? > > - Cassie > > > > On Wed, Jan 23, 2008 at 9:50 AM, John Hjelmstad (JIRA) <[EMAIL PROTECTED]> > wrote: > > > > > [ > > > https://issues.apache.org/jira/browse/SHINDIG-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561746#action_12561746 > ] > > > > John Hjelmstad commented on SHINDIG-32: > > --------------------------------------- > > > > This was a quick hack used to get the JS Container code in quickly. I'll > > be removing it over time. > > > > > cookies.js should not be under a goog. namespace. > > > ------------------------------------------------- > > > > > > Key: SHINDIG-32 > > > URL: https://issues.apache.org/jira/browse/SHINDIG-32 > > > Project: Shindig > > > Issue Type: Improvement > > > Components: Javascript > > > Reporter: Cassie Doll > > > Assignee: Kevin Brown > > > Original Estimate: 1h > > > Remaining Estimate: 1h > > > > > > The cookies.js file needs to be renamespaced to something else. It > would > > also be helpful if it was moved into a feature so that other features > could > > depend on it. > > > > -- > > This message is automatically generated by JIRA. > > - > > You can reply to this email to add a comment to the issue online. > > > > >
