Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Permit non-numeric port number in websocket-server #34

Merged
merged 1 commit into from

2 participants

@legoscia

This makes it possible to specify t for port, and let the system pick a
free listening port.

@legoscia legoscia Permit non-numeric port number in websocket-server
This makes it possible to specify t for port, and let the system pick a
free listening port.
97b7418
@ahyatt
Owner

Thanks for thinking of this change. But I'd like to understand how would the calling code know what port was chosen.

The caller would call process-contact on the return value of websocket-server to get the port number.

@ahyatt ahyatt merged commit 9fec6e2 into ahyatt:master
@legoscia legoscia deleted the legoscia:permit-non-numeric-port branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Dec 28, 2013
  1. @legoscia

    Permit non-numeric port number in websocket-server

    legoscia authored
    This makes it possible to specify t for port, and let the system pick a
    free listening port.
This page is out of date. Refresh to see the latest.
Showing with 1 addition and 1 deletion.
  1. +1 −1  websocket.el
View
2  websocket.el
@@ -794,7 +794,7 @@ in the websocket client function `websocket-open'. Returns the
connection, which should be kept in order to pass to
`websocket-server-close'."
(let* ((conn (make-network-process
- :name (format "websocket server on port %d" port)
+ :name (format "websocket server on port %s" port)
:server t
:family 'ipv4
:filter 'websocket-server-filter
Something went wrong with that request. Please try again.