this PR to avoid the dynamic attribution of port by net.createServer() but rather by a range specified on the server command line. An internal pool is maintained to distribute ports
this PR to avoid the dynamic attribution of port by `net.createServer()` but rather by a range specified on the server command line. An internal pool is maintained to distribute ports
I don't actively work on this project anymore. @TheBoroer does some upkeep so its up to him.
so please say int on front readme to avoid people thinking this project is not dead anymore....
>
>
> I don't actively work on this project anymore. @TheBoroer does some upkeep so its up to him.
so please say int on front readme to avoid people thinking this project is not dead anymore....
Sorry I've been mia, imma check this out early next week. If its good to go, I'll ping @defunctzombie to give me access to merge it in and push a new version to npm
Sorry I've been mia, imma check this out early next week. If its good to go, I'll ping @defunctzombie to give me access to merge it in and push a new version to npm
I'm using this on my server and something unique happened. I can't say how to recreate this because I'm not able to reproduce myself, but sometimes one URL gives me another client. Let's say I have client1 and client2; sometimes, when I access client1 I'm actually accessing client2, and only normalizes when I restart the server and make the connection again. Do you think this port manager may be the cause?
I'm using this on my server and something unique happened. I can't say how to recreate this because I'm not able to reproduce myself, but sometimes one URL gives me another client. Let's say I have client1 and client2; sometimes, when I access client1 I'm actually accessing client2, and only normalizes when I restart the server and make the connection again. Do you think this port manager may be the cause?
You are not authorized to merge this pull request.
This pull request can be merged automatically.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
this PR to avoid the dynamic attribution of port by
net.createServer()but rather by a range specified on the server command line. An internal pool is maintained to distribute portshi @defunctzombie Merging this will be amazing!
@defunctzombie could you please merge this one? We can configure firewall after that
#143
I don't actively work on this project anymore. @theboroer does some upkeep so its up to him.
this is very important
so please say int on front readme to avoid people thinking this project is not dead anymore....
Looks pretty good.
Sorry I've been mia, imma check this out early next week. If its good to go, I'll ping @defunctzombie to give me access to merge it in and push a new version to npm
Hope to see this feature in soon, it would save from opening a huge amount of ports in the firewall
I'm using this on my server and something unique happened. I can't say how to recreate this because I'm not able to reproduce myself, but sometimes one URL gives me another client. Let's say I have client1 and client2; sometimes, when I access client1 I'm actually accessing client2, and only normalizes when I restart the server and make the connection again. Do you think this port manager may be the cause?
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.