Did you accept connection on port aConnection["deport”]? I think it’s possible for the open socket to remain in the openSockets list until the connection times out. Grab message socketTimeout pSocketID to see if it’s timing out without connecting.
Eric On Jul 6, 2015, at 12:36 PM, Bob Sneidar <bobsnei...@iotecdigital.com> wrote: > Hi all. > > I am trying to use open socket like this: > > put aConnection["dbhost"] & ":" & aConnection["dbport"] into theSocket > open secure socket to theSocket with message socketConnected > wait for messages > put the openSockets into theOpenSockets > close socket theSocket > > I have this handler in the same script: > on socketConnected > -- callBack for open socket commands > put "connected!" > end socketConnected > > The problem is, socketConnected never gets called. The connection works > because theOpenSockets contains the connection as it should, but I never get > the callback. What am I missing? > > Bob S > > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
