[RFC] weave refactoring

[Johan Rydberg]

Johan Rydberg <jrydberg at gnu.org> writes:

> I also have plans to do the following;
>
>  * Create a new kind of store called RevisionStore which is used 
>    to store and retrieve revision information.  

The reason I want to do this is to abstract away how revisions are
stored.  Right now they are stored as plain files. With knits they
will (most likely) be stored in a versioned file.  For history deltas
the revision information is stored in the hdelta alongside text
deltas.  So some kind of abstraction of a "revision store" is needed.

Which brings me to how revision signatures are supposed to be stored.
Right now they are stored alongside the revisions in the revision
store.  Which means there can only be one signature per revision.

Should the signatures always to tightly coupled with the revisions?
If so, the responsibility for storing signatures can be moved to the
new RevisionStore class.  If not, the concept of signature store can
be re-introduced. 

Are there any plans on support several signatures per revision?  Is
there a need?   For knits there could be a separate signature-knit
storing multiple signatures.  

My preference is to have a separate signature store, that way the
underlying history format can store the signatures as they like, if it
supports it at all.  

Comments?  Ideas?  Robert?

~j