Please forgive the noob questions, but I've been scouring the internet, and I can't find any concrete answers to the following.
I'm developing an application that will stream audio from a remote data provider. I've gotten around the 413 (request entity too large) issues by using ranged requests, and that works fine. My question is regarding MDS versus direct TCP.
If I'm developing my app to make use of MDS and testing via the simulator, does this mean I'll have to purchase a BES before I deploy? If so, I suppose the alternative is direct TCP, which apparently requires me to specify an APN. I haven't been able to get this to work with my local simulator. I've tried adding deviceside=true and EndToEndRequired to my connector string, and the app just hangs.
One final problem, the simulator used in conjunction with MDS downloads at a fraction of the speed of Google's android dev stack. I'm getting roughly 10k/second while android gets 100k/sec. Any ideas how this could be improved?
Thanks in advance,
inre: "If I'm developing my app to make use of MDS and testing via the simulator, does this mean I'll have to purchase a BES before I deploy?"
no not really. you can deploy applications without having a BES, users would be using their own BES/MDS environment, not yours. If however you have a blackberry and would want to test it in a BES environment that you currently don't have, I suppose yeah you'd have to get a BES and run through there.
inre: " I've tried adding deviceside=true and EndToEndRequired to my connector string, and the app just hangs."
fwiw, deviceside=true + end2endreq specifies a BIS connection, not direct tcp. I haven't been able to make the MDS work w/ bis, but there may be a way. I'd suggest adding some error logging to prevent the 'just hangs' issue and work from there
|All times are GMT -5. The time now is 12:44 PM.|
Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2015, Jelsoft Enterprises Ltd.