On Fri, Mar 3, 2017 at 8:57 PM, Tony Mobily wrote:
>
>
>
>> That's my case, the proxy we use is a custom built node http proxy based
>> solution that does not use keep-alive on the backend requests.
>>
>
> That's interesting. How come you built your own?
>
We needed business
Tony,
A proxy, in general terms, consists of a server socket and a http client,
it's basic operation is to handle incoming requests to its server socket by
issuing http requests to a backend using the http client. Keeping that in
mind the keep-alive parameter applies to the http request that
.
>
> I was half way through doing this, when I read this:
>
> https://github.com/nodejs/node/issues/2642
>
> How do you deal with keepalive connections? They can potentially stay up
> forever (if they ping often enough) even after close() has been issued...
>
That's an interesting issue and
Tony,
We have pretty much the same solution you described implemented in our app,
except for the 10s timeout, and it works very well.
You don't have to do anything special to check the event loop, if you call
the close method on all your active servers the process will end when all
connections
I increased the number of ephimeral ports on the client before running it.
In any case I don't think that is the issue, becasue when I run the same
nodejs server process (on a different port), the two processes are able to
handle 32K concurrent connections each (64K total).
Thanks for your help.
I came across this code (in a Joyent repository) and was wondering if
someone can explain the purpose or benefit of declaring exports this way.
Thank you.
module.exports = {
get Amon() {
return require('./amon');
},
get CA() {
return require('./ca');
},
get
I see. This is code for a command tool, it makes sense. Thank you.
On Thursday, February 21, 2013 1:28:39 PM UTC-3, Bradley Meck wrote:
Loading in modules can be time consuming for one off apps or resource
constrained apps. This only requires them when they are being requested.
For long
Don't forget to specify an agent of explicitly set agent = false. If you
don't the global agent will be used and your certificate will be ignored.
There's a note about that behavior in
http://nodejs.org/api/https.html#https_https_request_options_callback but I
recently overlooked that and it took
Ok, i ll try it today!
Bernardo Rosmaninho
2012/5/31 Shogun shogun...@gmail.com
I updated executable, so now the workflow is:
...
$ npm install -g katana
$ katana create app
$ cd app
$ npm install
$ node app
...
Please note that for the moment Katana is a little unstable
Shogun, I'm getting this error:
bernardo@eniac ~/Projetos $ katana create app
Create application at: /home/bernardo/Projetos/app/ ? [Yes|No]: y
Done!
bernardo@eniac ~/Projetos $ cd app/
*bernardo@eniac ~/Projetos/app $ node app*
*
*
*module.js:337*
*throw new Error(Cannot find module
10 matches
Mail list logo