http://blog.gmane.org/gmane.comp.lang.javascript.nodejs hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55669 <pre> On May 18, 2013, at 11:41, Alex Kocharin wrote: I don't know that. I don't know how database servers work internally. They might be multithreaded, and/or on a server with multiple CPU cores. The hard drives might be SSDs or a RAID. So they might be very able to handle multiple read requests in parallel. The normal node way seems to be to start things in parallel, up to a point. I assume the database drivers will queue requests, if you ask for too many of them to be started at one time. </pre> Ryan Schmidt 2013-05-18T21:34:09 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55668 <pre> First get it working correctly with nodejs on a separate port (like 8077 like you're already doing in the code you showed). Later, you can decide whether it's worth the effort to set up a proxy from your main web server. </pre> Ryan Schmidt 2013-05-18T21:30:31 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55667 <pre> On May 18, 2013, at 07:27, Bhupender Bindra wrote: Sorry, what? I didn't understand the question. Show us the code you're running, and tell us what's happening, and what you wanted to happen instead. </pre> Ryan Schmidt 2013-05-18T21:28:35 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55666 <pre> Cache will protect against an outage. I mean, if you was using some module before, and npmjs.org is gone, such repository would just answer with an old version of a package pretending like new versions were not published. If you are beginning to use some new package, it would fail all right, but it's better than installing couchdb and replicating... By the way, is it possible to track changes to a list of packages on npmjs.org repository? I mean something like partial replication, if I want to have an update of express.js ASAP, but if there is update to some-unknown-lib.js, I wouldn't even want to spend a traffic to know about it. I'm checking out shadow-npm, but it's 400 lines of js code and it wasn't modified in a year. Doesn't look so promising -_- And it still uses CouchDB... for some reason I think this task could be solved without any database at all (as long as we're trying to keep things simple and don't talk about heavy loading, filesystem could serve as a database). On Saturday, May 18, 2013 8:53:15 PM UTC+4, Martin Cooper wrote: </pre> Alex Kocharin 2013-05-18T17:20:49 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55665 <pre> One reason for replicating is to protect yourself against an outage of the npmjs.org registry. It doesn't happen often, but it does happen. Something like shadow-npm, for example: https://github.com/dominictarr/shadow-npm (Caveat - I haven't actually used this, I just know it's out there.) -- Martin Cooper On Tuesday, May 14, 2013 7:16:51 AM UTC+4, andy wrote: </pre> Martin Cooper 2013-05-18T16:53:15 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55664 <pre> Why do you want replication at all? I was thinking about it for myself recently, but I found out that there're lots of libraries you won't ever use. So isn't it better to write something like proxying repository server that would host your private projects, but proxy all other requests to npm central repository (with caching of course to avoid heavy load)? On Tuesday, May 14, 2013 7:16:51 AM UTC+4, andy wrote: </pre> Alex Kocharin 2013-05-18T16:45:34 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55663 <pre> and then when that's done, we find balloons (in serial) whereas it would be more efficient to begin trying to find both points and balloons at the same time (in parallel); If there's a lot of overhead involved (networking stuff), looking for them in parallel would be necessary. But if we're looking for points and baloons in the same place (say, the same filesystem or database), they will be looked for in serial anyway, n'est-ce pas? You can't really turn a harddrive to a quantum superposition state so it would do two things at once. Therefore time to read would be the same, but async.js would really increase complexity here. On Saturday, May 18, 2013 2:07:00 AM UTC+4, ryandesign wrote: </pre> Alex Kocharin 2013-05-18T16:41:04 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55662 <pre> PHP is designed to be ran under some apachy stuff and live for just one request. So it would indeed be simpler to keep a node.js server constantly polling server with php module in it with ajax requests. But if this system will ever eat a lot of resources and you would like to turn it to a long-running daemon... I'd suggest to stop there and rewrite anything to node.js (or python or erlang or go or whatever). Because there're some things that PHP will never do good. On Saturday, May 18, 2013 3:05:43 PM UTC+4, jasonl...-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org wrote: </pre> Alex Kocharin 2013-05-18T16:16:01 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55661 <pre> It's just another CMS, right? I don't know... never used those, but I suppose it'd be nice to have. On Saturday, May 18, 2013 6:30:58 PM UTC+4, Nuno Job wrote: </pre> Alex Kocharin 2013-05-18T16:06:52 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55660 <pre>Backing! Founder: Observe.it (http://observe.it) Lead Software Engineer: Nodejitsu.com (http://nodejitsu.com) Twitter: &lt; at &gt;3rdEden Github: &lt; at &gt;3rd-Eden Skype: arnoutkazemier Mobile: +31623254031 On Saturday, May 18, 2013 at 4:30 PM, Nuno Job wrote: </pre> Arnout Kazemier 2013-05-18T14:33:43 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55659 <pre>Hi guys, Ghost is an amazing project that is trying to re-invent blogging platforms. It's written in nodejs and the authors use nodejs to create content. The project is being funded in kick starter and is already fully financed. Did I mention how good the ux is? :) I personally invited Hannah to speak at LXJS about this awesome project, and really look forward to their foss release. If you like what they are doing i would invite you to help them in their kickstarter. Not only you will get perks that will only last for 10 more days you are also backing some super awesome, independent developers trying to make authoring content sooo much easier: http://www.kickstarter.com/projects/johnonolan/ghost-just-a-blogging-platform Nuno </pre> Nuno Job 2013-05-18T14:30:58 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55658 <pre>HTTP requests would likely be best because most existing PHP software is designed around the HTTP request/responce model. And yes, Node vs '...' aguments are mute when you must use existing software, especially if your working on existing production systems. </pre> jasonlestermv-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org 2013-05-18T11:05:43 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55657 <pre>TrainingScript.js is jason file. I able to find the object and i able to get id,TP_Name but we can't able to retrive plannedSessions value to insert , update and delete { id:"te", TP_Name: "Junior 18s", TP_Description: "Training plan targetted Junior 18 girls section of the club aspiring to be National champins and International representitives", plannedSessions: [ { name: "500m intervals", description: "Intensive session of 500m pieces. Full recovery between pieces. Quality important", duration: "1:30", date: "14/4/2013", time: "19:00", location: "Islandbridge, Dublin" }, { name: "1000m intervals", description: "Session of 1000m pieces. Full recovery between pieces. Quality important, Practise of race piece throughout", duration: "1:30", date: "15/4/2013", time: "19:00", location: "Islandbridge, Dublin" } ] } ________________________________________________________ jQuery.getJSON("/TrainingScript", function(data) { drawTable(data); }); </pre> Bhupender Bindra 2013-05-18T12:27:38 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55656 <pre>Thanks for your help. So, is the solution only a right configuration of proxy on my server? Can you explain in better way what I do? Il giorno venerdì 17 maggio 2013 14:31:41 UTC+2, Dandi ha scritto: </pre> Dandi 2013-05-18T09:39:45 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55655 <pre> This line doesn't *call* anything; it *defines* that *when* a user requests "/" from your server, the server will invoke a request handler function called activityList.showActivities. When activityList.showActivities is invoked, it uses mongoose to find all data in the "point" collection, and when the results are received, calls res.render() to fill the indicated Jade template with the supplied variables and sends the resulting HTML to the browser. The res.render() invocation above uses the template "index2" not "index". And here you're iterating over a variable called "activities", which your res.render() invocation did not supply; you supplied a variable called "points", so that's what you would be iterating over in the template. Instead of just calling find() on the point collection, you'll also call find on additional collections. Here's an example of finding all points and all balloons: showActivities: function(req, res) { point.find({}, function foundPoints(err, points) { balloon.find({}, function foundBalloons(err, balloons) { res.render('index2',{title: 'CapCredits' , points: points, balloons: balloons}) }); }); }, Note that this is *not* the best way to do it, because a) we find points, and then when that's done, we find balloons (in serial) whereas it would be more efficient to begin trying to find both points and balloons at the same time (in parallel); and b) the ever-increasing indentation is ugly and harder to follow. This is a common problem in nodejs for which there are an unlimited number of npm modules that can help you structure your code better. "async" is a very popular module for this. That line would define that when a user requests "/otherMenu" from your server, the server would invoke the same activityList.showActivities function you've defined above. That's probably not useful. I don't see how REST enters into what you're trying to do at all. The term "REST" is often used when talking about web services, but what you've described above is not a web service; it's a web server producing a normal HTML web site. Users will make one HTTP request to your server (for "/" for example) and will receive a formatted HTML response containing all sorts of information from various database collections that your server has assembled. If you want a web service, and want, for example, that "/otherMenu" returns *just* the items of some database collection, perhaps in JSON format that you'll access via AJAX and turn into DOM elements on the fly in some client-side JavaScript, you can do that, but that's not what you were talking about above. </pre> Ryan Schmidt 2013-05-17T22:07:00 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55654 <pre>2013.05.17, Version 0.10.7 (Stable) * uv: upgrade to v0.10.7 * npm: Upgrade to 1.2.21 * crypto: Don't ignore verify encoding argument (isaacs) * buffer, crypto: fix default encoding regression (Ben Noordhuis) * timers: fix setInterval() assert (Ben Noordhuis) Source Code: http://nodejs.org/dist/v0.10.7/node-v0.10.7.tar.gz Macintosh Installer (Universal): http://nodejs.org/dist/v0.10.7/node-v0.10.7.pkg Windows Installer: http://nodejs.org/dist/v0.10.7/node-v0.10.7-x86.msi Windows x64 Installer: http://nodejs.org/dist/v0.10.7/x64/node-v0.10.7-x64.msi Windows x64 Files: http://nodejs.org/dist/v0.10.7/x64/ Linux 32-bit Binary: http://nodejs.org/dist/v0.10.7/node-v0.10.7-linux-x86.tar.gz Linux 64-bit Binary: http://nodejs.org/dist/v0.10.7/node-v0.10.7-linux-x64.tar.gz Solaris 32-bit Binary: http://nodejs.org/dist/v0.10.7/node-v0.10.7-sunos-x86.tar.gz Solaris 64-bit Binary: http://nodejs.org/dist/v0.10.7/node-v0.10.7-sunos-x64.tar.gz Other release files: http://nodejs.org/dist/v0.10.7/ Website: http://nodejs.org/docs/v0.10.7/ Documentation: http://nodejs.org/docs/v0.10.7/api/ Shasums: ``` 95d64001ccd5a17c2c25f1ae4b0358b6131e7cb8 node-v0.10.7-darwin-x64.tar.gz c34f991cc0752679002f763b2b3c8927babb08d8 node-v0.10.7-darwin-x86.tar.gz 673c287bcf671eced6aa94637b7c91e5149f4c56 node-v0.10.7-linux-x64.tar.gz 9f14d4f9add721148f0c15f093d3e6b1fa3820c9 node-v0.10.7-linux-x86.tar.gz 1fb7dc4195a9dd228039f5f7ca2cb9f7c35b105a node-v0.10.7-sunos-x64.tar.gz d84cd8afb50df44483b9dab0c65d5c81f07ac4a2 node-v0.10.7-sunos-x86.tar.gz d7794a7da103d639fdec4b9e7236a5a0a4330297 node-v0.10.7-x86.msi 0524ad9268095c9ed435708268e6aad7968309f7 node-v0.10.7.pkg f2bde505faf6ffed3084c8e550a9e6d4311f13d5 node-v0.10.7.tar.gz 5f50384766dd5435dba4989d95032452754150bf node.exe 809f12f84c8495d101ce6ae443890e8533695ab0 node.exp 5a7355e2f75ae3f72deab75f4c9f93e4e5325584 node.lib 6e45953bd7488a4236c43fea93b05da0854158a7 node.pdb fc5e3b2b1c74e53f1d214a9e2d5af30fe5247381 x64/node-v0.10.7-x64.msi aa67bbd421f26b37fa09ce30d5e626106677853e x64/node.exe b289989a156d4d7055554962e6f00ba3e380aeea x64/node.exp 0dbecc5007c9e28ad488d2058157f8360eaed958 x64/node.lib e4b63472787a3db6a3d85237e8c7fb4d973f797b x64/node.pdb ``` </pre> Isaac Schlueter 2013-05-17T21:38:44 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55653 <pre> [snip] If this is what you want -- for CakePHP to deal with most of the site, and for nodejs to be used for just one part of the URL space on that same host and port -- then you'll have to configure your web server (Apache? Nginx?) to *proxy* requests for those URLs to nodejs. You don't need any "nodejs" folder in CakePHP because CakePHP has nothing to do with what the web server does to proxy those requests. The only reason to go to all that trouble is if you need to publish any nodejs-specific URLs and you want the URLs to remain pretty and look like they're all part of a single service. But if you only need to access nodejs through AJAX then it doesn't matter what the URLs look like. A simpler configuration would be to leave CakePHP handling all of your URLs on your main hostname and port, and start the nodejs server on a separate port and/or IP address and talk to it that way. The rest of the code you show below is already doing this. Here, for example, you show that you're wanting to directly access the nodejs server at its port 8077 (while CakePHP remains on port 80 presumably through Apache or Nginx or similar web server). Also, there appears to be a typo in the URL. You probably meant "?callback=something". It looks to me like this should work: it should create an http server on port 8077 responding to the hostname 192.aaa.bbb.ccc and delivering the "Hello World!" response to any requested URL. It may be simpler if you omit the hostname; then it'll respond to any hostname on that port number. That should not be. That suggests that the nodejs server is in fact running on port 80. Unless you've already configured some sort of proxy from your primary web server, but your message made no mention of that. </pre> Ryan Schmidt 2013-05-17T21:35:01 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55652 <pre>Looks like v0.10.7 hasn't dropped yet. In the meantime, here's what’s new in Node.js and libuv this Week - May 17. Including crypto string performance, debugger for clustered apps &amp; round robin load balancing. Check it: http://blog.strongloop.com/whats-new-in-node-js-and-libuv-this-week-may-17-2013/ Jimmy Guerrero Community Dude StrongLoop </pre> Jimmy Guerrero 2013-05-17T19:35:02 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55651 <pre>in Express 3 you can do it as: req.header("custom-header") req.get("custom-header") and also since express request is a node IncomingMessage you can use: req.headers["custom-header"] Please check the "*subtle"* differences, - all three examples uses "REQUEST" not response as in one of your examples. - the first two examples are functions but the last on is an object hope this help. 2013/5/17 greelgorke &lt;greelgorke-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; </pre> José F. Romaniello 2013-05-17T18:38:20 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55650 <pre>ajax calls are simple http requests, the only difference between ajax and non-ajax is how the browser react on response. Am Freitag, 17. Mai 2013 11:27:14 UTC+2 schrieb Srividhya: </pre> greelgorke 2013-05-17T18:28:26 http://permalink.gmane.org/gmane.comp.lang.javascript.nodejs/55649 <pre>I would try mikeal's replicate: https://github.com/mikeal/replicate </pre> DTrejo 2013-05-17T17:02:35 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lang.javascript.nodejs