> On Apr 19, 2017, at 5:00 PM, Benjamin Mahler wrote:
>
> We can add a Call.GetTasks message to allow you to specify which task ids you
> would like to retrieve. But this isn't supported yet, the code needs to be
> written. E.g.
>
> message Call {
> enum Type {
>
We can add a Call.GetTasks message to allow you to specify which task ids
you would like to retrieve. But this isn't supported yet, the code needs to
be written. E.g.
message Call {
enum Type {
GET_TASKS = 13; // Retrieves the information about tasks, see
`GetTasks` below.
}
Hi Maxime,
Thanks for the feedback!
The proposed approach is definitely simplistic. The "Discussion"
section of the design doc describes some of the rationale for starting
with a very simple scheme: basically, because
(a) we want to assign clear semantics to the levels of the hierarchy
(regions
Hello,
sorry to insist, is the understanding below correct ? I'm really not sure.
I understand that network/portmapping isolator is using disjoint port
ranges to multiplex traffic into the same ports into containers but I'm
not really sure if we're talking about ephemeral or non-ephemeral
4 matches
Mail list logo