How reading URL from IP Webcam differs on Max 6 and 7

Hi,

I’m running into differences in how jit.qt.movie works, using with one and the same patch in both Max 6 and 7.
The short version of the question is: when using “read URL” to open an image from an online source, does jit.qt.movie do any kind of caching in Max 6 that it doesn’t do in Max 7?

The longer version of the question is that I’m trying to get a Max patch to stream video from an Android mobile phone using the IP Webcam app (https://play.google.com/store/apps/details?id=com.webcam.ipcam).

The stream is accessible in a browser using something like this:
http://10.0.1.3:8888/
(the IP address of the phone + port number 8888).
The page that loads uses jquery, flowplayer and droideye.js to display the stream.
It actually gets and refreshes a series of images in a format like this;
http://10.0.1.3:8888/stream/live.jpg?id=26
The id seems to be player (browser) specific. Opening the same stream on a second machine, the current frame has a different id number.

In Max 7, I can get the current frame by simply repeatedly sending
“read http://10.0.1.3:8888/stream/live.jpg” to jit.qt.movie.

In Max 6, this doesn’t work. I need to use the format with the id argument, where I need to “invent” some id number that is at least equal to or bigger than the last number used before. If I use a smaller number, say “12”, I actually get the 12th frame that this particular Max install on this particular machine has ever received from this app. And this can be from several days ago. In other words, there seems to be a persistent cache that I can access.

Any ideas on why this is and how to build the simplest possible patch to access the current image on both Max 6 and 7, would be greatly appreciated.

The Max 7 patch runs at ~15% cpu, where as the added complexity on Max 6 makes it run at a bizarre 96+%!

So what I would prefer, is something like the Max 7 behaviour described above, but under 6.

Thank you in advance for any ideas or suggestions on how to solve this.