[Adium-devl] Empty Directory File Transfers

[Graham Booker]

On Aug 22, 2007, at 2:27 PM, Evan Schoenberg wrote:

>
>
> That sounds like fine behavior to me - I can't envision any use case
> for sending an empty folder.  Beware the .DS_Store files (which
> shouldn't count as making the folder non-empty) when checking folder
> contents for emptiness.
>

There really isn't anything in the AIM protocol to allow sending of  
empty folders.  There is no concept of a folder in the protocol, they  
are just byproducts of the locations for files.  So a dialog sounds  
like the best option (although I say it should only be done if the  
original folder to be sent in the empty one, not with subfolders).

> We should probably check against 0-byte files, too -- I believe I
> recall this currently throwing a libpurple error ("This file can not
> be sent because it is 0 bytes" or something like that) and then
> leaving the poor file transfer stranded in 'initiating' per the File
> Transfer Progress window.
>

This needs to be fixed; I guess it is yet another case where Fire's  
file transfer worked better than libpurple.  There is a very simply  
way to send a 0 byte file, and it is perfectly legal.  You do  
everything in exactly the same way you would send a normal file,  
except you just don't send any payload for the file.  The end result  
is the file (along its containing directory, of course) is created  
with no data.

> Cheers,
> Evan


- Graham


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1603 bytes
Desc: not available
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070823/f134efd8/attachment.p7s>