Hi All
We are looking for Senior UI Developer based at Hyderabad Location, Kindly
share us the profiles on dchan...@globalsena.com or reach me at 9704712034
Regards
Dinesh Chandra
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Po
hi all, im new with nodejs and i have little problem, when i type node s.js
it not runs and showing dots (...) but when i type .load s.js it runs. how
can i use node s.js?
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Gui
The cluster module seems pretty good from my experiments thus far.
:-)
On Thursday, December 19, 2013 9:50:03 AM UTC-7, Bijuv V wrote:
>
> Hi ,
>
> I have a Web server with an Application developed using express. In the
> application we do mention the port at which the application should listen
If you are running on Windows, check out
http://tomasz.janczuk.org/2013/05/how-to-save-5-million-running-nodejs.html
On Windows, you have the option of using the httpsys module
(https://github.com/tjanczuk/httpsys) to replace Node's HTTP stack with the
kernel mode HTTP.SYS implementation Window
You're going to need to post some code, or a gist with some code, because
there's a number of things that could be going wrong. Persistent references
to things that you don't want to be garbage collected are usually
important, even for Functions.
Your best bet at solving something like this is
Hi Chris, Actually, you can submit a whitelist there. It should follow the same semantics as .gitignore, and gitignore fully supports whitelisting like that: ```*!something!foo.*``` It's just rarely seen because it's a maintenance burden. 20.12.2013, 05:20, "Chris Winberry" :Hey, htmlparser autho
No worries. Thanks for the explanation! I'm still learning and it's all
good. Thank you for your contribution and feedback; I'll know to watch my
own source folders in the future too.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-Lis
Hey, htmlparser author here. I got concerned when I heard something
malicious might have made its way into the package.
No malice but I will cop to stupidity. A while back (2 years now? wow) I
made a quick fix and did not realize I had some vestiges of test data while
working on a rewrite. That
Cleared by npm cache and uninstalled/re-installed nodejs just to double
check (in case it's my Mac that's infected). Still showing up using npm.
Yet it's not in git nor online source browsing. Filed with htmlparser
author. I know it's not apart of jQuery core!
Thanks for your quick reply :-)
O
"Assume stupidity, not malice". Those two files are web bugs. Very common annoyance. I wish Firefox would've denied any scripts that do not originate from the same domain by default... People just don't know how to use .npmignore, that's all. Take a look at what "less" package contains, you'll be
Please file a bug for this http://bugs.jquery.com and probably with
https://github.com/tautologistics/node-htmlparser
Thanks
Rick
On Thu, Dec 19, 2013 at 7:13 PM, Stephen Carnam wrote:
> Noob to nodejs (but not to JavaScript). Today I needed jQuery
> functionality in a nodewebkit app I'm writi
Noob to nodejs (but not to JavaScript). Today I needed jQuery functionality
in a nodewebkit app I'm writing and so I ran "npm install jquery". However,
I noticed the following show up in Netbeans as it tracks remote
dependencies being referenced now that jQuery is present; these are
curiously n
They won't :)
Oh well :)
It's better for things to work than for everyone to agree.
-Mikeal
On Dec 19, 2013, at 3:47PM, Alex Kocharin wrote:
>
> Well okay, just one silly argument. How will these people know that they're
> doing the wrong thing if nothing will ever break? :)
>
>
> 20.1
On Dec 19, 2013, at 3:21PM, Alex Kocharin wrote:
> It resulted in huge node_modules folder checked in (with binary deps because
> nobody cared), they weren't updated at all (and were outdated for like a
> year).
this just requires some diligence and using dedupe often.
> And the worst thing
Well okay, just one silly argument. How will these people know that they're doing the wrong thing if nothing will ever break? :) 20.12.2013, 03:42, "Mikeal Rogers" :First off, if someone version locks they are already doing the wrong thing. Saying "make my package ignore bugfix releases" is almos
First off, if someone version locks they are already doing the wrong thing.
Saying "make my package ignore bugfix releases" is almost always the wrong
thing. In this case it's better to keep their package working for them since
they clearly don't know what they're doing.
If they **really** didn
I was dealing with checked in dependencies in some private project with a few people who don't seem to be familiar with node very much. It resulted in huge node_modules folder checked in (with binary deps because nobody cared), they weren't updated at all (and were outdated for like a year). And t
Suppose somebody made a conscious choice to rely on your package version 1.2.3. If they wanted to receive updates, they would've specify ~1.2.3, and receive your 1.2.4 with a bugfix. But they don't even though npm specify "~" syntax by default. Why do you suggest to replace 1.2.3 (if it's broken o
I completely agree that checking in dependencies is currently a sensible
and pragmatic option for those concerned with consistency or security, but
I disagree with anyone that thinks that we shouldn't be setting our sights
a bit higher.
I don't want anyone to take this as a criticism, I've got imm
In the real world it's just better to have your dependents not fail to install,
you can't actually rely on the maintainers doing another publish after you
break them. In the end, the less packages that fail to install from npm the
better and whatever solution results in the least number of un-in
Why is it a bad thing? If someone wants to receive your update, he'll specify a version range and an update will be installed automatically. If someone want to rely specifically on broken version and locked it, they kinda asked for it. Well yeah, unpublishing is bad except for very few cases where
Nobody wants to break all of the things.
Unpublish need only be used in extreme cases, where sensitive data is
exposed, copyright problems, malware, etc... i.e. cases where, sadly,
dependent projects should (or must) be allowed to break.
Even when a package is unpublished, dependent projects woul
Those are easy to exclude and so long as you `npm rebuild` on deploy they'll be
overwritten anyway.
This is used as a best practice by quite a few people, people still tweet this
article I wrote out every month and I wrote it's more than 2 years old.
http://www.futurealoof.com/posts/nodemodules
That’s a terrible idea. The simplest reason it’s a terrible idea is that
binaries built for one platform will be checked in. ie developing on OS X and
deploying on Linux.
On Dec 19, 2013, at 5:28 PM, Mikeal Rogers wrote:
> +1
>
> On Dec 18, 2013, at 12:41PM, Tim Caswell wrote:
>
>> If you
+1
On Dec 18, 2013, at 12:41PM, Tim Caswell wrote:
> If you want this level of static dependencies you can check in your deps into
> node_modules in your git tree or use git submodules in there. Git does
> guarantee that the thing you point to can't be changed because the hash *is*
> the has
That leaves all of the other packaged already published and relying on a
specific version broken.
On Dec 19, 2013, at 11:46AM, Dean Landolt wrote:
> Even in that case it would still seem better to allow unpublish and bump the
> version number, right?
>
> Immutability (plus unpublish) would ma
That sucks. Any idea what's causing it?
On 19 December 2013 20:13, Sam Roberts wrote:
> On Wed, Dec 18, 2013 at 5:42 PM, Alex Kocharin wrote:
> > So if something needs to be republished, maintainer will be
> > forced to change version number (or add a build number although it's now
> > ignored
Hi, just use HAProxy http://haproxy.1wt.eu/ (software LB).
Here https://github.com/observing/balancerbattle you can find multiple
options to scale.
On Thursday, December 19, 2013 1:50:03 PM UTC-3, Bijuv V wrote:
>
> Hi ,
>
> I have a Web server with an Application developed using express. In the
On Wed, Dec 18, 2013 at 5:42 PM, Alex Kocharin wrote:
> So if something needs to be republished, maintainer will be
> forced to change version number (or add a build number although it's now
> ignored by npm).
I've found force republish invaluable in the last weeks when publishes
to npmjs.org sil
I scaled on a single machine using haproxy and thalassa.
The gist of it:
var http = require('http')
var app = require('./app')
var pkg = require('./package.json')
var server = http.createServer()
server.on('request', app)
// Listen on port 0. This finds a random, free
pm2 is a cluster master process. You can write a master yourself, or you can use it instead, it is essentially just one option. If you like to have another option, I'd name different ports and nginx as a load balancer between them. It was what we were doing before cluster was released, and I belie
On Thu, Dec 19, 2013 at 11:50 AM, Bijuv V wrote:
> Thanks Alex.
>
> So the options finally are -
>
> a. Use Cluster - used in many prod applications as mentioned by Luke
Yeah, ignore the experimental, it means node is allowed to changes its
API, if they need to.
It's API is a bit low-level, you
+ using strong cluster control, you can add dynamically additional
processes to a running application based on workload and drop them when not
needed.
You can avoid application restarts.
So if you started with 2 processes as part of the cluster and found them
overwhelmed with load, you can automa
On Thu, Dec 19, 2013 at 2:25 AM, Richard Marr wrote:
> I agree there should be a way to recover from a botched release, but mutable
> packages cause problems that are hard or impossible to solve in other ways.
> If the reason for mutable packages is just to allow recovery from botched
> releases t
The awareness between processes is useful for work load management between
master and child. Description by Alex is mostly accurate.
We are also working on a more distributed work load management solution in
strong-cluster to allocate specific type of workloads selectively to child
processes. S
Even in that case it would still seem better to allow unpublish and bump
the version number, right?
Immutability (plus unpublish) would make the npm registery an even better
place.
On Thu, Dec 19, 2013 at 2:43 PM, Mikeal Rogers wrote:
> There have also been security issues where old packages we
Thanks Alex.
So the options finally are -
a. Use Cluster - used in many prod applications as mentioned by Luke
b. Use PM2 module - similar to cluster I believe
c. Use Phusion Passenger - Not quite sure why would I go with such a
heavyweight ? (IMO - just by reading thru their website)
d. Use V
There have also been security issues where old packages were shipped with
sensitive information that needed to be ripped out.
On Dec 18, 2013, at 5:07PM, Forrest L Norvell wrote:
> I agree that packages should rarely be changed, but in practice if there's a
> major bug or the packaging gets to
I can't say for sure what he meant there, since year 2010 was like ages ago, and a lot of stuff happened. But it's probably about passing file descriptors from master server to a child process. Only one process can listen on a port at any given time, so master does it. But once it accepts a connec
Thanks for sharing your views . Do you know what Ryan means by Server File
Descriptors?
Also , about Strongloop, you mentioned about communication between the node
instances - why would this be necessary - cant figure out a use case .
On Thu, Dec 19, 2013 at 6:28 PM, Luke Arduini wrote:
> The "
Agreed, using cluster (either using 'pm2' module or by writing your own small cluster manager) is the way to do it. 19.12.2013, 21:29, "Luke Arduini" :The "experimental" stability index means almost nothing. It's fine. Plenty of people use it in production. On Thursday, December 19, 2013, Matt wr
Hi,
You can use StrongLoop's strong-cluster module to autoscale up or down and
solve all these issues. If app is running as single process, with a single
command or through the StrongOps GUI, more processes can be added as part
of the cluster. All processes will be aware of each other and part
Often that particular message means that you've lost control flow somewhere
and have called res.end() twice on the same request.
On Tuesday, December 17, 2013 6:28:17 PM UTC-8, ming wrote:
>
> Hi,
> i've been running a node server application which crashes probably once a
> week due to an unca
The "experimental" stability index means almost nothing. It's fine. Plenty
of people use it in production.
On Thursday, December 19, 2013, Matt wrote:
>
> On Thu, Dec 19, 2013 at 11:50 AM, Bijuv V
>
> > wrote:
>
>> a. Use Cluster feature of node. Everything is handled by node. Still
>> experime
On Thu, Dec 19, 2013 at 11:50 AM, Bijuv V wrote:
> a. Use Cluster feature of node. Everything is handled by node. Still
> experimental AFAIK.
>
I think while cluster is still marked experimental, it's built on top of
child_process which is marked as Stable.
Most people go with cluster. It works
On 12/19/2013 05:50 PM, Bijuv V wrote:
> If I spawn multiple node processes on the same machine, there will be
> a conflict on the ports. How can this be achieved (apart from the
> below options)?
How about going with passenger standalone with a number of instances?
However, I've never tried it in
2013.12.18, Version 0.10.24 (Stable)
* uv: Upgrade to v0.10.21
* npm: upgrade to 1.3.21
* v8: backport fix for CVE-2013-{6639|6640}
* build: unix install node and dep library headers (Timothy J Fontaine)
* cluster, v8: fix --logfile=%p.log (Ben Noordhuis)
* module: only cache package main (Wy
Hi ,
I have a Web server with an Application developed using express. In the
application we do mention the port at which the application should listen
for requests. For eg 3000.
If I spawn multiple node processes on the same machine, there will be a
conflict on the ports. How can this be achi
I just answered this on SO. Feel free to email me or ask questions on
#haraka on freenode if you get stuck.
On Thu, Dec 19, 2013 at 6:29 AM, Chris Dew wrote:
> Does anyone have an example of a client-side TLS upgrade in a plain text
> protocol?
>
>
> http://stackoverflow.com/questions/20679906/
Hi,
I've tried a number of things, but I still get an immediate crash the first
time my callback gets called. Nothing helpful is printed out and this happens
even when the body of the callback is just
HandleScope scope; scope.Close(Undefined());
Any suggestions how I might make progress from he
A more detailed documentation on HOW the child_process ipc works would be
great..
I've tried listening on fds like unix sockets and such... I think I am
missing something somewhere - it would be nice to also be able to reopen
0,1,2, but I suppose once I figure this out that won't be so hard?
c
Alex thanks for your reply.
Can you explain me in more detail on how to do it.
On Thu, Dec 19, 2013 at 6:39 AM, Alex Kocharin wrote:
>
> Yes. Just export express.js app, and don't bind it to any port inside of
> your module. It's quite popular practice.
>
>
> 18.12.2013, 15:14, "SaR" :
>
> Hi
Thanks for the Richard,
I trying to build a app using node and express. in the webpage i want to
have header app , footer app and also content sections are in different
app.
like if i have login module as app just use that and proceed ... basically
re-use the app in order to build new one.
Will
You might also want to think about having your components communicate via a
database, file system, or message queue, as having tightly coupled
components can cause devops headaches.
A looser coupling makes deployments easier, ops tasks more standardised
(e.g. look in RabbitMQ manual, rather than d
I did notice that the IPC fd is supposed to be exported as an environment
variable to the child, but upon console.log(util.inspect(process.env)); in
the child doesn't show any NODE_* envs.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing
Does anyone have an example of a client-side TLS upgrade in a plain text
protocol?
http://stackoverflow.com/questions/20679906/implementing-starttls-in-a-protocol-in-nodejs
Thanks,
Chris.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailin
I am copy/pasting my answer from an answer someone posted on SO
This is one of the downsides of using NodeJS. It basically has two methods
on which errors are handled; One through using the try/catch blocks, and
other by passing the first argument of every callback function as an error.
I belie
On Tuesday, December 17, 2013 7:28:17 PM UTC-7, ming wrote:
>
> Hi,
> i've been running a node server application which crashes probably once a
> week due to an uncaught "Can't render headers ..." exception. The
> skeleton of the code is like:
>
> =
> var
> h
You can use the cluster module to create worker threads to do the work and
have the master manage the sockets and communication.
This also allows you to make changes to the worker code and gracefully
restart workers without completely killing the server, for example:
master:
fork 2 workers
list
Hi, first, sorry if this is an inappropriate place to ask.
I am spawning a detached child process and am able to communicate via IPC
just fine, I can shut down the master process and leave the child running.
What I need to do is restart the master and reconnect to the same IPC
channel.
I am cr
Thanks Nuno, helpful as always.
On 19 December 2013 03:18, Nuno Job wrote:
> Google "nodejs lockdown lloyd"
>
> That should be easy enough to get started
>
> Ideally modules should be signed by author and a couple more people to
> validate origin.
>
> Nodejitsu sells a private npm product, wi
Thanks Alex.
Signed packages would be a real win too. Aside from some coding, I guess
the challenge there is how to encourage everyone to jump through the
additional hoops required. The signing could be happen by default (I'm
guessing) but publishers would need to upload a public key. I guess we'd
Thanks Tim, that's definitely a strong contender in terms of keeping the
infrastructure simple in a security-conscious environment.
On 18 December 2013 20:41, Tim Caswell wrote:
> If you want this level of static dependencies you can check in your deps
> into node_modules in your git tree or us
Hi Forrest,
I agree there should be a way to recover from a botched release, but
mutable packages cause problems that are hard or impossible to solve in
other ways. If the reason for mutable packages is just to allow recovery
from botched releases then why not just increment the version? Anyone
au
First point is too vaguely defined, I'm pretty sure you can do it, but can't say exactly how, because there are countless ways for two programs to communicate. To deal with the second issue you can use this module:https://github.com/rlidwka/node-hotswap Although it hasn't been updated for years, i
On Dec 19, 2013, at 02:26, SipherHex1984 wrote:
> Currently my boss it not happy with the idea of having to restart the node
> app each time we would like to change or add to it.
Whether he’s happy with it or not, it’s what you’ll have to do. But it can be
automated. There are existing techni
Hello, First of all I am having a bit of an issue. I have been a PHP
developer for many years now. I have always seen a need for sockets in JS.
Recently I am trying to come up with a nodejs for the company I am
currently working for. What I am looking for is a way to have a single app
that list
67 matches
Mail list logo
