Bruno Jesus 00cpxxx@gmail.com writes:
diff --git a/server/protocol.def b/server/protocol.def index fec5e75..1e83862 100644 --- a/server/protocol.def +++ b/server/protocol.def @@ -1250,6 +1250,7 @@ enum server_fd_type int family; /* family, see socket manpage */ int type; /* type, see socket manpage */ int protocol; /* protocol, see socket manpage */
- unsigned int connect_time; /* time the socket was connected (tick count) */
There doesn't seem to be any reason to return a tick count (as opposed to a normal server timestamp).
On Fri, Oct 24, 2014 at 11:16 AM, Alexandre Julliard julliard@winehq.org wrote:
Bruno Jesus 00cpxxx@gmail.com writes:
diff --git a/server/protocol.def b/server/protocol.def index fec5e75..1e83862 100644 --- a/server/protocol.def +++ b/server/protocol.def @@ -1250,6 +1250,7 @@ enum server_fd_type int family; /* family, see socket manpage */ int type; /* type, see socket manpage */ int protocol; /* protocol, see socket manpage */
- unsigned int connect_time; /* time the socket was connected (tick count) */
There doesn't seem to be any reason to return a tick count (as opposed to a normal server timestamp).
Thanks for the review. I used tick count because it's monotonic. What is a server timestamp? Can you point an example, please?
Best wishes, Bruno
Bruno Jesus 00cpxxx@gmail.com writes:
There doesn't seem to be any reason to return a tick count (as opposed to a normal server timestamp).
Thanks for the review. I used tick count because it's monotonic. What is a server timestamp? Can you point an example, please?
For instance process start/end times.
-
Alexandre Julliard -
Bruno Jesus