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.