04-18-2013 09:18 PM
04-19-2013 08:32 AM
I should mention that browser channel push is a very specific type of push that is only supported by BES (not BIS).
And, it does not involve sending HTML content but rather a content URL.
Are you in fact attempting to push using BES (an enterprise server)?
If you're using BIS (you registered for an eval account and you are pushing to the general public), there is an 8 KB push limit. You would want to use a poke-and-pull strategy.
You poke the app using your push and pass it the URL it should then go and download content from.
04-19-2013 09:12 AM
Thanks. Yes, push is through the BES server. HTML is sent as part of the push so that the content is cached on the device and it loads faster in the browser; also available if there is no network.
It works fine as long as HTML file size is less than 1MB. I am using HttpWbRequest setting all headers and file content using StreamWriter.
04-19-2013 09:49 AM
You might be able to increase this limit as suggested here in your BES:
But, as mentioned, push is not meant to push large amounts of data.
That's what the poke-and-pull pattern is generally for.
04-19-2013 03:40 PM
Thank you. Can you please provide some link about how poke-and-pull works? Also, what device model/OS it is supported on?
Thanks for your help!
04-23-2013 04:11 PM
I can't seem to locate a good reference for you about how poke-and-pull works but think of it in these steps:
1. You send a push to your application running on your device with a URL to your externally accessible server that contains data that you're going to want to pull down (e.g. from a RESTful Web Service you wrote)
2. In your push handling code, you would extract this URL to your server and then start downloading the appropraite content from that URL.
It's not really constrained to a particular device or OS. It's more a design pattern you can use.