Negative time span between client and server for TCP socket communication

Question

0.00/5 (No votes)

See more:

Negative time span between Client and Server for TCP Socket communication.

What I have tried:

Hi

I am having Client and Server TCP socket communication for which i am calculating Upload speed by sending a file in byte format from Client to Server. I am taking the Send time(in UTC format) from Client and from Server side I am taking Receive time(in UTC format). It works fine when both Server and client maintain same time (including seconds).

But the problem comes when the Server is lagging time(few seconds) than Client time. Hence I am getting negative time span when I calculate the Traverse time of the file packet from Client to Server. Though i manually change the Server time it takes its actually time back.

Also few client machines may have their time wrongly configured in their system.

Please provide the best approach or solution to resolve this issue.

Thanks in Advance

Posted 1-Aug-16 1:57am

sarath.mk

Updated 1-Aug-16 2:38am

v2

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)

OriginalGriff · Answer 1 · 2016-08-01T02:38:00

Simple: always use the same time source: normally the server.
Get the time from the server when you start, get it again when you finish.
As soon as you start using separate time sources you will get problems as PC clocks aren't particularly accurate - they don't need to be - as they are often "corrected" from an internet source and by default Windows does this once a week.