Hi Shinji,
> 0) NTP daemon is available anywhere in the Internet > We can adjust RTC within 10 mili seconds over the Internet automatically. > http://en.wikipedia.org/wiki/Network_Time_Protocol > 3-9) If the recorded time means the event occured or event will occured, > we do not have to adjust workstation time. > I understand what you and Tim have addressed only just now. Sorry to > have much time and bother you. Don't mention it. We just want to reach clarity... > > In this connectathon, I assumed virtual time flow. What is 'virtual time flow'? > As your example, > 0) Adjust all workstation using NTP server There seems to be no reason for this, if we don't have to keep our workstations in synch. > 1) Tim send me the file recorded 'event1', '2009-10-30T12:18:11BST' > 2) I received file and record it after change BST to UTC 'event1, > '2009-10-30T09:18Z' and record with timestamp. > 3) I send Tim with the file recorded 'event2', '2010-01-22T01:22:22JST' So you change the datetime on your workstation independently of the other workstations, right? > 4) Tim receive the file and record 'event2', the time may be changed to > UTC/BST with timestamp. > > Each system generate sample records before connectathon. Before? That's to test the whole setup before the connect-a-thon, right? > To simplify > more, all the record within system and messages should be record in UTC > not localized timezonen and presentation layer of each system translate > UTC to localized time zone. +1 (eh, you've got my vote on that one, too :-)) Best, Roger
