Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Move the "pub serve" WebSocket API to the web interface port #16957

Closed
nex3 opened this issue Feb 19, 2014 · 4 comments
Closed

Move the "pub serve" WebSocket API to the web interface port #16957

nex3 opened this issue Feb 19, 2014 · 4 comments
Assignees
@munificent
Labels
type-enhancement A request for a change that isn't a bug

Comments

@nex3
Copy link
Member

nex3 commented Feb 19, 2014

Currently "pub serve" exposes the same WebSocket API on each of its server ports. Once we have a web interface, it should use only that port.
@munificent
Copy link
Member

Set owner to @munificent.
Added Started label.

@munificent
Copy link
Member

Unmarked this as being blocked by #16954.

@munificent
Copy link
Member

The Web Socket API is still available on the old ports too for now, but a new dedicated port is now available.

Added Fixed label.

This was referenced Jun 5, 2015
Closed
Closed
@DartBot
Copy link

DartBot commented Jun 5, 2015

This issue has been moved to dart-lang/pub#873.

@kevmoo kevmoo added type-enhancement A request for a change that isn't a bug and removed priority-unassigned labels Mar 1, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@munificent munificent

Labels
type-enhancement A request for a change that isn't a bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@nex3 @kevmoo @munificent @DartBot