objective c - iPhone network performance -

I have a question and I'm open to suggestions (very strange!)

I'm writing an iPhone app, which requests a server (URL of the parameter) as a response, the iPhone XML receives all right.

Right now, I am looking to improve the speed of my actions which takes time to do some work. I have found that, in all the tasks downloaded, XML parsing, sending requests, pushing the request, parsing objects from XML), it takes the longest time to download the actual XML.

Now, my XML files are very, very, very simple and very, very, very small. I mainly read them like RSS and read them in UTIB.

My app works very well, and there is nothing that really feels slow, but there is an application in the app store that does something similar to my application, but The way it is faster and feels more 'fast', if you know what I mean. It also has a great facility to load headlines from RSS feeds one by one.

Currently I am experimenting with the compression of my data, but compression only makes half the size of my data and it does not do any real good work for display. The main thing is that the data should be downloaded, before it is parsed. It will be very quiet for the 'stream' of the data, which it comes in. In this way, I can do two jobs almost simultaneously and headlines one by one (makes user interactivity more attractive).

Does anyone have an idea of ​​improving my performance? Either way to communicate with great compression tips or servers in a completely different way .. All are welcome!

Update: To put server's latency and accountability aside; How do I get a source of XML to 'stream' my iPhone (download byte for byte) and parsed at the same time? There is a linear process to download now -> parsing -> is showing, but downloading it can be semi-parallel & amp; Parsing at the same time (and when each item is downloaded, show it instead of loading it at Uitable Weave at the same time)

Assume that you are using NSXMLParser's initWithContentsOfURL, this is probably part of the problem, it seems that downloads the entire contents of the URL, then parsing it at once Removes the parser for.

Despite the fact that NSXLLP is an event driven parser, it is unlikely that to support Parsar streaming data in an incremental way, you can definitely replace the NSXLL Parser with some other Parsing Library. , Which handles incremental data in a more sensible way.

One option would be to use NSURLConnection, and to create a new NSXMLParser and re-parsing each data, some data comes in time, in connection: didReiveiveData: the method of representing your NSURLConnection

It seems that this may be more than just grabbing some other libraries, it seems that you have to write some additional code to ignore additional action.

and optimize it, but depending on how you are controlling the downstream creation of your table data