Hi, Jiaju
A reply becomes slow, and I'm sorry.
2013/2/12 Jiaju Zhang :
> Hi Yusuke,
>
>
> Just look at the patch, it seems to me that it wanted to differentiate
> every state like "init", "waiting promise", "promised", "waiting accept"
> and "accepted", etc ... However I'm afraid in this way, it
Hi Yusuke,
On Tue, 2013-02-12 at 11:52 +0900, yusuke iida wrote:
> Hi, Jiaju
>
> 2012/12/18 Jiaju Zhang :
> > Good suggestion! I think it may need to introduce a notifier callback so
> > that the failure of communicating with the problematic node can be
> > notified to the "active" node. This mak
Hi, Jiaju
2012/12/18 Jiaju Zhang :
> Good suggestion! I think it may need to introduce a notifier callback so
> that the failure of communicating with the problematic node can be
> notified to the "active" node. This makes sense for the active node,
> because it will make the admin know how many h
On Mon, 2012-12-17 at 22:14 +0900, yusuke iida wrote:
> Hi, Jiaju
>
> I would like to attach the function which displays a communicative
> state on booth.
> In the present booth, when communication between sites stops service,
> no errors are told.
> If it becomes like this, the user cannot notice
Hi, Jiaju
I would like to attach the function which displays a communicative
state on booth.
In the present booth, when communication between sites stops service,
no errors are told.
If it becomes like this, the user cannot notice a problem.
I think that he would like to define newly the variable
