Hi,
We have had similar issues loading images this way - we cannot
stream from our image server program so Flash loads the same image into
2 movie clips swapping them whilst the server saves to the same image.
To solve some difficulties with refreshing, so we used a
cache-killer method, e.g. var url:String =
"http://imageserver/image.jpg?"; + new Date().getTime();
We also had some problems loading one image when the first one had
finished, so I used setTimeout inside the onLoadInit handler to delay
calling of loading the next image.
Our server also caused problems - apache could not read the image
when the server was writing it, so the programmer wrote to a 2nd image,
then renamed it to our desirable one, but this might not affect you.
Hope some of these tricks may help.
Glen
On 11/10/2011 23:42, [p e r c e p t i c o n] wrote:
Hi All,
I'm working on a project in which I continuously grab images from a server
(don't ask..) using MovieClipLoader.
everything works fine for a period of days then suddenly the player crashes
with the dreadful "..script to run slowly..." dialog.
when I check my servers logs, i notice that the server at some point earlier
than the crash, started to send 304 (http status - means the document hasn't
been modified) as opposed to status code 200 (ok - document was found..)
has anyone else encountered this? and if so, what headers might the flash
player be sending to trigger this?
anyone with in-depth knowledge of the headers flash sends?
Thx,
percy
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
![http://imageserver/image.jpg?"](http://imageserver/image.jpg?"){kind=link}