File system integration is a great feature. It allows to directly access and stream large files before they are completely downloaded and is the basis of the planned write access. Unfortunately, it is hard to make it work reliably on Windows. Often, it takes one or two minutes until Windows can connect to the Wuala drive. The latest update brings some improvements and compatibility with 64-Bit systems (read below on how I could made it work on my 64-Bit Vista SP1). I'll link from the Wuala settings directly to this article so this is the right place to discuss issues and tricks on how to make it work.
I am attempting to use the filesystem integration provided by Wuala in Ubuntu, but am running into an issue. I've got the nfs share mounted, everything shows up ok, but if I'm wanting to add files to a playlist in my media player or run unison, it gets choked up with the many gigs worth of data I'm throwing at it. When I add just 13 songs to any media player, it only pulls in a couple then stops. It isn't able to pull all the songs.
I used the wuala guide on setting up the nfs share in my fstab. Here's the link I followed. http://wua.la/en/kb/4 I noticed the bottom mentioning Ubuntu and have wondered if that is part of my issue.
lately i have experimented with wuala and fileintegration on win32 (xp) and latest wuala builds (426). i was copying whole cd contents (different files, loads of folder structures) into a semi-private (group/friendshared(only 1 friend as an example/test)) to the wuala network drive (w: for example).
the copying went normally, but only some days after (this happened first some days ago, but i verified it today with other content (CDs)) i realized that the uploaded wuala content of the folder i copied the files into wasnt exactly the same as my original sources. some bytes/megabytes were missing, and i tracked down some of the files/folders that were created but only with filesize=0 (zero), or were missing completely.
i was copying the stuff with the help of total commander, so not the basic builtin explorer.exe functions, nor commandline copy stuff...
i might try some more of this stuff at a later time.
the missing/incomplete files dont seem to follow any certain rules or patterns, there are simply some folders that are completely identical/complete and some files are missing or come with zero size.
totalcommander never complained that it couldnt write to w: or anything else like that.
i was manually looking for the differences, found the missing/incomplete files and was overwriting the files on the wuala store again.
after these second tries and overwriting procedure the wuala store was eventually finally complete and identical to my source material.
i guess that some of the queues in the wuala client, the pending transactions, the chunk-creation and distribution or related functions and parts of the wuala client program are still lacking robustness.
please take a look at this and do your own tests with lots of files/folders and different objectsizes.
thanks.
So I am an active linux developer who has spotted some very cool possibilities for Wuala. Right now, the problem is, I can't access any of the awesome! While I understand fully that preping an API for the public is a lengthy process, could you just offer a simple dbus/com service. An undocumented client library would rock too. Or even just making the mounted filesystem support 'query directories' etc. I'm not picky, I just want to harness a universally available and decentralized file store for some collaborative apps (non-realtime of course) . Specifically any DRCS (or even subversion to a degree) would love this.
I've updated my Vista today with Service Pack 1. After the final restart Wuala is not anymore integrated within my file system. I have restarted my Vista several times (with deactivated Windows Firewall) but without success.