On 10/17/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote: > Everything in the UI uses the database. > A full scan from disk to database take *FAR* too long. > > This was setup as a tiered effort. > First step. get the real, valid, useful content off of disk and into the > database into a usable form. > Second step. expand the data in the database fully.
It's exactly because it seems to be "tiered" that I was questioning the class hierarachy that has ArchivaArtifactConsumer and RepositoryContentConsumer as siblings. The new names make more sense, though this seems entirely internal to Archiva and not such a big deal to change later. Who else would be using these classes? -- Wendy
