Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(376)

Issue 7829046: code review 7829046: go.talks/present: make js use correct websocket a...

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 10 months ago by cespare
Modified:
12 years, 9 months ago
Reviewers:
adg
CC:
golang-dev, adg
Visibility:
Public.

Description

go.talks/present: make js use correct websocket address This makes the client connect to the host from which it's being served, rather than being hardcoded to localhost:3999. Right now, if you try to run with -http set to any port other than 3999, you'll get websocket closed as soon as you open the presentation.

Patch Set 1 #

Patch Set 2 : diff -r 4bd876a6faad https://code.google.com/p/go.talks/ #

Patch Set 3 : diff -r 4bd876a6faad https://code.google.com/p/go.talks/ #

Unified diffs Side-by-side diffs Delta from patch set Stats (+2 lines, -2 lines) Patch
M present/js/play.js View 1 2 chunks +2 lines, -2 lines 0 comments Download

Messages

Total messages: 3
cespare
Hello golang-dev@googlegroups.com (cc: adg@golang.org), I'd like you to review this change to https://code.google.com/p/go.talks/
12 years, 10 months ago (2013-03-20 00:40:50 UTC) #1
adg
*** Submitted as https://code.google.com/p/go/source/detail?r=6ccd835b48d9&repo=talks *** go.talks/present: make js use correct websocket address This makes the ...
12 years, 9 months ago (2013-03-21 05:45:14 UTC) #2
adg
12 years, 9 months ago (2013-03-21 05:45:15 UTC) #3
LGTM

I'm sure I fixed this before. Weird.




On 19 March 2013 17:40, <cespare@gmail.com> wrote:

> Reviewers: golang-dev1,
>
> Message:
> Hello golang-dev@googlegroups.com (cc: adg@golang.org),
>
> I'd like you to review this change to
> https://code.google.com/p/go.**talks/<https://code.google.com/p/go.talks/>
>
>
> Description:
>       go.talks/present: make js use correct websocket address
>
> This makes the client connect to the host from which it's being served,
> rather than being hardcoded to localhost:3999.
>
> Right now, if you try to run with -http set to any port other than
> 3999, you'll get websocket closed as soon as you open the presentation.
>
> Please review this at
https://codereview.appspot.**com/7829046/<https://codereview.appspot.com/7829...
>
> Affected files:
>   M present/js/play.js
>
>
> Index: present/js/play.js
> ==============================**==============================**=======
> --- a/present/js/play.js
> +++ b/present/js/play.js
> @@ -40,7 +40,7 @@
>          stopFunc();
>        }
>      }
> -
> +
>      function onRun() {
>        onKill();
>        outpre.innerHTML = "";
> @@ -97,7 +97,7 @@
>    }
>    if (play.length > 0) {
>      if (window.connectPlayground) {
> -      runFunc = window.connectPlayground("ws:/**/localhost:3999/socket");
> +      runFunc = window.connectPlayground("ws:/**/" +
> window.location.host + "/socket");
>      } else {
>        // If this message is logged,
>        // we have neglected to include socket.js or playground.js.
>
>
>
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b