aboutsummaryrefslogtreecommitdiff
path: root/src/cryptonote_protocol
diff options
context:
space:
mode:
authorThomas Winget <tewinget@gmail.com>2014-07-23 05:59:31 -0400
committerThomas Winget <tewinget@gmail.com>2014-07-23 05:59:31 -0400
commita99143444c9b67b4bf591ebd66ddec2e79d55407 (patch)
tree4f4aee0b943c302e8033f67e9b361b7ef589a0f9 /src/cryptonote_protocol
parentMissed serializing a get_connections RPC response parameter (diff)
downloadmonero-a99143444c9b67b4bf591ebd66ddec2e79d55407.tar.xz
Changed time_t to uint64_t for serialization
time_t is implementation-, architecture-, and apparently compiler-dependent. As an example, on my machine if I build a 64-bit binary, sizeof(time_t) is 8, but for a 32-bit binary it's 4. uint64_t is therefore much more consistent for serialization, given that RPC calls are potentially made between different machines.
Diffstat (limited to 'src/cryptonote_protocol')
-rw-r--r--src/cryptonote_protocol/cryptonote_protocol_defs.h6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/cryptonote_protocol/cryptonote_protocol_defs.h b/src/cryptonote_protocol/cryptonote_protocol_defs.h
index eddb3b67b..850108858 100644
--- a/src/cryptonote_protocol/cryptonote_protocol_defs.h
+++ b/src/cryptonote_protocol/cryptonote_protocol_defs.h
@@ -27,14 +27,14 @@ namespace cryptonote
std::string peer_id;
uint64_t recv_count;
- time_t recv_idle_time;
+ uint64_t recv_idle_time;
uint64_t send_count;
- time_t send_idle_time;
+ uint64_t send_idle_time;
std::string state;
- time_t live_time;
+ uint64_t live_time;
BEGIN_KV_SERIALIZE_MAP()
KV_SERIALIZE(incoming)