Problem with ServerSocket Accept Method.

Question

0.00/5 (No votes)

See more:

can anyone suggest me how can i stop accept method for accepting connection .i need to stop accept because i want to execute my callback function in between.

Posted 9-Aug-12 18:59pm

Gauravbaba

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Philip Stuyck · Accepted Answer · 2012-08-09T20:40:00

Very strange question.
You can close the socket of course then you don't have your server listening anymore either.
You can specify in listen that you want to service only 1 connection like this
listen(sock,1).
Other than that I think your application is written entirely wrong because it should not be a problem to execute your callback before returning your processing to accept. Because normally you do something like this :

while(1){
newsockfd = accept(sockfd, (struct sockaddr *) &cli_addr, &clilen);
execute your callback
}

while your callback is executing you cannot accept a new connection.
You should keep the code of your callback as small as possible.
TCP applications are actually meant to handle multiple connections at a time, which makes them quite complicated. Either you end up using select on multiple sockets or using several threads.