Sockect and Http connections in j2me

So far, the saya implementation follows this general data flow
1. Http Post request to confirm the existence of user account/number

String params = "action=get_info&phone="+phone;
String userProfile = sayaConnect.postData("http://54.251.106.122:8080/utils", params);

2. Socket connection to authenticate user on the ws-chat server

mJWC.open("ws://54.251.106.122:8070");

The simplifies implementation work but presents a minor problem on j2me which if not checked might negatively impact on user experience(UX) . Security domains implemented in j2me are very tough and therefore(depending on implementation platform), the user might have to give explicit permission for any action needing the creation of a network connection.

If socketConnection is kept alive, then this permission might only be required once. However, for Http stateless connection, user permission might be required each time a Http request is performed. While this can be partly countered by signing the app(welcome to the messy world of java certificates), the prudent thing is to design the app in a better manner.