If we launch a HTTP connection, according the security domains the AMS/JAM asks to the user "allow the network access". Well, if we select "Yes", the application continues working, but if we select "Not", during the same application lifecycle session, always that we try to make a HTTP connection, the AMS/JAM doesn't allow it to us.
Well we have the following problem, and probably you can help us. We really don't know if we are developing in a wrong way or the mobile phone AMS/JAM is managing the "oneshot" with the HTTP sessions in a wrong way.
The MIDP standard defines three modes:
- Oneshot to prompt the user at each invocation.
- Session to prompt the user once each time the application runs
- Blanket to prompt the user only once in the whole time it remains installed on the device.
Our conclusion, is that the after a "Not" response to the first question "allow the network access", the JAM/AMS should ask again for new intents until a "Yes" response. In other case, after the first "Not" the user will be under obligation to close the application and to open it again.
Dou you know if we can have a solution for this?