Push Data Problems

[lmflores]

Hi:
First of all, Mark, sorry about sending an e-mail instead of making this public. I didn´t read.

I am making an application tha must provide off-line information. The thing is that the information we are using is up to 3 Mbytes in csv format. Is the smaller we can get.
We have tried using a HttpConnection and pull the data from a webserver, but the page size is very large and i get the "Entity Request too Large" error.

We tried to do it with e-mails attachments, making a custom attachment handler, but the actual device seems to have problems downloading attachements biggers than 2 Mbytes.

The last thing we are testing is a direct socket connection. The handheld connects to a server that sends the data, but we are having problems. The server seems to send the data faster than the handheld is receiving, and when the server finishing sending the 40,000 record, the handheld is receiving the 6,000 record and it gets freeze.
Does anyone knows why this is happening?

We are not using BES and we don´t really want to.
Does anyone can suggest a way to solve this problem without using BES?

Thanks in advanced

[arconsulting]

3MB over a wireless connection is a lot of data.

If you must do it w/o a BES, you need to break your 3MB file into managable chunks. FYI, RIM recommends packets that are 2-3KB in size.

First, your device will need to query the server for a directory of files (aka chunks) and then request each of these files individually. If one fails, the device will rerequest the file until it has all of them. Not pretty.

One important note is that different carriers impose different max sizes for http requests/responses.

With BES, the work can be done on the server side.

Either way, you will consume a lot of battery life downloading a 3MB file.

Can you get the data onto the device in another way? Sync via USB and then just send updates wirelessly?