maverck
03-28-2015, 07:05 PM
Hi Vincent,
One more time thanks for the answer.
Is there any chance that there will be any documentation of hubic 'addons' to openstack swift or rather the way hubic use the api?
As far as I discovered indeed segments are stored in default_segments in path looks like:
default_segments/UUID/timestamp/some_number/part_number
1) UUID is version 4 which means it's random. (hope I get it right)
2) Timestamp is normal UNIX format (http://www.unixtimestamp.com/)
3) Some number is magic (no ideas here). Only know it's 8 digit. Looks random.
4) Part number is 8 digit
And there is special Content-type: hubic/uploading.
It makes all the hubic apps ignore that file until Content-type is removed after upload.
This makes hubic use content-type based on file extension.
I also do the research about app I using to backup NAS, and it looks like code is in python and very easy to decompile and change.
Maybe that's the way to do it hubic-compatible
One more time thanks for the answer.
Is there any chance that there will be any documentation of hubic 'addons' to openstack swift or rather the way hubic use the api?
As far as I discovered indeed segments are stored in default_segments in path looks like:
default_segments/UUID/timestamp/some_number/part_number
1) UUID is version 4 which means it's random. (hope I get it right)
2) Timestamp is normal UNIX format (http://www.unixtimestamp.com/)
3) Some number is magic (no ideas here). Only know it's 8 digit. Looks random.
4) Part number is 8 digit
And there is special Content-type: hubic/uploading.
It makes all the hubic apps ignore that file until Content-type is removed after upload.
This makes hubic use content-type based on file extension.
I also do the research about app I using to backup NAS, and it looks like code is in python and very easy to decompile and change.
Maybe that's the way to do it hubic-compatible