nperrier/sockso — comment on commit 94e43113f38dad3bc99e9e5515d8d3bdd645b858
File:  line 0
By rodnaph:

It's ok I wouldn't worry too much about how it's all factored, the most important thing is that it works! How it could be structured though it seems to me is something like, having a CoverArt class that represents a cover image...

```java
class CoverArt {
public Image scale() { .. }
// etc...
}
```

This has methods for dealing with the actual image, and scaling sizing, whatever. Then there could be a something like a CoverArtCache class that handles reading/writing these images to the cache...

```java
class CoverArtCache {
public boolean isCached() { ... }
public CoverArt read() { ... }
// etc...
}
```
Also, the indexing bit could be done by it's own class, then used as a dependency in DBCollectionManager.

```java
class CoverArtIndexer {
public void indexCover( CoverArt image ) { ... }
// etc...
}
```

But that's only my rough suggestion, probably without a proper understanding of all the problems. So like I said don't stress over the refactoring, if it works then that's good - lets bosh it in.

Tests are more important though, so if you could add some of those I'll merge this in then.

Cheers for all the work! :)