This repository has been archived by the owner on Mar 8, 2022. It is now read-only.
Added support for binding the socket to address and port #68
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default behavior is to bind the socket to all interfaces on a
random port. On a multi-homed node it sometimes is preferred if
the socket was only bound to a specific address.
The underlying dgram socket from node has the necessary support for
binding to an address, if that address is specified while binding.
Added options to new Session(options)
sourceAddress: The IP address to bind the socket to, and where
requests are coming from. Must be an IP address on the node, if
specified. Default is to bind to all interfaces.
sourcePort: The UDP port number to bind the socket to, and where
requests are coming from. Default: 0 (random).