Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Make the management of segmented objects portable (i.e., interoperable) #25
Currently, the application relies on its specific way of segmented and stroring large objects.
We use the object name to determine whether or not some segments exist (furthermore, we assume that the segments are located in a different container whose name is formed by the concatenation of the name of the container in which the object is located and the string "_segments").
This approach is not portable. The list of segments should be retrieved using the manifest object.
We are waiting for this pull request to be processed: Added access to the manifest of StoredObjects.
(In the eventuality the changes are not merged into the library, we will try to find alternatives).
Basically, all functions that manipulates objects are likely to be flawed when dealing with segmented objects that were not uploaded using Swift Explorer.
Problem when removing large objects (that were uploaded using another application)
If the user deletes a large object that was stored following a different convention, chances are that only the manifest object will be deleted and the segments objects will remain and waste space (the post Understanding the Size of Containers should give some insights about this problem).
Problem when comparing large objects (that were uploaded using another application)
This issue is discussed in the post On Comparing Local and Remote Files With Swift Explorer.
Problem when renaming and moving large objects (that were uploaded using another application)
This function remains to be implemented (precisely because of this issue, and also because some lack of time...). The problem becomes obvious in the post Towards Renaming and Moving Objects in Swift Explorer.