Yesterday, while working on a simple and short flash lite project to create a rss feed scroller for flash lite 2.0/2.1 enabled phones, i noticed a very obvious thing. For most of the urls that i tested, many of the feedburner ones seemed to have no output. when going for a closer observation it looked like most of the phones were facing memory errors.  

Its pretty obvious because even if you may need a very small piece of information for the rss feed, you still have to load the entire rss into memory for parsing. Most phones which are not in the smart phone category wont support such a luxury. Hence the best solution to this would be to pre prepare the data at a server then have your phone consume it.

Meaning that you need to have something like a ordinary http server in between, which will pull in the rss feed and slice out only what is needed by your application. Then create a custom xml with the sliced data and feed it to the phone.

Not only will you be lowering the data load time but also be sure that your application will run smooth on all ranges of phone without causing memory problems.

I  recommend using swx-php based remoting for flash lite 2.0/2.1. Hopefully i will try to make a session out of this , on “how to integrate your flash lite application with the back end for better efficiency”, using php as a back end primer.