09 July 2002 Status report -------------------------- Scott:
>1. If I start a file-transfer and don't give permission > immediately, then an error message comes up on the sender > asking if I want to "continue wait?". After I get that, > if I confirm the file transfer at the receiver, the > transfer doesn't begin. If I go back to the sender and > answer "yes" to waiting, I get a socket error. The > receiver shows no file transfer in the status window, > and the sender gets stuck at 20480 in its file transfer > window. Now, the sender does not get stuck but the whole procedure still needs more clarity. >2. Canceling a file transfer doesn't work for either side, > sender or receiver. Fixed >3. Similar to the VNC PropTab in each one of the devices, > there should be a File Transfer PropTab in each one of > the devices running Kaboodle. If it's MyPC (ie, the one > I'm working on), it should show what's in the "Receive > File" tab of the File Transfer service icon. If it's > another Kaboodle PC on the LAN, it should have the > "Send File..." information in its PropTab, with the > MachineName of this Kaboodle PC coming up by default in > the dropdown field. So, what you suggest is to dissolve the existing File Transfer panel in the devices panels. That is doable. But I think, MachineName dropdown list will be no longer needed. >4. If there are no other Kaboodle PC's on the LAN, and if > Kaboodle is not VPN'd, then the file-transfer dropdown > box should not be empty. It can instead give an error > message: "Sorry...Kaboodle can only transfer files to > other PC's that are also running Kaboodle". This issue will be not actual if we turn down the MachineName box at all. (Your thoughts?) >5. Have a look here: > http://perso.wanadoo.fr/samfd/esvnc > > This guy has added file-transfer into the VNC code directly. Thank you. I have had a look. They do not use threads for file transfer at all. There is a cycle like Read-a-File-Batch / Send-the-Batch The only difference from what I do is they use system memory allocation instead of new-style allocation. --------------------------------------------------- What more is done (in cvs): 1. >> ... Known bug: when Status tab is open and a file comes, >> it's name and size are not displayed. Fixed 2. >>I continue to improve read/send threads. I have implemented two additional threads: one explicit for sending a batch, and the other one implicit - overlapped file reading. Unfortunately, it did not substantially speed up. The test file KaboodleSpec_1.8.doc (222 208 bytes) is transferred within 12 seconds. The thing is that reading a batch to the file buffer occurs in no time at all as compared with sending. So the file thread never always waits for the sender thread. Note that encryption still occurs in the sender thread, so the way out could be to move the encryption code to the read thread. Will try latter on. 3. Now, if "Do not ask" option is set at the receiver side and a file comes that should overwrite, the prompt box pops up at the sender side rather than receiver. (As you once suggested) -Oleg ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
