feat: blob capability implementation #1340
Conversation
| Blob.allocate | ||
| .invoke({ | ||
| issuer: id, | ||
| audience: id, | ||
| with: id.toDIDKey(), | ||
| nb: { | ||
| content, | ||
| size, | ||
| }, | ||
| expiration: Infinity, | ||
| }) | ||
| .delegate(), |
There was a problem hiding this comment.
I was thinking this one could be actual invocation that we run from here, I do not believe we need to schedule it for later. In my mind it would basically do what we have here
Than we would do what you do here. Followed by logic that checks if we already have blob, if so we could also issue receipt for accept. If we do not have it yet then do exactly what you do here.
There was a problem hiding this comment.
I'm not sure if we have a good way to check if we already have a receipt for this task or not, but assuming we can do that I imagine we'd have a big if clause around all these so if we do have a receipt we just check if blob was received and if so issue receipt for the accept if we do not have receipt yet it's a first run so we do what was described prior
There was a problem hiding this comment.
I just noticed this and also created #1342 with this branch with more iterations. I ported these comments over on #1342 (review)
|
Oh I just now noticed this. I also created PR #1342 with more iterations. Thanks for the feedback, I will port there |
Just creating this PR so we could discuss implementation details for #1339