posting on behalf<br><br><br><div class="gmail_quote"><div class="gmail_quote"><div><div class="h5"><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Jan Zawadzki</b> <span dir="ltr"><<a href="mailto:jan.zawadzki@hapara.com" target="_blank">jan.zawadzki@hapara.com</a>></span><br>
Date: Wed, Jul 21, 2010 at 9:15 AM<br>Subject: [Server-devel] Journal and Google<br>To: <a href="mailto:server-devel@lists.laptop.org" target="_blank">server-devel@lists.laptop.org</a><br><br><br>There are API's for working with Google Docs, that's not the problem.<br>
<br>We can do the sync with the XS in the middle - so rsync to XS, and native Google API's to Google.<br><br>Challenge is in syncing up the individual machines directly to Google Docs without the storage being replicated on the XS.<br>
<br>The underlying assumption is that replication uses rsync - which we can't use easily in the Google land without proxies, etc.<br><br>Jan<br clear="all"><font color="#888888"><br>-- <br>Hapara ● Google Solutions For Your Enterprise<br>
PO Box 106485 Auckland New Zealand<br>
P: +64 4 499 5343 M: +64-27-209-1718<br><a href="http://www.hapara.com" target="_blank">www.hapara.com</a> Twitter: <a href="http://twitter.com/hapara_team" target="_blank">@hapara_team</a><br><br>
</font></div><br>
<br>
</div></div></div><br>
</div><br>