Separate threads for connector and acceptor in boost asi
I have a scenario wherein I have a modified version of Blocking Synchronous TCP Client. According to my design I need to open an acceptor on my Client with a different port for listening connections.
The socket acceptor is called only after it receives a particular message from the server. I expected the acceptor to have created a socket with different port and wait for connections and the previous connection of the socket made with the server to continue its operations.
However my code is linear, when the acceptor is called, my code waits for the establishment of a connection. I understood I have to create a separate thread for this scenario.
As I’m relatively new to boost Asio I would like to get some help regarding this, where I would like to run two threads, one connected to a port and one accepting connections to a defined port where the second thread accepting the connection needs to be called from the first thread connected to the Port.
I’m not able to realise this scenario, I would be thankful for any help on this.
Thanking you in advance!
boost-asio
add a comment |
I have a scenario wherein I have a modified version of Blocking Synchronous TCP Client. According to my design I need to open an acceptor on my Client with a different port for listening connections.
The socket acceptor is called only after it receives a particular message from the server. I expected the acceptor to have created a socket with different port and wait for connections and the previous connection of the socket made with the server to continue its operations.
However my code is linear, when the acceptor is called, my code waits for the establishment of a connection. I understood I have to create a separate thread for this scenario.
As I’m relatively new to boost Asio I would like to get some help regarding this, where I would like to run two threads, one connected to a port and one accepting connections to a defined port where the second thread accepting the connection needs to be called from the first thread connected to the Port.
I’m not able to realise this scenario, I would be thankful for any help on this.
Thanking you in advance!
boost-asio
add a comment |
I have a scenario wherein I have a modified version of Blocking Synchronous TCP Client. According to my design I need to open an acceptor on my Client with a different port for listening connections.
The socket acceptor is called only after it receives a particular message from the server. I expected the acceptor to have created a socket with different port and wait for connections and the previous connection of the socket made with the server to continue its operations.
However my code is linear, when the acceptor is called, my code waits for the establishment of a connection. I understood I have to create a separate thread for this scenario.
As I’m relatively new to boost Asio I would like to get some help regarding this, where I would like to run two threads, one connected to a port and one accepting connections to a defined port where the second thread accepting the connection needs to be called from the first thread connected to the Port.
I’m not able to realise this scenario, I would be thankful for any help on this.
Thanking you in advance!
boost-asio
I have a scenario wherein I have a modified version of Blocking Synchronous TCP Client. According to my design I need to open an acceptor on my Client with a different port for listening connections.
The socket acceptor is called only after it receives a particular message from the server. I expected the acceptor to have created a socket with different port and wait for connections and the previous connection of the socket made with the server to continue its operations.
However my code is linear, when the acceptor is called, my code waits for the establishment of a connection. I understood I have to create a separate thread for this scenario.
As I’m relatively new to boost Asio I would like to get some help regarding this, where I would like to run two threads, one connected to a port and one accepting connections to a defined port where the second thread accepting the connection needs to be called from the first thread connected to the Port.
I’m not able to realise this scenario, I would be thankful for any help on this.
Thanking you in advance!
boost-asio
boost-asio
edited Nov 13 '18 at 7:04
Mayur
3,57762652
3,57762652
asked Nov 12 '18 at 22:15
indigoindigo
12
12
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53270880%2fseparate-threads-for-connector-and-acceptor-in-boost-asi%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53270880%2fseparate-threads-for-connector-and-acceptor-in-boost-asi%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown