Explain to me about timewarps

[T_Yamamoto]

Like how do they happen?

This is a serious question.

 

[waggy]

It's just a jump to the left.

 

[Snock514]

Sorry..

 

[MontyAC]

The site needs a little maintenance. [removed]

We don't support Base64 images, so I'm not sure what it is you're trying to accomplish...
-ViRGE

 

[Newbian]

If you have to ask then you will not understand.

 

[jpiniero]

Bet it's something dumb like the clocks on one of the servers gets out of whack.

 

[T9D]

This should help:

http://www.youtube.com/watch?v=Rtkdo7bOmJc

 

[schneiderguy]

You will understand when you are older.

 

[shortylickens]

 

[Pardus]

The terms time warp, space warp and time-space warp are commonly used in science fiction. They sometimes refer to Einstein's theory that time and space form a continuum which bends, folds or warps from the observer's point of view, relative to such factors as movement or gravitation, but are also used in reference to more fantastic notions of discontinuities or other irregularities in spacetime not based on real-world science.

According to Einstein's theory of general relativity, when a body of mass "m" and volume "V" (each length of "l") moves with a velocity "v", then its physical properties change in many ways. Its length decreases and mass increases. These factors keep on increasing and decreasing with the increase in velocity. When the body reaches the speed of light "c", its length becomes zero, its mass becomes infinite and the time factor vanishes. In other words, no time passes inside the event horizon of the moving body. In this way, the body sometimes takes irregular shapes and covers a distance of millions of light years in no time, because the passage of time for that moving body has vanished. During this process, the body is said to be moving with a (time-)warp speed.

http://en.wikipedia.org/wiki/Time_warp_(science_fiction)

 

[Theb]

The database is perfectly fine, it's actually the users that jump through time.

 

[DrPizza]

Multiple servers & the time gets out of whack on one of them.

 

[Mixolydian]

multiple servers & the time gets out of whack on one of them.

sync! Sync! Sync!

 

[l0cke]

Blame Fusetalk

 

[Markbnj]

There's a rift, in Cardiff.

 

[cbrunny]

It's just a jump to the left.

And then a step to the right!

 

[tfinch2]

Multiple servers & the time gets out of whack on one of them.

Not using NTP?

 

[disappoint]

Multiple servers & the time gets out of whack on one of them.

Get rubidium frequency standards on all of your servers and you'll never have that problem again. You'll only have to set them once.

Accurate timekeeping off by a maximum of ~1 millisecond per year. Atomic clocks are the bomb. Yo.:awe:

 

[disappoint]

The database is perfectly fine, it's actually the users that jump through time.

Why would it rely on the users machines for timekeeping?

 

[Train]

For a second I thought timewarps was an anagram for wiretaps, but then realized I was a letter off. Was just about to head over to meme generator, damn

 

[Jaepheth]

Bob makes a post which is sent to Server A which timestamps it X
Alice posts a reply which gets sent to Server B which time stamps it Y

A and B went out recently and between appetizers and entrees they had an argument over the efficacy of daylight savings. This situation devolved over the next half hour and by dessert Server A was already very sick of Server B's passive aggressive attitude. The bill came and B brought up how automatic tipping was bullshit. Well, A had just had enough and made a rather crude remark about how Server B's manufacturer programmed it. B then made a comment recounting its time as a music server when it got used to 1/4" stereo connectors and A's RJ48 connector just wasn't the same. By the next morning A and B wanted nothing to do with each other and when B called A to set their watches, A let it go to voice-mail. As a result, when it came time to time-stamp Bob and Alice's posts A's clock was behind; which resulted in X > Y.

Now when the posts are sorted by time (ascending) Alice's reply gets placed before Bob's original post.

 

[MagickMan]

It's just a jump to the left.

Winner!

 

[Leros]

This problem could easily be solved if the database set the timestamp itself instead of the server specifying the timestamp value. I'm assuming there is a single database master where all writes go.

 

[Howard]

Bob makes a post which is sent to Server A which timestamps it X
Alice posts a reply which gets sent to Server B which time stamps it Y

A and B went out recently and between appetizers and entrees they had an argument over the efficacy of daylight savings. This situation devolved over the next half hour and by dessert Server A was already very sick of Server B's passive aggressive attitude. The bill came and B brought up how automatic tipping was bullshit. Well, A had just had enough and made a rather crude remark about how Server B's manufacturer programmed it. B then made a comment recounting its time as a music server when it got used to 1/4" stereo connectors and A's RJ48 connector just wasn't the same. By the next morning A and B wanted nothing to do with each other and when B called A to set their watches, A let it go to voice-mail. As a result, when it came time to time-stamp Bob and Alice's posts A's clock was behind; which resulted in X > Y.

Now when the posts are sorted by time (ascending) Alice's reply gets placed before Bob's original post.

wat

 

[Crono]