Author: yurize
Date: Fri Nov 18 12:23:20 2011
New Revision: 798869

Log:
Publishing merge to wave site by yurize

Modified:
    websites/production/wave/   (props changed)
    websites/production/wave/content/wave/about.html

Propchange: websites/production/wave/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Fri Nov 18 12:23:20 2011
@@ -1 +1 @@
-/websites/staging/wave/trunk:785678-797293
+/websites/staging/wave/trunk:785678-798867

Modified: websites/production/wave/content/wave/about.html
==============================================================================
--- websites/production/wave/content/wave/about.html (original)
+++ websites/production/wave/content/wave/about.html Fri Nov 18 12:23:20 2011
@@ -72,8 +72,8 @@ collaboration systems, such as multiple 
 <h2 id="history">History</h2>
 <h3 id="pre-history">Pre-history</h3>
 <p>One of the fundamentally technologies that enables the Wave Protocol to 
work is the idea of “<a 
href="http://en.wikipedia.org/wiki/Operational_transformation";>Operational 
Transformations</a>” Essentially a method to keep document changes in sync 
while spread over a network, invented by C. Ellis and S. Gibbs.
-While it is not the intention of this document to explain how OT works, or its 
full history, you can read a good technical explanation <a 
href="http://www.codecommit.com/blog/java/understanding-and-applying-operational-transformation";>here</a>;
-http://www.codecommit.com/blog/java/understanding-and-applying-operational-transformation</p>
+While it is not the intention of this document to explain how OT works, or its 
full history, you can read a good technical explanation <a 
href="http://www.codecommit.com/blog/java/understanding-and-applying-operational-transformation";>here</a>;<br
 />
+</p>
 <h3 id="google_wave_2009">Google Wave (2009)</h3>
 <p>Originally unveiled at a <a 
href="http://en.wikipedia.org/wiki/Google_I/O";>Google I/O</a> conference in May 
2009, Google Wave was Google's attempt to create integrated messaging system 
allowing real-time sharing of messages between selective groups of people. It 
communicated using the open “Wave Federation Protocol” with the intention 
that it could one day replace email, with many companies hosting their owns 
servers and exchanging messages with each-other seamlessly.
 This being a distinct advantage over other systems to selective share 
information, which almost all require the people communicating to hold accounts 
with the same company's server. (eg, Facebook, Google Plus)


Reply via email to