Home/ Questions/Q 6132359
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T17:05:36+00:00

I have a site that get content from other sites with some JSON and

  • 0

I have a site that get content from other sites with some JSON and XML API. To prevent loading problems and problems with limitations I do the following:

  1. PHP – Show the cached content with PHP, if any.
  2. PHP – If never cached content, show an empty error page and return 404. (The second time the page loads it will be fine “success 200”)
  3. Ajax – If a date field does not exist in the database, or current date is earlier than the stored date, load/add content from API. Add a future date to the database. (This makes the page load fast and the Ajax caches the content AFTER the page is loaded).

I use Ajax just to run the PHP-file. I get the content with PHP.

Questions

  1. Because I cache the content AFTER it was loaded the user will see the old content. Which is the best way to show the NEW content to the user. I’m thinking automatically with Javascript reload the page or message-nag. Other prefered ways?
  2. If I use very many API:s the Ajax loadtime will be long and it’s a bigger risk that some error will accur. Is there a clever way of splitting the load?

The second question is the important one.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Because I cache the content AFTER it
    was loaded the user will see the old
    content. Which is the best way to show
    the NEW content to the user. I’m
    thinking automatically with Javascript
    reload the page or message-nag. Other
    prefered ways?

    I don’t think you should reload the page via javascript, but just use Jquery’s .load(). This way new content is inserted in the DOM without reloading the entire page. Maybe you highlight the newly inserted content be adding some CSS via addClass().

    If I use very many API:s the Ajax
    loadtime will be long and it’s a
    bigger risk that some error will
    accur. Is there a clever way of
    splitting the load?

    You should not be splitting content in first place. You should try to minimize number of HTTP requests. If possible you should be doing all the API calling offline using some sort of message queue like for example beanstalkd, redis. Also cache the data inside in-memory database like for example redis. You can have a free instance of redis available thanks to http://redistogo.com. To connect to redistogo you should probably use predis

    • 0