We integrate node to run on IIS using a server is the proxy pattern. IIS takes the request and then uses HTTP over named pipes to communicate to the node.js instance.
Sent from my Windows Phone From: Tim Caswell Sent: 2/1/2012 6:53 AM To: [email protected] Subject: Re: [nodejs] NodeJS with Apache There is nothing wrong with mixing severs as long as you're aware of the tradeoffs. One easy way to integrate a node server in a system is to have the browser connect to the node server on a custom port using long polling jsonp. The PHP, rails, or other system can post messages to the node server using an internal port (remember, not all ports have to listen on "0.0.0.0") and then node server can then relay the messages to the clients. If you want to go same domain, then it's a little trickier, but can be done. Either use a good proxy that supports lots of long-held connections (there is one implemented in node) or have your node server be the proxy itself. On Tue, Jan 31, 2012 at 10:22 PM, Robert Steckroth <[email protected]> wrote: > As a general rule, PHP with JavaScript is bad design. NodeJs brings the > development power to a CMS of a server. There shouldn't > be any front-end PHP muddying those waters. Also, Python is poised > to incorporate NodeJs, if any dare to try. All and all, this is a > JavaScript thing with Scripting for added functionality. > > > > On Tue, Jan 31, 2012 at 10:28 PM, Jon Morehouse <[email protected]> > wrote: >> >> I understand that apache would bottleneck the node.js and vice versa >> (Where applicable). What if I Loaded the main part of my site using LAMP >> with my php. I would then log in, load most of the files etc. Then, I would >> like my "news feed" like function to be its own node server. So it would be >> dynamically loaded in my php, by using an iframe? >> >> Would it be possible to take login credentials with php and then send >> information about the user to node for updating? My "newsfeed" section would >> be dynamic and ajax heavy and would be bottlenecked by the php at extremely >> high usage rates. >> >> >> >> >> Jon Morehouse >> Moeller High School Class of 2009 >> Pepperdine University 2009-2010 >> University of Southern California Class of 2013 >> >> >> >> >> On Jan 31, 2012, at 4:45 PM, Philipp Klose wrote: >> >> As long as you are not using socket.io you could use mod_proxy to use >> node.js behind Apache. But it is kind of pointless, because Apache more >> or less destroys all the advantages of node.js >> >> Am 31.01.2012 23:34, schrieb USCTrojans: >> >> Hello, >> >> >> I'm fairly new to programming and working on a large project which is >> >> currently using a lamp stack. I was just wondering if I could get some >> >> thoughts on potentially using a combination of Apache and NodeJS to >> >> deliver my site. From what I understand thus far, NodeJS is far >> >> superior to apache for working with multiple threaded ajax requests, >> >> the heart of my site. However, I would like to continue to use my php >> >> framework for more sql based stuff that is not as ajax heavy, and also >> >> to deliver my base "site". Would it be good/smart/efficient practice >> >> to put them both behind a reverse proxy like NginX and then >> >> essentially embed the NodeJS core into my php framework with an iframe >> >> or something else? Would it be possible to pass variables like logged >> >> in information between the two systems? >> >> >> Thanks for any help, I'm excited to start working with NodeJS >> >> >> >> -- >> 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 email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> >> -- >> 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 email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en > > > > > -- > Bust0ut Surgemcgee --- > BudTVNetwork.com > RadioWeedShow.com > PBDefence.com > "Bringing entertainment to Unix" > "Finding the exit without looking" > > -- > 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 email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
