stop writing small shares in old V1 share format #1461

Open
opened 2011-08-01 15:49:51 +00:00 by zooko · 0 comments

When we extended the immutable share format to allow large shares, we made it continue writing out the old "V1" share format when the shares were small enough to fit therein. This was for backward compatibility in case someone migrated a share file to an old pre-v1.3 storage server or downgraded their storage server to pre-v1.3. We no longer need to support those uses cases--nobody is going to do either of those two things ever again. It might simplify life for future implementors if we start writing out only V2 share format from now on.

When we extended the immutable share format to allow large shares, we made it continue writing out the old "V1" share format when the shares were small enough to fit therein. This was for backward compatibility in case someone migrated a share file to an old pre-v1.3 storage server or downgraded their storage server to pre-v1.3. We no longer need to support those uses cases--nobody is going to do either of those two things ever again. It might simplify life for future implementors if we start writing out only V2 share format from now on.
zooko added the
code-storage
minor
enhancement
1.8.2
labels 2011-08-01 15:49:51 +00:00
zooko added this to the undecided milestone 2011-08-01 15:49:51 +00:00
zancas was assigned by zooko 2011-08-01 15:49:51 +00:00
tahoe-lafs modified the milestone from undecided to 1.11.0 2012-04-01 04:54:17 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1461
No description provided.