• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
Sign in to follow this  
Followers 0

Sockets and ConnMgrEstablishConnection

1 post in this topic

Posted

When I first started experimenting with the Motorola Q for socket connections,

I had no problem establishing a socket connection simply using the standard WSAConnect.

In the last few weeks, however, the device stopped being able to connect.

I could not make a socket connection unless I first used something like Explorer.

After exiting explorer the connection would seem to stay up (not good either IMHO),

and WSACOnnect would work.

Doing some more research, it appeared that, perhaps, I should have been initializing the connection

using the connection manager. However, there are a few things which are unclear about using the

connection managers APIs.

In my case I seem to be in a bad area, only able to make data calls sporadically. I'm not minding this at the

moment because it is helping to test that situation.

Specifically:

1. When the data call fails competely, I get a CONNMGR_STATUS_CONNECTIONFAILED - which is fine. However,

a dialog box also pops up saying that the Data Call Failed. Not good. Anyway to get rid of this? My app

assumes its being suspended when it loses activation and so this is causing some problems.

2. I often get a CONNMGR_STATUS_WAITINGCONNECTION status from ConnMgrEstablishConnectionSync.

Its is quite unclear to me at this point if I am supposed to poll ConnMgrConnectionStatus on

CONNMGR_STATUS_CONNECTED, or do another call to ConnMgrEstablishConnection

or ConnMgrEstablishConnectionSync periodically.

Currently I am just waiting but often after even 30 seconds the status has not changed. Occasionally I get connected

immediately, but so far this is never after a CONNMGR_STATUS_WAITINGCONNECTION. THis makes me suspcious that

I am doing something wrong when getting this message.

thanks in advance for any suggestions/help

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.