makeImageRequest => caching?

Hi all,

I have a question regarding "makeImageRequest": how exactly is the caching done? I have an application which in some cases needs to update an icon every few seconds to assure a changed status is visualized. On the simulator this works fine, I guess because there no proxy is used. On the device however it does not work in a consistent way. The icon seems to update in one call but in the next one it suddenly falls back to the previous icon again. My assumption is that the proxy does some caching but I need a confirmation. Also, is there a way to disable the caching entirely? The webserver is sending a "no-cache"-header already, but this does not seem to make any difference.

Any suggestions?

Thanks!

Top Replies

Talkabout over 3 years ago in reply to waterkip +2

Sorry, was not aware that you are interested

The problem was that for a particular device type I was changing the status immediately after sending the command, but the next status request to the API was…

All Replies

Talkabout over 3 years ago in reply to _psx_

I am trying to do some more tests, thanks for your support so far!

_psx_ over 3 years ago in reply to Talkabout

I do 4 request on background and can see

1. About 5 second lag for first

2. Next 3 last about next 6s

so usually is takes about 10s but it's a rather 4 small jsons. But from time to time 30s is not enough to make 4 and I can see only 3 or 2 and have to wait next 5 minutes to do them.

_psx_ over 3 years ago in reply to Talkabout

And maybe better solution is asking for all device at once or only for those which user can see on screen.

And everywhere write info read at ... .. ago, and allow user to update data manually when he wants to see current status

_psx_ over 3 years ago in reply to Talkabout

And for me more useful information is not status but warning status GARAGE DOORS ARE OPEN.

So everyone should can define good, warning and critical state for status and get info when something is wrong.

Talkabout over 3 years ago

Hi guys,

I figured out that there was one more problem on application side, currently the image requests seem to work fine, thanks again!

Bye

waterkip over 3 years ago in reply to Talkabout

What was wrong? You can't leave us hanging

Talkabout over 3 years ago in reply to waterkip

Sorry, was not aware that you are interested

The problem was that for a particular device type I was changing the status immediately after sending the command, but the next status request to the API was still delivering the old status. That cause the icon to change back to the "old" one and I was assuming that has something to do with the "makeImageRequest"-method, which was not the case.

Bye