| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
| |
For very high performance systems, we're going to want to be able to
simply push the value reported from the server down onto clients.
If we report realtime now, then all wrapped languages are going to
assume it, meaning that such a change will be impossible later.
|
| |
|
|
|
|
|
| |
Use it to validate that arithmetic on time types makes even some vague
kind of sense.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Change on 2015/01/06 by yangg <yangg@google.com>
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=83351442
|
|
|
|
|
|
|
| |
Change on 2014/12/16 by rsilvera <rsilvera@google.com>
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=82275653
|
|
|
|
|
|
|
|
|
|
|
|
| |
gpr_inf_future and time_point::max(). The redundant AbsoluteDeadline prefix is removed from the utility function names.
Now the ClientContext holds a gpr_timespec instead of a time_point.
A test will be added in the server side deadline support cl.
Change on 2014/12/11 by yangg <yangg@google.com>
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=81920769
|
|
|