Date and time type for use with Protobuf?

Although you aren't saying which languages you are using or what kind of precision you need, I would suggest using Unix time encoded into a int64 It is fairly easy to handle in most languages and platforms (see here for a Windows example), and Protobufs will use a varint-encoding keeping the size small without limiting the representable range too much.

Although you aren't saying which languages you are using or what kind of precision you need, I would suggest using Unix time encoded into a int64. It is fairly easy to handle in most languages and platforms (see here for a Windows example), and Protobufs will use a varint-encoding keeping the size small without limiting the representable range too much.

– JesperE Dec 7 '11 at 16:24 Unix time consumes only 4 bytes, which is quite an efficient encoding. But for dates after 2038, it requires more than 4 bytes – JoelFan Dec 7 '11 at 18:30 Unix time is not specified in terms of how many bytes it takes up, it is defined as the number of seconds since the epoch. Traditionally it has been represented as a 32-bit integer, but most operating system uses 64-bit integers today.

– JesperE Dec 7 '11 at 20:31 The wikipedia page on Unix time contains more info, in case you are interested: en.wikipedia.org/wiki/Unix_time – JesperE Dec 7 '11 at 20:32.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.