Am I reading the dictionary correctly? If I am, the accept command on the server end would use the same "read from socket" and "write from socket" commands as the client size uses?
So when I client first connects to set up a connection, the callback message on the serer would be used for authentication, after which the success/failure of authentication would be sent with the "write to" command, and future callbacks would have stored that the authentication had occurred and therefore proceed to do a "whatever" with more read/write messages? And all of these seem to be SSL? Or do I have to supply my own encryption? And then for the down the road issues, assuming that I'd be running on multi-core servers, could the initial connection actually distribute to a process one of the *n* cores--perhaps by telling the client it's assigned IP/port, at which point it would authenticate again? -- Dr. Richard E. Hawkins, Esq. (702) 508-8462 _______________________________________________ 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
