On 10/7/07, Jürgen Ragaller <[EMAIL PROTECTED]> wrote: > Am Oct 7, 2007 um 1:22 schrieb [EMAIL PROTECTED]: > > The 1.3 specifications include no locks. Globally distributed > > applications cannot have any locking. Two people edit on one server, > > another is editing on another server, and a third is editing a local > > repository while disconnected from the network. Lenya cannot mature > > while using that obsolete paradigm. > > I don't think that lenyas checkout/locking mechanism for a cms is an > obsolete paradigm. > > Checkout (Lock) informs editors working together on their site about > other people working on the same document already. Working > collaboratively on a website requires a lot of coordination > (editorial work) - a single server providing information about who is > doing what supports the team; lenya 2.0 helps with the features: > notification, overviews for admin and checkout. > > If two people accidentially work on the same document, they would > have to merge their text somehow (a svn approach); this makes more > sense for program code then for cms text (for program code it's > difficult already...). > > Disconnected work requires only a connection for the checkout / > checkin; in between the offline work (in open office for example) is > possible. > Jürgen Ragaller
Start with your last statement. Pretend everybody works disconnected. What was the purpose of the locking system? People want to work on the same document. The only purpose of the locking system is to prevent people from being productive. A merge may be needed, but that is true whenever several people want to edit the same document. Think Wiki. Temporary locking does not prevent material from being overwritten by the next editor. Locking annoys people trying to work. Locking often gets stuck; the most common support request with any locking system is to have something unlocked. Locking is useless in a distributed environment because too many people will bypass it. The topic of this thread was preventing editors from easily and frequently leaving documents locked. Removing locks eliminates that issue. solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
