Awesome, I'll get to implementing right away... I think it should be pretty easy... (although i'm sure i'm overlooking something!)
- Cassie On Tue, Jan 29, 2008 at 1:07 PM, Paul Lindner <[EMAIL PROTECTED]> wrote: > On Tue, Jan 29, 2008 at 12:54:34PM -0800, Cassie wrote: > > > > This versioning of the reference though, that is completely shindig, and > we > > can definitely do it. That is my fault for thinking we could update to > > 0.7quickly. (it should be pretty trivial for the container to do) > > I'd like to get people to 0.7 quickly too, however we now have some > significant investment in 0.6 surfaces support, and will have to be > careful in how we deploy this. > > > The only thing that sucks about this is that the code is 99% the same, > so we > > are going to have nearly duplicate copies around. Also, how many > versions > > back should we support? > > > > Something that I've been thinking about is possible just a > > opensocial6to7.jsfile. This js file will just map all of the old calls > > to the new ones. (so > > opensocial.makeRequest would be defined to just point to the new method) > > > > I like this a lot for many reasons. 1, we don't have duplicate code! 2, > > anybody can just drop in this upgrade js file on their site to support > > multiple versions. 3, if a container doesn't support the old version a > > gadget can import the file themseleves. 4, it gives developers a very > clear > > code based guide to updating their gadget to 0.7 and beyond. > > > > We would have one of these files per version change (6-7, 7-8 etc) > > If I understand what you're saying > > * opensocial-reference-0.7 would depend on opensocial-reference > * opensocial-reference-0.6 would depend on opensocial-reference, > plus have a compatibility shim calls in feature.xml > > I like this idea. > > I'll go forth and create a shindig issue on this... > > -- > Paul Lindner > hi5 Architect > [EMAIL PROTECTED] >
