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.

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

Add support for connecting via Windows named pipes #343

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add support for connecting via Windows named pipes #343

wants to merge 1 commit into from

Conversation

HCanber
Copy link

@HCanber HCanber commented Nov 18, 2015

When hosting Sinopia on Windows' IIS using iisnode, iisnode provides the available port as a Windows named pipe and not as a port number. Node can open these, however the parse_address() function in utils.js does not allow them.

This PR fixes that.

Named pipes

A named pipe in Windows has the format:
\\.\pipe\PipeName

  • The period specifies the local computer
  • The pipe name string specified by PipeName can include any character
    other than a backslash, including numbers and special characters.

From: https://msdn.microsoft.com/en-us/library/windows/desktop/aa365783(v=vs.85).aspx

How to use it in iisnode

It can be used in iisnode by creating a project, npm install sinopia and then create index.js:

process.argv.push('--listen', process.env.PORT || '4873')
require('./node_modules/sinopia/lib/cli')

Configure iisnode to use index.js as start file.

When hosting Sinopia on Windows' IIS using iisnode, iisnode provides
the available port as a Windows named pipe. Node supports these, however
the parse_address() function in utils.js does not.

A named pipe in Windows has the format:
\\.\pipe\PipeName

The period specifies the local computer
The pipe name string specified by PipeName can include any character
other than a backslash, including numbers and special characters.
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365783(v=vs.85).aspx
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant