T
Tim Kuehn
Guest
I'm trying to clarify an ambiguity in the docs - there's reference to a server socket object and a socket object - do these two objects overlap in terms of functionality? I would expect them to be different in terms of configuration and enabling, and have commonality in terms of sending and receiving data. The docs don't make that clear - the server socket docs have this: INSTANTIATING-PROCEDURE attribute, NAME attribute, HANDLE attribute, NEXT-SIBLING attribute, PREV-SIBLING attribute PRIVATE-DATA attribute, SENSITIVE attribute TYPE attribute Methods DISABLE-CONNECTIONS( ) method ENABLE-CONNECTIONS( ) method, SET-CONNECT-PROCEDURE( ) method Events CONNECT event While the socket docs have BYTES-READ attribute BYTES-WRITTEN attribute HANDLE attribute INSTANTIATING-PROCEDURE attribute LOCAL-HOST attribute LOCAL-PORT attribute NAME attribute NEXT-SIBLING attribute PREV-SIBLING attribute PRIVATE-DATA attribute REMOTE-HOST attribute REMOTE-PORT attribute SENSITIVE attribute SSL-SERVER-NAME attribute TYPE attribute Methods CONNECT( ) method (Socket object) CONNECTED( ) method DISCONNECT( ) method (Handle) GET-BYTES-AVAILABLE( ) method GET-SOCKET-OPTION( ) method READ( ) method (Socket) SET-READ-RESPONSE-PROCEDURE( ) method SET-SOCKET-OPTION( ) method WRITE( ) method (Socket) Some of the socket functionality could apply to server sockets, others clearly do not. Which is which isn't clear.
Continue reading...
Continue reading...