Author | Topic: SocketNegotiateSSL() | |
---|---|---|
![]() | Jonathan Leeming | SocketNegotiateSSL() on Fri, 27 Mar 2015 11:28:06 -0600 Hi, I'm trying to figure out how to impliment SSL websockets and came across this comand in the documentation. I seem to remember at the last SouthWest Xbase conference that there was a brief discussion about SSL and Web Sockets with the answer that it is not currently available. Given that... What does this SocketNegotiateSSL() actually do and is it possible now to have SSL web socket connections. I looked through the sample but could not find an example of the impimentaion of this. Any quick hints would certainly be appreciated... actual examples would bring out my everlasting gratitude! Thanks... Jonathan |
![]() | Andreas Herdt | Re: SocketNegotiateSSL() on Wed, 29 Apr 2015 09:55:42 +0200 Hi Jonathan, The function SocketNegotiateSSL() is doing exactly what the name implies. After a connection using that function an SSL handshake is performed with the server. After that all communication through the socket (read and write) is secured. I looked at our implementation of WebSocket, with the next drop the WebSocketClient uses that function if being connected at port 443. The drawback appears now |
![]() | Jonathan Leeming | Re: SocketNegotiateSSL() on Thu, 30 Apr 2015 11:34:50 -0600 Thanks Andreas, I am looking to have both the client & server sides written in Xbase++ so obviously the "drawback" will be the limiting factor until it perculates up the agenda. Regards... Jonathan On Wed, 29 Apr 2015 09:55:42 +0200, Andreas Herdt wrote: >Hi Jonathan, > >The function SocketNegotiateSSL() is doing exactly what the name >implies. After a connection using that function an SSL handshake >is performed with the server. After that all communication through the >socket (read and write) is secured. > >I looked at our implementation of WebSocket, with the next drop >the WebSocketClient uses that function if being connected at port >443. > >The drawback appears now |