Skip to content
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

Major back-end rework #1191

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Major back-end rework #1191

wants to merge 2 commits into from

Conversation

KevinMackenzie
Copy link
Contributor

Currently targeting master with these changes, but that may change.

}

// ContentHeader is the authoratative source for which seqeuence of ContentChunk's is current
type ContentHeader struct {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A thought here: If we kept multiple of these objects in the DB, then we can create a coarse history of the circuit. Not hard to add later on (not a breaking change), but I have to think more if this is sufficient for storing "milestone circuits".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thought about this some more. We still have only one ContentHeader pointing to the "current" version. Some kind of timestamp needs to be added to the first ContentChunk entry of a given ContentID to establish a timeline once ContentHeader no longer points to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants