netenken1

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by netenken1

  1. I have same problem with you, you can try the solution above...

    create temp folder, and btsync to the temp folder , after 100% transfer done, copy temp folder content return the folder you want them to...

    but I found btsync currently not suitable to do our work, still have so much issue for us...

    I am creating our own btsync like app several month ago...

  2. BTTorrent Sync is an all-new-stype excellent transfer tool in the world, it combine both p2p and internet syncing utility, I think no one has fully thinking about how to use and help their working before...I am using Aria2 now, and it's help my work very much ,

    How about checking "Aria2" API, I think it could be a good template for somepart...

    although "Aria2" is one of P2P tools, and also providing good and completely API example , But I think if you can provide some basic functionality with first step , It's already enough for so much MIS help doing there work....

    for most import API I think as above:

    1. Add/Edit/Remove specific share folder

    2. Resync specific folder

    3. Add/Update/Remove predefine host

    4. Enabled/Disable engine, just enabled/disable not close application (maybe someone need schedule p2p transfer)

    5. Speed limit control

    6. report each shared folder transfer state

    7. all API call by XML style , for exp REST or XML-RPC, bittorrent sync build-in is better

  3. Execellent, but I found while syncing already exist file, that file also be rename to suffix with ".!sync" , would you please change or add a option that should let user change the rule ??

    While syncing a exist file, do not rename old file to ".!sync" , alternative create a new same file with suffix ".!sync" , but do not delete the old file before new file transfer finish !!

    for example:

    original "zzz.mov" is exist before, while the peer got new version of "zzz.mov" , the original "zzz.mov" still there, but the new version of zzz.mov start syncing and name as "zzz.mov.!sync"

    while do that ? becuz while new version of "zzz.mov" syncing, maybe it need 5hours , user can still access the original "zzz.mov" , before new version of "zzz.mov" done

    **** It's very important for somebody updating program or live-data ...