Add basic versioning check to Chromoting's plugin/JS code.

Add basic versioning check to Chromoting's plugin/JS code.

Fixup order of elements in the ScriptableObject interface header. It's supposed to match the .CC file but had gotten seriously out of sync.

BUG=none
TEST=manual


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=86655

[Jamie, 2011-05-25 00:29:34]

Reordering things to improve consistency is worth doing, but can we make it a
separate CL? Combining makes it much harder to verify that the _functionality_
of this CL is correct.

http://codereview.chromium.org/7065036/diff/1005/remoting/client/appengine/st...
File remoting/client/appengine/static_files/chromoting_session.js (right):

http://codereview.chromium.org/7065036/diff/1005/remoting/client/appengine/st...
remoting/client/appengine/static_files/chromoting_session.js:12:
chromoting.apiVersion = 42;
Apart from the HHGTTG reference, why 42? Left-over debugging?

[garykac, 2011-05-25 16:39:43]

Moved comment reorg into separate cl

http://codereview.chromium.org/7065036/diff/1005/remoting/client/appengine/st...
File remoting/client/appengine/static_files/chromoting_session.js (right):

http://codereview.chromium.org/7065036/diff/1005/remoting/client/appengine/st...
remoting/client/appengine/static_files/chromoting_session.js:12:
chromoting.apiVersion = 42;
On 2011/05/25 00:29:34, Jamie wrote:
> Apart from the HHGTTG reference, why 42? Left-over debugging?

Indeed. leftover debugging. I fixed up the webapp version, but missed this.
grr...

[Jamie, 2011-05-25 16:45:15]

LGTM.

[commit-bot: I haz the power, 2011-05-25 18:19:20]

Change committed as 86655