Well, in that case, I would say it looks like a memory leak or something.
You say the socket should close in two minutes - are you leaving some
closures there too? Maybe those get piled up and then afterwards they only
accept new requests when old ones expire.
Did you count how many requests
I would like to present a microframework in Node.js called Elet which was
inspired by CakePHP framework. It helps in building web applications
simpler and require less code.
Please check: https://github.com/justin-john/elet
Nice!
First suggestions, questions:
- Maybe fs.readFileSync in view.js engine method is something to be cached,
or replaced by async call (yes, I know, it could imply that engine method
becomes async... no free lunch ;-) I would prefer file content caching, and
watch file system changes. Or
Had a quick look. Why would I use this over express?
On 9 Aug 2015 16:55, Justin John justinjohnmath...@gmail.com wrote:
I would like to present a microframework in Node.js called Elet which was
inspired by CakePHP framework. It helps in building web applications
simpler and require less code.
After adding express-validator, the app slows down dramatically: why is
that?
// mongoose config
require('./database');
var express = require('express');
var path = require('path');
var favicon = require('serve-favicon');
var logger = require('morgan');
var cookieParser =
Hi moacir, is there any socket process not completed to execute? Maybe it
can make your server not responding because main program wait the response
from socket.
On Aug 9, 2015 10:55 PM, zladuric zladu...@gmail.com wrote:
Well, in that case, I would say it looks like a memory leak or something.
