Comment # 1
on bug 13190
from Peter Wu
Copying comments from a related patch https://code.wireshark.org/review/18721 :
What about using timestamps with greater precision?
See https://doc.qt.io/qt-5/qdatetime.html#fromMSecsSinceEpoch
The timestamp seems to be implied to be UTC, is that desired?
Can we learn something from the nstime APIs for choosing an appropriate format?
Note that even if we decide to accept (say) a floating point number as
argument, the internal storage can be different (time_t, guint64, etc.).
(Another option is to store a string like RFC 3339-style "2006-08-14
02:34:56-06:00" or ISO 8601-style "2006-08-14T02:34:56-0600" which might be
prettier for humans. Leap seconds/hours could be problematic for this though.)
Simone, could you clarify your use case for ntop?
You are receiving this mail because:
- You are watching all bug changes.