12-31-2008 12:47 PM
If my app does NOT make any connections to a BES should
I be able to make any other conenctions (eg. WiFi, BIS, TCP, WAP, File)
without getting the split pipe error message even if the user
is connected to a BES?
12-31-2008 12:51 PM
12-31-2008 01:14 PM
I'm not positive on this, but I think that file connections are private.
Our application runs into problems when non-BES device's have their firewall enabled (we have to have users turn it off, which is not ideal). Our application uses BIS to connect to the internet, and also uses the FileConnection API to write data files to the store/home/user path.
So what I guess I'm saying is that from my experience, you can still run into problems even if you are not going through a BES...
12-31-2008 01:27 PM - edited 12-31-2008 01:28 PM
Oh, ok..."not" connected to a BES. I'll have to bow out and let someone who knows the development side better than me come in and help.
The connections can be funny, though. I installed an app on a non BES device-no policy and firewall off. I got the split pipe error when the firewall was off and had to turn on the firewall to get rid of it (I wouldn't think it should work this way...seems opposite to me.) Same app on a BES device and it worked fine. Someone else will need to explain!
01-02-2009 10:12 AM
The split pipe error seems extremely inconsistent to me.
I've seen cases where the firewall was locked although the user was never on BES and there is no IT policy on the device.
I've seen cases where non BES users have to turn off the firewall to use Wifi.
I've seen cases where non BES users have to turn ON the firewall to make other connections.
It seems to depend on the particular model and OS version.
I wish this was documented or at least someone could answer my original question.