TCP Connection resources

Question

0.00/5 (No votes)

See more:

Hi Guys

I am creating a client embedded application to execute from inside a GPRS modem.

Regarding TCP connections, is it more resource intensive to create and then disconnect TCP connection continuously(i.e polling), or is it more resource intensive to keep a TCP connection open all the time??

Thank you

Regards

Posted 11-Nov-10 13:05pm

sach262

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)

E.F. Nijboer · Answer 1 · 2010-11-11T22:08:00

When polling is done once every x seconds it might be better to disconnect and maybe even delete the object, otherwise it would probably be more efficient to keep it going. It's a trade off between keeping the connection and with that the memory needed or otherwise freeing up memory but need more cycles to setup the connection again.

It would probably be best to test both methods if you're still not sure. The polling can be done by some separate code that can then be easily replaced with any other polling scheme. You could also think of a method where the connection is kept open for some time before closing it to avoid fast disconnect/connect actions when polling more intensively. So even a more dynamic scheme could be interesting to test before choosing the actual implementation you are going to use.

Good luck!