Using the Vimeo API & caching responses

Our site uses the Vimeo PHP library (https://github.com/vimeo/vimeo.php).

Currently I'm calling the library within snippets, e.g.:



But this means way more calls to the API than necessary ... right?

Vimeo recommends caching the response, but I'm not sure how to do that in modx.

I'm guessing the first 3 lines only need to be run once, then cached ... until we make changes to our Vimeo account (add videos, albums, etc.)

What's the best way to accomplish this?

The only part that changes from snippet to snippet is the `$vimeo->request...` portion ... is there a way to only have that at the start of our snippets?

Unless the requests are all made on the same web page, you do need the first two lines. If they are all on the same page, you could put the first two lines in a separate snippet at the top or in the template, unless the request line is repeated in a loop, then you can just put the first two lines outside the loop.

For caching the response, I think you'd have to create your own cache and write the content of $videos to it (maybe with serialize()). Then for each request, you'd have to check the cache and read (and unserialize()) the data if there's a cache hit, and make the request if not. You can't call the snippet cached because you'd get the wrong videos on many pages.

Thanks for that ... I think I understand ...

The caching is simpler than I thought! [ed. note: danzg last edited this post 6 years, 10 months ago.]

I'm glad I could help.

On second thought, serialize() is not a good choice if you're storing photos or video. It would probably be better to just read and write them as binary data.

You might also take a look at StatCache, though it has some limitations and might not work for your use case. [ed. note: BobRay last edited this post 6 years, 10 months ago.]