[Flash Lite 3 for WM] What is the limitation?

[ltyt]

Hi all

I'm a beginner with Flash Lite and I intend to create a Flash Lite 3 application for running on browser of Window Mobile smart phone.
Up to now, as I know the Internet Explore mobile in WM6.1 supported the Flash Lite.

But there are something I could not find anywhere.
+ What the limit file size of swf file in Flash Lite 3
+ Is there any memory usage limitation or it depends on device memory?
+ Is there any limitation in data transfer between flash app and server (http or https)
+ Does Flash Lite 3 support Multi thread?
If not so is there anyway to simulate the multi thread in Flash Lite?

I need some below function in my application
- Asynchronous update content
- While app sending request or receiving reponse to/from server (http, https), if user do some action (select other function or scroll..), current request/response will be stopped.
I think these function need to be implemented by multi thread.

I really need help on these problem, please help to let me know your opinion.
Sorry for my bad in English.

Thanks in advance.

[hp3]

I have not seen any information about memory issues for the IE activeX control in wm6.1. This information would probably need to come directly from Microsoft because MS licensed FL for use in the browser. Adobe did not create this activeX control.

flash does not work as a multi-threaded platform, or at least the developer has no way to develop multi-threaded applications using Flash.

--------
While app sending request or receiving reponse to/from server (http, https), if user do some action (select other function or scroll..), current request/response will be stopped.
--------
Just to clarify, are you saying that if you embed a SWF in IE for wm6.1, start a http connection, then scroll in the web browser, that Flash Lite terminates the HTTP request? If this is true then it should not happen and could be a bug. Scrolling in the web browser should not interfere with Flash behavior.

However if the user gives focus to another application other than the web browser it is possible that MS designed the activeX control to stop activity to conserve CPU resources.

[ltyt]

Thanks for your reply
--------
While app sending request or receiving reponse to/from server (http, https), if user do some action (select other function or scroll..), current request/response will be stopped.
--------
About above case, I would like to explain it more clearly.
I intend to creat an app which display an image. That image is big, and user can only view one part of it at one moment.
[Scroll] mean that user can scroll that image up, down, left, right to view other part of image.
But the image is a low quality image (it is used as background) , after user move to new position, app will send request to server to get the High Quality image of selected part and display -> that why there is http request.

While the request/response is processing, user navigate in menu and execute other function or similar scroll to other position -> current [request/response processing] will be stopped immediately and application will execute selected function.
It is similar to the Google map.

Do you think that there is a way to implement it without multi thread?

Thanks for you reply.

[hp3]

you dont need multi thread to do this.

The issue is terminating the download of the high quality image, before starting a new request to control memory usage. It is worth mentioning that browsers also can allow multiple simultaneous HTTP requests and the IE activeX control architecture supports this as well. Most desktop PC browsers allow 4 or more simultaneous requests, not sure about mobile browsers, but may not matter too much in your case.

When you load an image into Flash Lite you will create a movie clip to act as a container for the image. To terminate the currently loading image, your best approach will probably be to load a very small file size image into the same movie clip. This "unloads" the high quality image.

Flash Lite has an automated memory management which runs periodically. You cannot force it to free memory. It will only free memory periodically. Terminating the download marks the partially loaded image for removal from memory, but will not actually be removed from memory until the memory management system runs.

So, you may need to do some experimentation and set up a way to monitor memory usage to make sure your app does not exceed any built in memory limits if the user requests high quality images in rapid succession.

[ltyt]

Thanks for your quick reply

I understood your approach and I will take a try.

Again, thanks for your advice.