I wrote a wrapper backend that create Par2 files and write them to the wrapped backend. Just add a leading 'par2+' to your url_string to use this (e.g. 'par2+webdavs://USER@HOST/PATH')
pros:
- easier to maintain than build-in par2 functions
cons:
- incorrect size calculation as par2 files are not included in size
- no async creation of par2 files
I wrote a wrapper backend that create Par2 files and write them to the wrapped backend. Just add a leading 'par2+' to your url_string to use this (e.g. 'par2+webdavs: //USER@ HOST/PATH' )
pros:
- easier to maintain than build-in par2 functions
cons:
- incorrect size calculation as par2 files are not included in size
- no async creation of par2 files