[nodejs] Re: Run different version of node.js servers

+1 for n. awesome tool. On Jun 9, 8:45 am, darren wrote: > n is a great little node version manager and easy to type! > > On Jun 8, 3:58 am, Charles Moulliard > wrote: > > > > > > > > > Hi, > > > Is it possible to deploy different versions of node.js (0.6.x, 0.7.x) > > servers on a machine and t

Re: [nodejs] Re: Katana - MVC/HMVC framework for any Node.js samurai.

Sweet! Thanks! On Sat, Jun 9, 2012 at 8:25 PM, Shogun wrote: > Hi EllisGL, sorry for the late response. > > So i updated readme with this https://github.com/Shogun147/Katana#sessionsand > pushed few updates. Hopes this will be enough for now, but ask if > something is not clear. > > Also this d

[nodejs] Re: Katana - MVC/HMVC framework for any Node.js samurai.

Hi EllisGL, sorry for the late response. So i updated readme with this https://github.com/Shogun147/Katana#sessions and pushed few updates. Hopes this will be enough for now, but ask if something is not clear. Also this days i'll end write a todo application which use auth module and mongoose.

Re: [nodejs] Re: full hostname

On Jun 9, 2012, at 13:35, Ben Noordhuis wrote: > Slightly OT, but it's not always a good idea to trust the value of the > Host header. It's a frequent source of 'confused deputy'-style > attacks. In a world where there are not enough available IPv4 addresses for every web site to have its own,

Re: [nodejs] Microsoft Driver for Node.JS for SQL Server

This is awesome! ms-sql server is probably my favorite rdbms. t-sql is very powerful ( http://en.wikipedia.org/wiki/Transact-SQL ) In the past, I've had a lot of success using stuff like: Common Table Expressions (CTEs) : http://msdn.microsoft.com/en-us/library/ms190766(v=sql.105).aspx Rec

RE: [nodejs] Re: Microsoft Driver for Node.JS for SQL Server

Jonathan, as your fellow co-worker this awesome to see. Thank you guys for doing this! Sent from my Windows Phone -- From: Jonathan Guerin Sent: 6/9/2012 10:40 AM To: nodejs@googlegroups.com Subject: RE: [nodejs] Re: Microsoft Driver for Node.JS for SQL Server Don’

Re: [nodejs] Re: full hostname

> The simplest option is to usually set the expected host name in a > config file or something that your app loads And is usual a good option. I know of "solutions" that take the hostname resolve this forward into an IP and make a reverse-DNS lookup on that to get a full qualified name. I say as s

Re: [nodejs] Re: full hostname

On Sat, Jun 9, 2012 at 8:18 PM, Isaac Schlueter wrote: > The simplest option is to usually set the expected host name in a > config file or something that your app loads, or just look at > req.headers.host. Slightly OT, but it's not always a good idea to trust the value of the Host header. It's a

Re: [nodejs] TLS - EPIPE error without close event being emitted

I had some problems with this in Haraka recently. Turns out I needed to check if the actual TLS socket was writable before attempting a write. This is the relevant commit in case it helps: https://github.com/baudehlo/Haraka/commit/8aafb8d170e97a2979b7e1a7d8434ab5909d9bca The key part is outbound

Re: [nodejs] Re: full hostname

The simplest option is to usually set the expected host name in a config file or something that your app loads, or just look at req.headers.host. I mean, at *some* point you know what it is, right? Just put that in a file or environment variable (or for very fancy cases, like a host-header routin

RE: [nodejs] Re: Microsoft Driver for Node.JS for SQL Server

Don't forget that we also have a Linux ODBC driver... ;) http://www.microsoft.com/en-us/download/details.aspx?id=28160 Cheers, Jonathan From: nodejs@googlegroups.com [mailto:nodejs@googlegroups.com] On Behalf Of Graeme Foster Sent: Saturday, June 09, 2012 8:34 AM To: nodejs@googlegroups.com Sub

[nodejs] [Off-Topic] Doksbin: NodeJS powered Pastebin Service

Hi Guyes, This seems like Off-Topic for someone. So I tagged it. I was impressed with Bandit Algo and wanted to test it out. So I built a simple paste service for Documents. (named as Doksbin) http://doksbin.com

Re: [nodejs] Re: TLS - EPIPE error without close event being emitted

It is defined above in a var statement. Sent from my iPhone On Jun 9, 2012, at 11:52 AM, Ben Noordhuis wrote: > On Sat, Jun 9, 2012 at 6:47 AM, catshow wrote: >> This is what I use to connect via TLS. According to the >> documentation "tls.connect() returns a CleartextStream object." >> >>

[nodejs] Re: { [Error: socket hang up] code: 'ECONNRESET' }

Why are you using 302 ? On Jun 9, 2:19 am, degreane wrote: > > var AdyRequestHandler = function(req,res){ > .. >         var FwReq = http.get(myheaders,function(FwRes){ >                 res.writeHead(302,FwRes['headers']); >                 FwRes.on('data',function(chunk){ >                

Re: [nodejs] Re: TLS - EPIPE error without close event being emitted

On Sat, Jun 9, 2012 at 6:47 AM, catshow wrote: > This is what I use to connect via TLS.   According to the > documentation "tls.connect() returns a CleartextStream object." > >    const tlsOptions = { >        "cert":fs.readFileSync(config.certFile), >        "key":fs.readFileSync(config.keyFile),

Re: [nodejs] Re: Microsoft Driver for Node.JS for SQL Server

That's excellent news and will definitely make SQL Server more attractive to some. I was a bit worried when I saw it's based on the native Windows driver :) -- Graeme Foster On 9 June 2012 16:15, Jonathan Guerin wrote: > Linux support is on our roadmap. :) This is just a very early preview > so

[nodejs] Re: [ANN] UtahJS Conf 2012 Video on Flow-Control.

A good set of slides. One quibble is that, to be fair to "De-nested Callbacks/Ladder of Doom", you should take advantage of function hoisting and list the functions and calls in the order they execute. On Friday, June 8, 2012 2:15:45 PM UTC-4, CoolAJ86 wrote: > > Flow-Control > Love it. Hate i

[nodejs] Re: Microsoft Driver for Node.JS for SQL Server

Linux support is on our roadmap. :) This is just a very early preview so we can get feedback about our API from you guys! :) On Jun 9, 3:26 am, Sapardee wrote: > It's just running on windows, not linux platform yet. Hopefully Ms will > support mssql driver for linux. > On Jun 9, 2012 2:16 PM, "dv

Re: [nodejs] uncaught exception does not kill forked processes

I'm spawning child processes using .fork(). I think the problem occurs when a forked process has a database connection open when the parent dies, I'll try to make a few tests. On Friday, June 8, 2012 9:10:16 PM UTC-3, Ben Noordhuis wrote: > > On Fri, Jun 8, 2012 at 9:41 PM, Rambo wrote: > > Do

Re: [nodejs] Microsoft Driver for Node.JS for SQL Server

It's just running on windows, not linux platform yet. Hopefully Ms will support mssql driver for linux. On Jun 9, 2012 2:16 PM, "dvbportal" wrote: > Awesome, I like the new way Microsoft is going. > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/w

[nodejs] { [Error: socket hang up] code: 'ECONNRESET' }

Good Day Sirs. i have an issue while using node js to just proxy a GET request through node JS and it hangs giving the following issue Error 4 { [Error: socket hang up] code: 'ECONNRESET' } i have tried different methods but still the same all that the code does is just remove the range request f

[nodejs] Microsoft Driver for Node.JS for SQL Server

Awesome, I like the new way Microsoft is going. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send ema