GCP2.0 Device: XMPP pings.

GCP2.0 Device: XMPP pings.

BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=216107

[maksymb, 2013-08-02 19:17:42]

138 lines

[gene, 2013-08-06 20:05:06]

lgtm,
nit below

https://chromiumcodereview.appspot.com/21916003/diff/12001/cloud_print/gcp20/...
File cloud_print/gcp20/prototype/cloud_print_xmpp_listener.cc (right):

https://chromiumcodereview.appspot.com/21916003/diff/12001/cloud_print/gcp20/...
cloud_print/gcp20/prototype/cloud_print_xmpp_listener.cc:18: const int
kUrgentPingInterval = 60;  // in seconds
Looking at the code, it looks like urgent timeout will be send after 90 seconds
(kPingTimeout + kUrgentPingInterval) from the previous ping. Could you please
change it so it will be send after 60 seconds?

[maksymb, 2013-08-06 20:27:14]

https://codereview.chromium.org/21916003/diff/12001/cloud_print/gcp20/prototy...
File cloud_print/gcp20/prototype/cloud_print_xmpp_listener.cc (right):

https://codereview.chromium.org/21916003/diff/12001/cloud_print/gcp20/prototy...
cloud_print/gcp20/prototype/cloud_print_xmpp_listener.cc:18: const int
kUrgentPingInterval = 60;  // in seconds
On 2013/08/06 20:05:06, gene wrote:
> Looking at the code, it looks like urgent timeout will be send after 90
seconds
> (kPingTimeout + kUrgentPingInterval) from the previous ping. Could you please
> change it so it will be send after 60 seconds?

Done.

[commit-bot: I haz the power, 2013-08-06 20:28:03]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/maksymb@chromium.org/21916003/18001

[commit-bot: I haz the power, 2013-08-07 02:34:37]

Retried try job too often on android_dbg for step(s) slave_steps
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=android_db...

[commit-bot: I haz the power, 2013-08-07 02:41:41]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/maksymb@chromium.org/21916003/18001

[commit-bot: I haz the power, 2013-08-07 06:01:31]

Change committed as 216107