bzz-feed-rawto avoid it when looking up
time = 0and then incrementing, and in order to know the last epoch, the client could still fetch the feed metadata, if I understand it correctly?
time = 0, at this point there’s no way to know if the writer has written to the first chunk (
time = 0) or if it’s just the default value. One way would be to set the
nullto differentiate from
0but that would add a bunch of null-checks in the other pieces of logic, or start the iteration from
0, so we can treat a feed ID with
time = 0as having never been written to, what do you think please?
time = 0, should it expect the chunk at that
timeto have been written or not?
timeafter pushing, so if it hasn't written it's
getID()returns is actually the ID of the next write, but the name does not reflect that
getID()returns the ID of the latest write, but with the assumtion that if
time = 0there has been no write.
time = 0for the first chunk, yes the problem is how shall we translate the fact there has been no chunk written? We could set
time = nullbut then that breaks the current interface and it would require additional logic in the code. Otherwise it could be
time = -1but I don’t think it’s valid with Swarm, so if the app just tries to make a request using the provided ID, I don’t think it would work as expected.
1please? I think that simplifies the protocol/logic a lot.
bzz-related packages, and a new package to synchronize JSON documents from various sources: https://github.com/MainframeHQ/erebos/releases/tag/v0.13.0