Support for Named Pipes connectivity
Open
Nobody has claimed this yet.
enhancement
package:socket.io-client
- Dominant language
- TypeScript
- Stars
- 63.2k
- Forks
- 10.3k
- Avg merge
- 11d 20h
- Merged PRs (30d)
- 2
Description
You want to:
- [] report a bug
- request a feature
Current behaviour
I could not find a way to make a client to server connection using a named pipe. It should be possible to establish such a connection:
new io( "\\\\.\\pipe\\pipename" )
Or something equivalent.
Setup
- OS: Azure Web App (Windows)
- browser: ---
- socket.io version: 1.7.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Socket.IO's current client and server connection APIs and how transport options are implemented. Use the requested new io("\\\\.\\pipe\\pipename") form as the behavioral reference; done means a client can establish a connection through a named pipe on a Windows Azure Web App.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100