Adding an asset more than once about resource-loader

[englercj]

The reason is because this library doesn't want to be a resource caching and management system, just a loader. You shouldn't use this library for anything except the actual mechanism of loading data. All caching, resource management, knowing what is loaded and what isn't, deciding what to load, etc, should all exist as logic outside of this library.

The philosophy here is that once you've decided what to load, you fill a loader with requests and trigger it. If you're adding a name 2 times, then your higher-level logic is flawed and incorrectly had a duplicate in it.

As a more concrete statement, your project should have a Resource Manager that stores resources and manages their lifetime. When it decides something needs to be loaded from a remote source, only then does it create a loader and load them. It may have many loaders going at once, or only one. Up to you. Maybe it would be worthwhile for me to build a library that does that for people, built on top of this library.

[irongaze]

@englercj it would be a good idea to make this more explicit up-front, perhaps in the main project readme. It is definitely unexpected behavior to folks coming new to the project and caused me a lot of debugging and googling to figure out what was going on.

My expectation was that if I requested loading an existing resource, the loader would simply queue it and immediately fire an onLoad once the loader starts just like a browser would with a dom node. I understand why you're not implementing that feature, but it is odd without the context you just provided.

(and thanks for this project - I really appreciate your work!)

[englercj]

I added this to the readme in the v4 typescript branch.