On Tue, 2007-10-09 at 16:24 -0400, Noah Kantrowitz wrote: > In theory (not sure how implemented this is), when one activity has a > higher version, its code should be automatically pushed to the other > machines.
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. Cheers! Marc > --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 > >>> [email protected] > >>> http://lists.laptop.org/listinfo/sugar > >>> > >> > > > > > _______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
