If the users must use a spreadsheet, how about the google apps spreadsheet? It is by its nature shareable.<div><br></div><div>/Ritchie<br><br><div class="gmail_quote">On Mon, Feb 16, 2009 at 7:48 AM, Bernd Felsche <span dir="ltr"><<a href="mailto:berfel@innovative.iinet.net.au">berfel@innovative.iinet.net.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div></div><div class="Wj3C7c">Richard Meyer <<a href="mailto:meyerri@westnet.com.au">meyerri@westnet.com.au</a>> wrote:<br>
>On Sun, 2009-02-15 at 22:13 +0900, Bernd Felsche wrote:<br>
>> Leon Brooks <<a href="mailto:leon-plug@cyberknights.com.au">leon-plug@cyberknights.com.au</a>> wrote:<br>
>> >On Sunday 15 February 2009 20:43:32 Bernd Felsche wrote:<br>
<br>
>> >> I've looked at a number of options including<br>
>> >> Intermezzo, Unison, Lustre, ...<br>
<br>
>> >> They tend to fall into one or more of the following<br>
>> >> categories:<br>
<br>
>> >> 1) too complicated for the users.<br>
>> >> (Unison is a steep learning curve)<br>
>> >> 2) no longer supported (Unison)<br>
>> >> 3) probably unsuited for slow<br>
>> >> (unreliable) links (Lustre)<br>
<br>
>> >> What remain are (Open)AFS and Coda.<br>
<br>
>> >Is RSync feasible? Aussie origin 'n' all (Tridge). Easy<br>
>> >enough to make a one-click icon to do an RSync sync from<br>
>> >the 'Doze boxes. Your choice of whether each RSync login<br>
>> >is read-only or not (plus of course usual chmod stuff).<br>
<br>
>> Sadly not feasible as it requires interaction for synchronisation<br>
>> (or file monitoring) and the synchronisation direction varies, as<br>
>> well as the possibility of "collisions" with the likelihood of two<br>
>> users (finite probability) wishing to make changes to the file<br>
>> simultaneously.<br>
<br>
>> The direction of synchronisation also varies unpredictably. It's<br>
>> not like there's one master file that's copied and only read on<br>
>> "slaves".<br>
<br>
>> rsync is currently being used for other files where there's a master<br>
>> copy at head office and the branches get a read-only copy on their<br>
>> server. It works well for that.<br>
<br>
>I presume I'm WAAAYY too late in pointing out that this sort of thing is<br>
>what DBMSs were developed for ....<br>
<br>
</div></div>I understand completely.<br>
<br>
Sadly the users don't; and want to use Excel spreadsheets.<br>
(i.e. waste their time diddlying)<br>
<div class="Ih2E3d"><br>
>.. and also not all that helpful. :-(<br>
<br>
>I'd also like to see what your solution ends up being ...<br>
<br>
</div>I'll let you know. At the moment, OpenAFS is still the front-runner<br>
with Coda a close second. Too few options for comfort, which is why<br>
I'm asking for suggestions of others (and possible gotchas).<br>
<div class="Ih2E3d">--<br>
/"\ Bernd Felsche - Innovative Reckoning, Perth, Western Australia<br>
\ / ASCII ribbon campaign | Religion is regarded by the common people<br>
X against HTML mail | as true, by the wise as false, and by the<br>
/ \ and postings | rulers as useful. -- Seneca the Younger<br>
<br>
_______________________________________________<br>
</div><div><div></div><div class="Wj3C7c">PLUG discussion list: <a href="mailto:plug@plug.org.au">plug@plug.org.au</a><br>
<a href="http://www.plug.org.au/mailman/listinfo/plug" target="_blank">http://www.plug.org.au/mailman/listinfo/plug</a><br>
Committee e-mail: <a href="mailto:committee@plug.linux.org.au">committee@plug.linux.org.au</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ritchie Young<br><a href="http://rubysync.org">http://rubysync.org</a><br><br>
</div>