@@ -486,8 +486,8 @@ void ReadClient::OnActiveModeNotification()
486
486
{
487
487
VerifyOrDie (mpImEngine->InActiveReadClientList (this ));
488
488
489
- // Note: this API only works when issuing subscription via SendAutoResubscribeRequest, when SendAutoResubscribeRequest is called,
490
- // either mEventPathParamsListSize or mAttributePathParamsListSize is not 0.
489
+ // Note: this API only works when issuing subscription via SendAutoResubscribeRequest, when SendAutoResubscribeRequest is
490
+ // called, either mEventPathParamsListSize or mAttributePathParamsListSize is not 0.
491
491
VerifyOrDie (mReadPrepareParams .mEventPathParamsListSize != 0 || mReadPrepareParams .mAttributePathParamsListSize != 0 );
492
492
493
493
// When we reach here, the subscription definitely exceeded the liveness timeout. Just continue the unfinished resubscription
@@ -498,8 +498,9 @@ void ReadClient::OnActiveModeNotification()
498
498
return ;
499
499
}
500
500
501
- // If the server sends out check-in message, and there is no reschedule subscription yet in client side at the same time, it means
502
- // current client does not realize subscription has gone, and we should forcibly timeout current subscription, and schedule a new one.
501
+ // If the server sends out check-in message, and there is no reschedule subscription yet in client side at the same time, it
502
+ // means current client does not realize subscription has gone, and we should forcibly timeout current subscription, and
503
+ // schedule a new one.
503
504
if (!mIsResubscriptionScheduled )
504
505
{
505
506
// Closing will ultimately trigger ScheduleResubscription with the aReestablishCASE argument set to true, effectively
@@ -508,8 +509,8 @@ void ReadClient::OnActiveModeNotification()
508
509
return ;
509
510
}
510
511
511
- // If the server sends a check-in message and a subscription is already scheduled, it indicates a client-side subscription timeout or failure.
512
- // Cancel the scheduled subscription and initiate a new one immediately.
512
+ // If the server sends a check-in message and a subscription is already scheduled, it indicates a client-side subscription
513
+ // timeout or failure. Cancel the scheduled subscription and initiate a new one immediately.
513
514
TriggerResubscribeIfScheduled (" check-in message" );
514
515
}
515
516
0 commit comments