Have you done any measurements that tell you where the server-side time
is going?
If it's database access - and you're satisfied that your schema design
is optimal - then solutions to that problem include some variations on
the following.
a. A caching mechanism that would update the cache at a rate you
select, rather than at the rate of visits.
b. Create a static page that often, and respond to users with that
static page.
Client-side, if memory is being consumed and not returned, then forcing
a page reload can clear that issue.
AS
On 5/21/2011 3:01 AM, Kris Geusebroek wrote:
Hi all,
A timer event would certainly work. Although i found that with Internet
Explorer the memory consumption is huge. Every update will create new
dom elements and the removal of dom elements is not freeing the memory
out of the box.
So whatever solution you choose you should take that in mind
Cheers Kris
_______________________________________________
Users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/openlayers-users
