[KenCochrane]

> I'm supporting images that end in .jpg, .png, or .gif. So currently I know that anything after the extension is parameters.

How do you know that is the extension and not a directory with a .jpg in the name? It is too complicated to convert to your URL scheme.

For me the URL based solution isn't quicker to type since I have to think too much. Also, how often is this going to be typed by hand verse scripted anyway? It will be easier to script if the URL is the same and only the GET Params change.

I prefer the get parameters, it is more obvious.

Another option that isn't as clean, but I have seen before is to Base64 encode the image URL. You wouldn't be able to easily type but you could keep your URL scheme, and still possible to script.

[nkkollaw]

It looks like most people like the GET parameters approach, so I guess it makes sense to just opt for that.

I seem to be alone in caring if it looks good or not (rightfully).