Renaming variables in p2ptransportchannel to be consistent.

Renaming variables in p2ptransportchannel to be consistent.
Also change the type of "time interval" to int from uint32.
Fixed a few TODO therein. I think we should have the following convention:
1. All time delay/intervals should have type int although the time instant should have time uint32_t.
2. "interval" is preferred to "delay" if the delay will be repeated (like rescheduling).

BUG=
R=pthatcher@webrtc.org

Committed: https://chromium.googlesource.com/external/webrtc/+/049fbb1883344dd32081bf6ae02012aef927eaea

[honghaiz3, 2016-03-03 22:37:04]

Description was changed from

==========
Renaming variables in p2ptransportchannel to be consistent.
Also change all "time interval" to type int from uint32.

BUG=
==========

to

==========
Renaming variables in p2ptransportchannel to be consistent.
Also change all "time interval" to type int from uint32.
Fixed a few TODO therein.

BUG=
==========

[honghaiz3, 2016-03-03 22:50:21]

Patchset #1 (id:1) has been deleted

[honghaiz3, 2016-03-03 22:50:34]

Patchset #2 (id:40001) has been deleted

[honghaiz3, 2016-03-03 22:50:45]

Patchset #1 (id:20001) has been deleted

[honghaiz3, 2016-03-03 22:55:46]

honghaiz@webrtc.org changed reviewers:
+ deadbeef@webrtc.org, pthatcher@webrtc.org

[honghaiz3, 2016-03-03 22:59:09]

Description was changed from

==========
Renaming variables in p2ptransportchannel to be consistent.
Also change all "time interval" to type int from uint32.
Fixed a few TODO therein.

BUG=
==========

to

==========
Renaming variables in p2ptransportchannel to be consistent.
Also change the type of "time interval" to int from uint32.
Fixed a few TODO therein. I think we should have the following convention:
1. All time delay/intervals should have type int although the time instant
should have time uint32_t.
2. "interval" is preferred to "delay" if the delay will be repeated (like
rescheduling). 

BUG=
==========

[pthatcher1, 2016-03-05 01:33:15]

lgtm

[honghaiz3, 2016-03-07 18:21:29]

The CQ bit was checked by honghaiz@webrtc.org

[honghaiz3, 2016-03-07 18:21:29]

The patchset sent to the CQ was uploaded after l-g-t-m from pthatcher@webrtc.org
Link to the patchset: https://codereview.webrtc.org/1762863002/#ps100001 (title:
"Fix a small bug introduced previously")

[commit-bot: I haz the power, 2016-03-07 18:21:37]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1762863002/100001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1762863002/100001

[commit-bot: I haz the power, 2016-03-07 19:13:18]

Description was changed from

==========
Renaming variables in p2ptransportchannel to be consistent.
Also change the type of "time interval" to int from uint32.
Fixed a few TODO therein. I think we should have the following convention:
1. All time delay/intervals should have type int although the time instant
should have time uint32_t.
2. "interval" is preferred to "delay" if the delay will be repeated (like
rescheduling). 

BUG=
==========

to

==========
Renaming variables in p2ptransportchannel to be consistent.
Also change the type of "time interval" to int from uint32.
Fixed a few TODO therein. I think we should have the following convention:
1. All time delay/intervals should have type int although the time instant
should have time uint32_t.
2. "interval" is preferred to "delay" if the delay will be repeated (like
rescheduling).

BUG=
R=pthatcher@webrtc.org

Committed: https://crrev.com/049fbb1883344dd32081bf6ae02012aef927eaea
Cr-Commit-Position: refs/heads/master@{#11888}
==========

[honghaiz3, 2016-03-07 19:13:18]

Description was changed from

==========
Renaming variables in p2ptransportchannel to be consistent.
Also change the type of "time interval" to int from uint32.
Fixed a few TODO therein. I think we should have the following convention:
1. All time delay/intervals should have type int although the time instant
should have time uint32_t.
2. "interval" is preferred to "delay" if the delay will be repeated (like
rescheduling).

BUG=
R=pthatcher@webrtc.org

Committed: https://crrev.com/049fbb1883344dd32081bf6ae02012aef927eaea
Cr-Commit-Position: refs/heads/master@{#11888}
==========

to

==========
Renaming variables in p2ptransportchannel to be consistent.
Also change the type of "time interval" to int from uint32.
Fixed a few TODO therein. I think we should have the following convention:
1. All time delay/intervals should have type int although the time instant
should have time uint32_t.
2. "interval" is preferred to "delay" if the delay will be repeated (like
rescheduling).

BUG=
R=pthatcher@webrtc.org

Committed:
https://chromium.googlesource.com/external/webrtc/+/049fbb1883344dd32081bf6ae...
==========

[commit-bot: I haz the power, 2016-03-07 19:13:19]

Patchset 3 (id:??) landed as
https://crrev.com/049fbb1883344dd32081bf6ae02012aef927eaea
Cr-Commit-Position: refs/heads/master@{#11888}

[honghaiz3, 2016-03-07 19:13:19]

Committed patchset #3 (id:100001) manually as
049fbb1883344dd32081bf6ae02012aef927eaea (presubmit successful).