Curious delay after move from v2.8 to 3.3

[SteveCole]

I've been developing under the 2.8 API and my app has loaded immediately but, under the 3.3 API, it's exhibiting a weird lag time.

One of my featureLayers is constructed on the fly using a FeatureCollection. Using some well placed console.log commands, I can see that the code is, in fact, running immediately (including processing the deferred results which are used to construct the featureCollection).

The problem is that those features are NOT visible or clickable for another 4 minutes! After that 4 minutes, the features suddenly appear and everything is fine. There's no error to speak of in the console and, again, it runs fine in v2.8

We're using ArcGIS Server 10.1. This app is currently running on an internal, developmental server but I'm hoping to push a public version soon (I have some other issues I need help with).

Has anyone else experienced weirdness like this with the 3.3 API?

Steve

[SteveCole]

Ok, for comparison, here's a version of our app using v2.8 of the API:

http://gismaps.snoco.org/fws28/

This loads quickly and my data (the square symbology) shows up immediately. It's the same code base with respect to the page's 5 minute refresh and the dojo charting, just modifed as required to get running under v3.3.

[SteveCole]

I can't explain WHY this happens but Jeff's question about window.setInterval() to refresh my page every 5 minutes appears to be on the money. What I ended up doing was calling my update function immediately before specifying the window.setInterval() command and now the features display immediately like they did under v2.8 of the API.

One frustrating gremlin down, several more to go. Thanks again to everyone and especially Jeff!


Cheers-
Steve

[JeffPace]

Happy to help. Glad you found a work around!