Local (but not local) Sockets Testing

Question

5.00/5 (1 vote)

See more:

Hi Everyone,

I'm implementing asynchonous socket programming in (C++, winsock, TCP/IP, based on this example Chat Client Server[^]) at the moment (for data streaming) and am running into problems with missing data when I run the code over a network rather than locally (I only seem to recieve a packet every 0.7s, despite sending them every 0.1s).

Its a pain to ask my colleague to run my client code on his computer everytime I want to debug, so I wonder if it's possible to run my client and server on the same machine but to send the message over a physical network & router, to re-create the same problem? So, instead of my client connecting to 127.0.0.1, I actually connect it to my IP address and the message goes through my phsycial hub.

Is this possible? Or am I barking up the wrong tree? :confused:

Thanks,

Ad

Posted 17-Jan-11 5:43am

ad_robot

Add a Solution

Comments

Manfred Rudolf Bihy 17-Jan-11 14:50pm

Good question! 5+

3 solutions

Solution 3

A few pointers that you may or may not already know:

Remote debugging can be set up by running msvsmon.exe from C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\<platform>\msvsmon.exe on the remote computer or VM. This is in the 64-bit Program Files on a 64-bit computer, then in the debugging page of the project properties select Remote Windows Debugger from the drop-down list

Packets are generally concatenated together, hence you might be receiving 7 packets every 0.7 seconds if it takes your code that long to get back around to checking.

Posted 17-Jan-11 15:48pm

Andrew Brock

Comments

ad_robot 18-Jan-11 5:36am

"Packets are generally concatenated together...", ah, interesting, I'll have to look into this. Thanks for the tips.

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)

dasblinkenlight · Accepted Answer · 2011-01-17T06:21:00

In my experience, running your client in a virtual machine on the same computer as the server lets you simulate real-world client-server environments very realistically. Our company used VMWare's and Microsoft's virtualization products for debugging and in QA; both worked very well for our purposes. It looks like this approach may work in your case as well - the code path inside the framework and OS will be the same as in a non-local client-server scenario, except the packets will not travel to the router and back.

HimanshuJoshi · Accepted Answer · 2011-01-17T06:16:00

Solution 1

Virtual machine might be an answer here; but I advice that get another dedicated machine for testing from your employers since it will be far better to test on actual physical layer than any kind of simulation.

On a second thought, there is one more thing you can do,
1. Get another network card for your machine
2. Connect it to a switch and assign IP address
3. You will get two different IP addresses on your machine
4. Run server on one IP and client on another and connect them.

Posted 17-Jan-11 6:16am

HimanshuJoshi

Updated 18-Jan-11 5:10am

v2

Comments

Espen Harlinn 17-Jan-11 13:11pm

5+ Nice and easy

HimanshuJoshi 17-Jan-11 13:35pm

Thanks Espenn

Manfred Rudolf Bihy 17-Jan-11 14:49pm

Good idea! 5+

HimanshuJoshi 17-Jan-11 15:26pm

Thanks Manfred R. Bihy

Sergey Alexandrovich Kryukov 17-Jan-11 19:28pm

Very useful list of options - my 5.
Thank you,
--SA

HimanshuJoshi 17-Jan-11 21:31pm

Thanks SA

ad_robot 18-Jan-11 5:34am

Thanks for the different options. The network card option sounds very appealing, I think I'll try that out first.

Local (but not local) Sockets Testing

3 solutions

Solution 2

Solution 1

Solution 3

Add your solution here

Preview 0

Existing Members

...or Join us