The project, called revShare, was commissioned by David Johnson, and as such, is his property. You may try and contact him directly to find out more. At the time it was created, things worked by updating changes via FTP to a server and reading them via HTTP. The idea was it should be able to accomodate synchronous and asynchronous communications. So, if someone made a change to a stack they were sharing with you, yours would update as soon as you came online, no matter if they were online or not. Sort of a cloud based stack sharing system.
On Fri, Mar 18, 2011 at 11:06 AM, Bob Sneidar <b...@twft.com> wrote: > Hi Chipp. Any chance that stack still works? That is a great idea. > > Bob > > > On Mar 18, 2011, at 1:20 AM, Chipp Walters wrote: > > > Yep, years ago I wrote a stack sharing library for Rev which passed back > and forth via a server any changes made to stacks, thus allowing multiple > people in remote locations to work on the same stack at the same time, and > used the base64encode trick you mention to encode all meta data for all > controls and their properties. Worked well. > > > > Chipp Walters > > CEO, Shafer Walters Group, Inc > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- Chipp Walters CEO, Shafer Walters Group, Inc. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
