Dynamic Content - Keep loaded divs in memory - so no reload

[photo2005]

[Batalf]

[mbz]

Batalf,

The dynamic content I am displaying via this script are .PHP pages (where information is pulled from a MySQL Database) ...

Will this update have any performance increase in this instance (since the pages are essentially dynamic and not static)??

Or, will it simply still have to reload the page every time because of the nature of PHP/MySQL?

Thanks,
MIKE

[Batalf]

[photo2005]

Hey Alf,

Good stuff. It seems to be working on my end too. There is still a bit of a lag compared to the other script's cache feature, but its quicker than nothing at all.

[mbz]

Batalf,

Is there any way to actually transparently load / cache several pages (before their links are actually clicked by the user), so if they will load in the backend (and not show) but allow for faster display when the user does click on the link?

Would simply loading each of the pages into a div with css set to display:none work for this? (even though the same page when clicked would be loaded into a different div that will be displayed) Or, is there a better way??

Thanks,
MIKE

[mbz]

[Batalf]

Hi Mike,

Yes, preloading the content into a div with display:none is a very good idea.

I will add this to my script as soon as possible.

[mbz]

Batalf,

Will my example actually work, as it sends each of the requests in rapid succession (from the loop, and doesn't wait for each previous request to complete) ... Do you know what I mean?

MIKE

[Batalf]

Yes, I think I know what you mean. You are thinking of the problem that could occure if you start a second ajax process before the first one is finished.

That's actually something I thought about before creating the script

To solve this problem, I create a unique sack() object for each request to the server. So, each and every request live their separate life and know nothing about the other requests.

[mbz]