Toecutter

Member
  • Content count

    4
  • Joined

  • Last visited

Posts posted by Toecutter


  1. It's just a matter of agreement how programs should treat a file attributes. But in fact you miss the point. I had been talking about getting this data from uploader's side, so downloader can sort file-list by date or use some kind of date/time analysis, e.g. for downloading newest files in share.

    For example someone have a folder with 1000 files you like, from which you downloaded all. Next time you go to the same folder and see 1200 files. Assuming that previous files you had deleted or they are not in your share now, how can you know which files you need? If there is a date of creation you can just sort by it and see if there are files created approximately after last visit and download them. At present for such task you need to keep/memorize previous files - which is really inconvenient.

    Or simply add an additional protocol command, that'll provide file-lists list ^__^

    To go even further client can have support for several metadata sending commands for date/time, file comments, ratings, MP3-tags, attributes or whatever. ^____^'

    I just had another thought on this in light of what you say above.

    If there was a facility to keep the users filelist (like say class them as a 'seed' user), all you would neet to do is download the latest filelist and carry out a compare between the two. This would produce an exception list for you.

    You could then select from the exception list and this would then be kept as the seed users list for the next compare.

    another 2p worth


  2. This is my "most needed feature" for the time being. It'll be very useful to have possibility of sorting files/dirs in filelists by date and time of creation and will help to create autonomous bot of new releases.

    PS: Since all filelists are in XML, I don't think that it'll affect clients compatibility.

    Hmmm...

    Did the thread go off topic?

    The original question related to the creation date of a file.

    This is part of the files meta data but will not neccesarily carry over with the file.

    i.e. If I download a file from anothjer user I'm not guaranteed to show the same date of creation as part of the files meta data (look yourselves at the properties of files you have downloaded).

    Therefore, a bot would not be able to read an original creation date.

    Or have I missed the point?

    My 2p

    Toecutter