a main problem with the wuala project as whole is, that there is far too little information on technical details, far too little documentation and real information given by the developers.
people often wonder why the wuala software behaves this or the other way, search for solutions that are sometimes no real problems if the behaviour would be properly documented.
i started up some older build (winxp) wuala client after a while of downtime and it upgraded itself.
after logging in to the wuala network (username) the wuala client now works heavily on the wuala database files in probably reoganisation tasks (fragmentsxx.db and COMP-fragmentsxx.db files being messed with the whole time)
anyways so it literally took ages for this client to finish, and the connection status icon was yellow all the time. only after a long while, and when finally the insane diskactivity has finished, the connection status icon went green again.
ctrl+alt+d _shownetworkstats displayed that it wasnt connected to any supernodes during this period, hence the yellow icon i presume.
what makes me wonder if this is a neccessary behviour, that the client cant properly connect to the network until its finished with its database overhaul. maybe some multithreading designs could help, or maybe its just really the need to bring the database into a consistant and up-to-date state again before being able to add and fetch chunks of data again to and from it.
it would really be great if the wuala team could document its piece of software much more in detail.
hi there, i wanted to post the official question about what the exact technical requirements and capabilites of network access for wuala are, to allow wuala become a supernode, or a client node and all this techstuff information.
some of my wuala clients only become storage nodes (supernode capability false, and mediated over ip/node .....)
i wonder what the exact technical requirements for the networkconnection of wuala are and if this could be made more transparent to the userbase (documentation).
all of my clients run on highcapacity broadband nodes, but none of the wuala clients run directly on the external ip-address/interface visible to the external inet.
some wuala clients run via a upnp-capable internetgateway, others have normal portforwaring set up properly. all wuala client connections result in a good/green connection. all nodes exchange and host/trade storage.
so far it seems as if supernodecapability was somehow related to upnp-ed connection (or maybe direct inet connection without any firewall/restrictions).
i am wondering if this could be enhanced or why portforwarded wuala clients wont become supernodes.
from time to time i need to startup a wuala client at some remote destination (clients, friends, whatever...) and just log into my wuala useraccount and just dump some files/data into my wuala-space. what i am wondering about how quickly i can logout/close this temporary wuala client so that my uploaded/added data stays alive in my wuala dumpspace.
it would be best if a running client when doing uploads, would first look for other clients running with the same credentials and then trying to dump the data first to these same-account nodes, or maybe after a while there could be also nodes of friends (wuala friends), or the nodes that a wuala node is closest to (network-wise) and so on....
sometimes i have only little time to let this temporary wuala node running, and i dont know when i am on the safe side so that my uploaded file(s) have safely arrived inside the wuala storage space.
maybe you are even already doing this on your clients/nodes, but it hasnt been clear, thats why i have posted this.
i have also read about your plans, there there will be a standalone wuala java-only (non-install) client, which could (probably) run from websites (applet) and so on, without real installation on any operatingsystem that comes with java support.
this would also make sense, to have these java (most likely) temporary clients to first try to communicate to other running clients of the same user, so that they spread modified/new data to the more stable and persistent clients of the same user first, and that those clients then take over the spreading and distribution of the data fragments/parts.
Loading Profile...
Luzius (Official Rep)
last replied
on May 16, 2008 07:21
