{"issue":{"user":{"id":829872,"login":"skrossner","url":"https://api.github.com/users/skrossner","avatar_url":"https://secure.gravatar.com/avatar/00c8ca79897ec8bd34465c6ffccee9a9?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"00c8ca79897ec8bd34465c6ffccee9a9"},"milestone":null,"created_at":"2011-12-15T06:06:10Z","title":"invalid asset path is repeatedly retried","labels":[],"state":"open","updated_at":"2011-12-16T02:39:20Z","id":2563439,"html_url":"https://github.com/ippa/jaws/issues/17","closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"number":17,"body":"If I call \"jaws.assets.add()\" with a string argument representing an invalid asset path, then that path is attempted to be fetched each time it is referenced in a jaws.Sprite constructor.  This leads to massive slowdown (and lots of network traffic) if there are thousands of sprites that use this invalid asset path.\r\n\r\nI would prefer an invalid asset is not attempted to be retrieved once it fails to be retrieved the first time.  Also, an exception or even a console error would be nice as soon as the asset is deemed invalid.","url":"https://api.github.com/repos/ippa/jaws/issues/17","comments":2,"assignee":null},"comment":{"user":{"id":829872,"login":"skrossner","url":"https://api.github.com/users/skrossner","avatar_url":"https://secure.gravatar.com/avatar/00c8ca79897ec8bd34465c6ffccee9a9?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"00c8ca79897ec8bd34465c6ffccee9a9"},"created_at":"2011-12-16T02:39:20Z","updated_at":"2011-12-16T02:39:20Z","id":3172547,"body":"I'd say throwing an exception that the caller would catch makes the most sense; I don't know of any use cases where execution should proceed after one or more assets fail.  I'd say throw it after all the specified assets are attempted to be fetched and have the message contain the names of each failed asset.  Or throw it after the first failed asset if that's easier to implement.\r\n\r\nIf you don't want to throw an exception then logging is fine.  Silently failing would be confusing, yes.","url":"https://api.github.com/repos/ippa/jaws/issues/comments/3172547"},"action":"created"}