coolRunnings: firewalled images

[GoogleCodeExporter]

If the user is creating sprites from images behind a firewall, then the
CoolRunnings service can't access them. If we can't workaround this issue,
then at least we can look at making it a more graceful failure. 

Original issue reported on code.google.com by stevesou...@gmail.com on 1 Sep 2009 at 6:25

[GoogleCodeExporter]

I believe right now coolRunnings will fail if any of the images aren't 
accessible.
Instead, we should figure out a way to handle the error. For example, 
coolRunnings
should sprite all images possible, but return some error data that indicates the
images it couldn't sprite.

Original comment by stevesou...@gmail.com on 6 Sep 2009 at 1:26

• Changed title: coolRunnings: firewalled images

[GoogleCodeExporter]

Original comment by stevesou...@gmail.com on 22 Sep 2009 at 5:33

• Added labels: Milestone-NextRelease, Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by stevesou...@gmail.com on 22 Sep 2009 at 5:33

[GoogleCodeExporter]

Is this the Error Occured alert issue?, if so 

Original comment by klaus.ho...@gmail.com on 7 Oct 2009 at 11:49

[GoogleCodeExporter]

I can suggest the following workaround:
1) coolRunnings detects that image can be accessible. So it should return any 
message: 'please upload the image to public resource' or something similar
2) SpriteMe uploads required (it seems all the) images to a public resourse 
(Flickr? 
Facebook? Google Docs?) and replaces URLs with the public ones (returned on 
upload).
3) coolRunnings receives URLs to images which are public acessible.

Does this make sense?

Possible issues: 
a) maybe such images should be make private,
b) and SpriteMe must replace URLs back if images have been converted to sprites.

Original comment by sunny.dr...@gmail.com on 16 Oct 2009 at 11:31

[GoogleCodeExporter]

added to CoolRunnings GCode

http://code.google.com/p/coolrunnings/issues/detail?id=1

Original comment by jaredhir...@yahoo.com on 7 Dec 2009 at 7:07