Lloyd Hilaiel
Lloyd Hilaiel
this is a great idea.
decisive. good.
Yeah, I do use orderly occasionally. I integrated into the first version of node-convict. I think it's still useful for documentation, or interface specification and validation in non-javascript environments. But...
@benadida writes: Well, it might be a bit _too_ paternalistic to prescribe a CSRF parameter _name_, since sites might be using one already and different frameworks have different names for...
it looks like this is an upstream bug? https://github.com/joyent/node/issues/3863
I _believe_ it's safe to remove this flag for gcc 3.4.6, because I believe it's disabling an optimization that did not exist in that compiler version. I'd accept a patch...
+1. As it stands now, client code must clumsily work around it at a higher level, something like: ``` server.use(express.cookieParser()); var cookieSessionMiddleware = sessions({ secret: COOKIE_SECRET, session_key: COOKIE_KEY, path: '/'...
We're now using benadida/node-client-sessions - fwiw --lloyd On May 31, 2012, at 1:41 AM, Jason [email protected] wrote: > +1 > > Is this project still being worked on? Any better...
source: https://github.com/benadida/node-client-sessions in npm: http://search.npmjs.org/#/client-sessions
the more cool sh*t you build into this, the more it almost feels like yak shaving a bit and breaking out the commonality between ircloggr and teamstatus into a framework...