Determine Storage Scheme

[CBDotGuru]

As specified here https://github.com/ethpm/ethpm-spec/issues/75 we need to determine how to store packages such that the list can be enumerated and packages can be retrieved by name/uri.

Consideration should be given to either use functionality provided at https://github.com/ethpm/ethereum-indexed-enumerable-set-lib or https://github.com/Majoolr/ethereum-libraries/tree/master/LinkedListLib .

We should discuss the pros and cons of each implementation as well as determine if list order matters. Discussion should be had at https://github.com/ethpm/ethpm-spec/issues/75 .

[pipermerriam]

Consider the following requirements from the side of a development framework consuming from a package index.

• Way to pull all package names.
• Way to pull all versions for a given package name.
• Way to pull the URI for the release for a given package name + version.

Bonus points if it's easy for a client to cache the last seen release and to be able to use that information to only pull data on new releases.

Data structure:

• package name: string
• release: (version + URI)
  • version: string
  • URI: string

Some uniqueness constraints:

• package names should be unique.
• (package name + version) should be unique
• URIs do not need to be unique.

Useful but not necessary metadata:

• timestamp of when a release was published.

[CBDotGuru]

cc @paulohp