-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Piece IO #2
Piece IO #2
Conversation
Define API and interfaces for pieceIO component
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ergastic this looks good generally. I think we should remove the WritePayload function from the Interface & implementation cause it doesn't appear to do anything GeneratePieceCommitment doesn't, and the current implementation doesn't do that.
Keep working on this if you want till you go on storage miner and then we'll just pick it up.
tempDir filestore.Path | ||
} | ||
|
||
func NewPieceIO(padReader PadReader, carIO CarIO, sectorCalculator SectorCalculator, tempDir filestore.Path) PieceIO { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder -- should PieceIO just have access to a Filestore directly and be called a PieceStore? And then we don't have to worry about getting things in and out of the filestore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that case I'd like add a function to create a temporary file through the filestore.
What
filecoin-ffi
Pending
Better unit test coverage