0001311: Amulegui cannot connect to amuled after a few hours

Notes
(0002794) wild_oscar (reporter) 2008-04-30 02:56	It seems that the file known.met may be responsible for this problem - deleting this file will make amulegui connect correctly for a few hours (until amuled rebuilds it...).

(0002795) sturedman (developer) 2008-05-03 12:18	I've played around a bit with it and found: - The remote gui protocol is very sensitive to dropped packets. If packets are lost, the whole connection goes out of sync and displays nothing useful anymore permanently (until you restart the remotegui). - Remote packets are affected by the upload bandwidth throttler. That's why deleting known.met helps. It breaks your upload for a while, because aMule has to rehash all shared files. And during this time, the remotegui works better because there is more UL bandwidth available. - Even with UL bandwidth = 0 (unlimited) it works sometimes, sometimes not (though better than with limit). - with lots of files it works worse than with few, because more data has to be transferred. Looks like the protocol needs some rework...

(0002806) wild_oscar (reporter) 2008-05-05 12:41	Can this be the same issue as http://www.amule.org/abugs/view.php?id=1146 [^] ?

(0002808) wild_oscar (reporter) 2008-05-08 16:20	Any chance of: 1) merging this issue with http://bugs.amule.org/view.php?id=1146 [^] 2) Prioritizing it, as it is making amulegui useless right now?