for each FileMaker record, I store multiple images, and issue them serial numbers from "image" records in a related table

I then built a calculated HTML page ( data URL ) to display all the images together, using RawData, width & height. It does work

however, is this efficient?

since I can't reference the "thumbnail" folder directly, does the server have to generate a thumbnail to size for each RawData call?

even if they are cached, does it generate the first time thru?

it seems this could tax the server, if I had a bunch of mega Mb images

thanks!

greg

Why are you using the RawData URL for this? When you use the RawData URL the SuperContainer server sends you the original image, not a thumbnail/preview image. You're getting the full-size file each time.

SuperContainer caches preview images, so if you generate a preview using the Files URL then it won't have to generate it again when you view the same preview image.

My recommendation is to use the regular Files URL, not RawData, and let SuperContainer server automatically generate preview images for you. It will also automatically size them to fit in your web viewer, so you won't need to use the width and height parameters.

if you use "Files", then it returns an entire web page, not just the image. I need just the image

and "RawData" will return a thumbnail, if you specify width and height

just wonder why the thumbnails folder is not hosted as well

greg

>Why are you using the RawData URL for this? When you use the RawData URL the SuperContainer server sends you the original image, not a thumbnail/preview image. You're getting the full-size file each time.

SuperContainer caches preview images, so if you generate a preview using the Files URL then it won't have to generate it again when you view the same preview image.

My recommendation is to use the regular Files URL, not RawData, and let SuperContainer server automatically generate preview images for you. It will also automatically size them to fit in your web viewer, so you won't need to use the width and height parameters.

The thumbnail IS what you're getting when you get the resized image. That's what the thumbnail is. It's a resized version of your original image. The thumbnails direcotry is where SuperConainer caches the preview images and is "accessed" by specifying a width and a height in your URL. SuperContainer is accessing the thumbnails directory any time you request an image of a different size than the original.

so, I just need to consistently specify width & height in all my URL's, and it will re-use that thumbnail

and if I "request an image of a different size than the original" and different than the last thumbnail, it will make another

Please add this explanation to your documentation!

thanks,

greg

>The thumbnail IS what you're getting when you get the resized image. That's what the thumbnail is. It's a resized version of your original image. The thumbnails direcotry is where SuperConainer caches the preview images and is "accessed" by specifying a width and a height in your URL. SuperContainer is accessing the thumbnails directory any time you request an image of a different size than the original

You never need to worry about which image SuperContainer Server is accessing. Just specify the size you want and the server will handle retrieving or generating the image. You don't need to write your calculations specifically so that it generates or does not generate a new preview image, and it's not something you have control over. It will handle it on its own.