[sugar] How to handle application protocols

[Eben Eliason]

> I can see that happening for python code. However, Write is part Python,
> part C++. The Python part depends on a specific version of the C++ part,
> so you can't just send over the python part and expect it to work.
>
> Now we don't track the non-python dependencies for an activity anywhere
> as far as I know, so I don't see this working in practice.

This is really just an extension of the bundle transfer idea, by which
anyone should be able to join an activity on the mesh they don't yet
have.  There is overhead involved, but bundles are self-contained
largely for reasons like this.  If the bundle has a newer version,
then it should be simple enough to transfer the entire bundle from A
to B.  Assuming the bundle contains the C++ component, what's the
complication?

- Eben


> > --Noah
> >
> > On Oct 9, 2007, at 4:17 PM, J.M. Maurer wrote:
> >
> > > On Tue, 2007-10-09 at 16:05 -0400, Noah Kantrowitz wrote:
> > >> Change your application version number in the .activity file?
> > >
> > > Well ofcourse.
> > >
> > > But consider this: 3 kids update their Write activity (including the
> > > underlying libabiword), which will also upgrade their AbiCollab
> > > protocol. 7 others don't upgrade yet, and continue to use their old
> > > version of Write/libabiword.
> > > Now kids from both groups will will see each other on the mesh
> > > view, see
> > > shared documents, but when they try to collaborate, it will 'silently
> > > fail'.
> > >
> > > That doesn't look user-friendly to me.
> > >
> > >   Marc
> > >
> > >
> > >
> > >> --Noah
> > >>
> > >> On Oct 9, 2007, at 3:53 PM, J.M. Maurer wrote:
> > >>
> > >>> While fixing some bugs in AbiCollab, I found a bug that I can
> > >>> only fix
> > >>> by breaking the existing protocol. I can also imagine that this will
> > >>> happen more in the future (caused by new features, or other unknown
> > >>> bugs
> > >>> that might need fixing).
> > >>>
> > >>> Do we have any policy on application level protocol changes? At the
> > >>> moment, a "new" AbiCollab will simple refuse to communicate with an
> > >>> "old" AbiCollab.
> > >>>
> > >>> Cheers,
> > >>>   Marc
> > >>>
> > >>> _______________________________________________
> > >>> Sugar mailing list
> > >>> Sugar at lists.laptop.org
> > >>> http://lists.laptop.org/listinfo/sugar
> > >>>
> > >>
> > >
> > >
> >
>
> _______________________________________________
> Sugar mailing list
> Sugar at lists.laptop.org
> http://lists.laptop.org/listinfo/sugar
>