27 Oct
2009
27 Oct
'09
7:45 p.m.
"Daniel Pfeifer" <daniel@pfeifer-mail.de> wrote in message news:6d2cdc7bcae533b0939b0137b5b4c0af-EhVcX1dJTQZXRw0RBgwNVDBXdh9XVlpBXkJHHF5ZWC9QVUYKXlZoAFFSQ11aLkQAWlxfR1lSWQg=-webmailer2@server07.webmailer.hosteurope.de...
The number of use cases is limited. Here are some of them:
* connect to a well known address (client) * bind to a well known address -- create listening socket (server)
So what do you propose? An asynchronous constructor for socket?
Nope I did not propose anything like this. For the two use-cases I mentioned, we would need two separate classes -- with a constructor and destructor and a method to return the created file-descriptor/socket-handle.