Re: [nodejs] Node.Js Hosting

[Jeremy Darling]

Don't know what you call expensive, but Linode's (https://welcome.linode.com
) $5 plan (or any other similar VPC) are quite affordable.

Other options from them at https://www.linode.com/pricing

I've had great luck with Linode in the past.

Other options would be Amazon, GCP (Google), Azure, etc...

Just depends on the amount of work you care to put in and how much you are
willing to spend per month.

 - Jeremy

On Mon, Apr 23, 2018 at 10:37 AM, Wayne Bruton 
wrote:

> Hi Guys,
>
> Any reliable alternatives to Heroku? Heroku is awesome but expensive.
>
> Kind Regards
>
> Wayne
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules: https://gist.github.com/othiym23/9886289#file-moderation-
> policy-md
> Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/nodejs/4600f091-503f-41bf-a66e-92304a8451fe%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7Eh%3D5hpUpwZrRLq%2BLCiDYG1F9AWrCxWCKmYeCVe199a9FA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] platform

[Jeremy Darling]

2nd response from google for exactly that question answers this best:


(from
http://stackoverflow.com/questions/35238667/is-npm-dependent-on-the-os-of-a-computer
with slight inline edits)

The binary, npm, that you install is platform dependent, as is node.js.
That's why there are different releases for each platform available on the
download site.

For the most part, your project files are platform independent. For
example, most of your JavaScript files will all be used by node.js and work
just fine without having to worry about what platform you are on because
the system details will be dealt with by node.js itself.

However, some modules *are* platform dependent. For example, anything that
uses node-gyp will try to compile on your platform whenever the module is
installed by npm. You do not have to worry about that though because it is
handled by npm, that's why you're using a package manager.

Copying node_modules can be done; but it's more often than not better and
easier to just run npm i on whatever machine is going to be running your
application. You can avoid having to worry about version problems using
something like npm shrinkwrap  which
will lock down the version of a package that your module depends on.
share improve this answer

answered Feb 6 '16 at 8:24

zero298 
3,81731938

On Mon, Mar 27, 2017 at 1:07 PM,  wrote:

> hello
>
>
> Is node.js is platform dependent or independent ?
>
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules: https://gist.github.com/othiym23/9886289#file-
> moderation-policy-md
> Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/nodejs/8f8b4285-5374-4490-9b05-7b4217cdb37a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7Ei9tRkcLVBBjL5TPFYf7byYU40TfcKGfkpeTGDEETfQyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] JAR like format for nodejs

[Jeremy Darling]

Since you can overload the way that Require works you don't actually need a
"change" to Node you can just add in your own loader, as an example here is
a very simple YAML loader:

const fs = require('fs');
const yaml = require('js-yaml');

require.extensions['.yaml'] =
require.extensions['.yml'] = (module, filename)=>{
  const content = fs.readFileSync(filename, 'utf8');
  module.exports = yaml.load(content);
};

You could do something similar with whatever and have it basically
decompress say a Zstandard archive or something.  I only suggest Zstandard
as I've seen great compression with it against extremely large JSON
structures, so would probably excel at JS as well.

On Thu, Oct 13, 2016 at 9:12 AM, Jan Flyborg  wrote:

> Hi,
>
> I am wondering if there are any plans to change the module system of
> nodejs to make it able to import modules from a single archive (much like
> Java's jar which actually is a zip in disguise).
>
> We are planning on deploying code on a space constrained device and since
> our node_module folder is very large, we are looking for ways to reduce its
> size. We can of course address this with normal minification, but if a
> jar-like archive format were available that would probably also help us a
> lot.
>
> Any thoughts on this?
>
> Cheers
> //Jan Flyborg
>
>
>
>
> --
>
> Sent from my mobile device. Please excuse my brevity.
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules: https://gist.github.com/othiym23/9886289#file-
> moderation-policy-md
> Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/nodejs/CACrfS1AcaqsM2EjicTtsJMxC3PG0wxCaE%3DDSvK4JCvCGM%2BrWVA%
> 40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7EgwZEFJZcr7rF%2B0XcS688UAxPpgP-p2goxoYgiSxvEJPA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] Why build Node from source on Linux?

[Jeremy Darling]

Personally, I prefer to install Node through NVM (
https://github.com/creationix/nvm) for development environments.  For our
stage, QA, and production environments we use the prebuilt image.

As for advantages, honestly, I can't find any unless you plan on working on
the Node codebase yourself.

On Thu, Nov 5, 2015 at 10:50 AM, JamieP  wrote:

> I want to install Node on Linux and am not sure whether to unpack the
> pre-built binary for Linux 64 or to build from source.
>
> Can anyone brief me on the drivers behind building from source on the
> target machine as opposed to just unpacking a pre-built version?
>
> cheers
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/3ef23a1e-aeeb-4a6a-96b0-535a9b2e97d2%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7EiCQjrYc76FHSBx94S4zpT%3DYKpBNqWmreiYXUcqTD5d_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] Node.js high performance says: You should not have files bigger than 5 kB

[Jeremy Darling]

Never heard that before.  Having worked on some very large Node.js projects
I can tell you that 5k is no magic number, lots of code bases, libraries,
and projects will have source files over 5k.

Really what you have to watch out for is spaghetti code that is easy to
accidentally end up with.  Solution, once you have it working, refactor it
to ensure readability and reuse.

 - Jeremy

On Mon, Aug 31, 2015 at 2:56 PM, bryan rasmussen 
wrote:

> So I'm reading the book Node.js high performance on the page where the
> subject is Seperating your code and it says:
>
> "Again, you should always split your code into smaller parts. Node.js
> helps you do this in a very easy way. You should not have files bigger than
> 5 kB. If you have, you better think about splitting it."
>
> Anyway the Again doesn't seem to refer to anything, and the Node.js helps
> you do this in a very easy way seems especially lackiing but I am still
> wondering about this stricture of you should not have files bigger than 5
> kB, why specifically this size is there anyone that can enlighten me?
> If you can enlighten me how does it apply to files that are in some MVC
> framework - if my controller is bigger than 5 kb what happens?
>
>
>
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/de723fc0-5889-4652-8c73-78ede4205d82%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7EjT7eL7Sdn95yfMHq%3DfypMEC1T7ycstDO-cROcQqaU3ww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] Checking order HTTP requests leave the connection pool?

[Jeremy Darling]

Actually, yes, there is a way to intercept the http request/response
mechanic.  This is some "working" code that I will be cleaning up at some
point, but for now it could suffice as a reference.  Of course you can also
use the precis-client-logger with the precis-file-adapter or
precis-console-adapter if you don't want to rewrite it or copy/paste it.

https://github.com/precis-logging/client-logger/blob/master/lib/http-capture.js

Really though, your GET and POST won't got out at the same time, they might
be close but they will never be exact.  Within a few 100ms would be my best
guess.

On Wed, Jul 22, 2015 at 6:29 PM, Jonathan Uesato  wrote:

> I'm trying to use Node.js to make a series (~1000) of HTTP requests which
> are duplex connections. I'm worried that my GET and POST requests are not
> being sent out at the same time, because I get intermittent errors back
> from the server.
>
> Is there a way to monitor HTTP requests as they are actually sent out? For
> example, is there some event which is emitted when they leave the
> connection pool? If it matters, I'm using the request library, though I
> imagine this shouldn't make too much of a difference.
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/fb684ffb-6586-4a84-b9eb-9b2093ab91b3%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7Ehb1BYbnMpa2BC10aMKpCZ4YC1C9OTpSi1jaC37-7TKNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] [ANN] Logger - distributed logging system

[Jeremy Darling]

Well, you could use something like (the soon to be released) Precis (
https://github.com/precis-logging/precis) project.  Built on top of a
centralized event message bus (by default it will use MongoDB capped
collections) and already being used for 100,000+ messages a second.

The event bus used by Precis can be switched out to fit your needs so you
could use RabbitMQ, Redis, etc instead of Mongo's capped collections.

I'm busy right now removing all of our custom code and open sourcing the
entire thing.  Goal is to have the first GA in the wild by end of March to
middle of April.

Disadvantage to this scale of logging is your talking about a full SOA with
many services to maintain.  Advantage is that scaling just requires
deploying new processing nodes.

Honestly Logger looks pretty snazzy and I've already added it to my list of
projects to look at as a plugin in place of or along side FluentD in Precis.

Of course there is always ELK (ick), Splunk, Octopussy, Graylog, or you
could just build it yourself if you don't like the features of what is
already available.

 - Jeremy

On Tue, Mar 10, 2015 at 9:47 PM, Aria Stewart  wrote:

>
> > On Mar 10, 2015, at 7:36 PM, Tim Dickinson 
> wrote:
> >
> > You don't. It was designed to collect hundreds if not thousands of log
> lines per second. The UDP server is made to scale. So to prevent packet
> lose just scale up the UDP server.
>
>
> Aw, sad. It's easier to scale without things if you have a protocol that
> handles retries like TCP. This way you just have to overprovision like 10x
> and hope you still don't miss any due to bursting. :(
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/B39400AF-9039-4339-9093-60C9A828BA8E%40nbtsc.org
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7Ej%3Daj47hbN7hL_dAETx5HU7xAY0Ysq%2BrzsaS68O6pENjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] book or beginners tutorial about functional programming in node

[Jeremy Darling]

You can almost always find something on the Essential JavaScript Links
repository:

https://gist.github.com/ericelliott/d576f72441fc1b27dace

>From there, maybe this will help:

   - The Two Pillars of JavaScript Part 2: Functional Programming
   



On Tue, Jan 20, 2015 at 1:20 PM, Roelof Wobben  wrote:

> Hello,
>
> I try to do the functional js workshop on nodeschool.io to learn more
> about this subject.
>
> But I noticed that I have to litle knowlegde to solve the problems.
>
> Is there a good book or tutorial so I can learn more about this subject.
>
> Roelof
>
>  --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/4420f773-1df9-4afc-b1bc-85e4f42779e5%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7EiFhma0nx_yCKsEv8Zc7F5Qu6Ftd5CkSeS4n8F99B%3DqkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] wtf npm

[Jeremy Darling]

He is calling the job listings ads.  IMHO they are out of the way and below
the valuable content.  Not like your paying for npmjs so really there
shouldn't be a complaint, they have to make their $$ someplace and I'd
rather it be from a couple job listings in the bottom right corner of the
page than from 5-10 2x3 advertisements about viagra.

 - Jeremy

On Tue, Jan 13, 2015 at 9:24 AM, Aria Stewart  wrote:

>
> > On Jan 13, 2015, at 10:12 AM, Andrew Kelley 
> wrote:
> >
> > Before, npmjs.org displayed module dependents - modules that depended
> on the module you are currently visiting - and did not display ads.
> >
> > Now, npmjs.org displays ads and does not display module dependents.
>
> The lack of dependents is a bug, I hear.
>
> What do you mean by ads?
>
> Aria
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/8F72302B-D68C-4330-8E76-ACE5905A8245%40nbtsc.org
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7Ei4%2BXCrtqCmp%3DpQy%3D5rnxjLzG3fK9oyE%2B-WK0f8DWPARw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] Re: Any way to capture errors from vm.runInNewContext?

[Jeremy Darling]

Hadn't thought of wrapping the code in a domain, thanks for the idea.  Will
give that a try and see if it gets me closer.  Trying to catch typos on a
remote SSH client instead of just getting a generic Hapi error back.

On Wed, Dec 10, 2014 at 9:49 PM, Andrey  wrote:

> no. You are only creating context, not full sandboxed JS environment.
> The code is called from the same event loop and functions you have in your
> context are same regular functions as in the rest of the code.
> All possible solutions are same as for "how do I handle async errors"
> question. Use domains, zones, co+generators etc (nothing gives you 100%
> guarantee)
>
>
> On Thursday, 11 December 2014 11:01:47 UTC+11, Jeremy wrote:
>>
>> Is there any way to actually capture exceptions from code running
>> vm.runInNewContext or vm.runInContext, etc...?  Seems there should be an
>> on('error') or something callback but can't find it.
>>
>> Wrapping the call in try/catch does't capture anything that is within an
>> async call within the script being executed.
>>
>>  - Jeremy
>>
>  --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/c8fb51bd-e38a-4dd3-8257-8b91b34fefec%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7EhP73qTEoVQ9ZEKY5HGiheeLH85FV87PuCRYyCW-Xr5tw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[nodejs] Any way to capture errors from vm.runInNewContext?

[Jeremy Darling]

Is there any way to actually capture exceptions from code running
vm.runInNewContext or vm.runInContext, etc...?  Seems there should be an
on('error') or something callback but can't find it.

Wrapping the call in try/catch does't capture anything that is within an
async call within the script being executed.

 - Jeremy

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7Eg-DOiz%2BA%2Birpp4XXvDq21FtwQbixaU090iZWyuyX_hOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] Re: Plain text search to ... modules?

[Jeremy Darling]

Thanks, if nothing else that's a great starting point :)

On Mon, Nov 10, 2014 at 3:49 AM, greelgorke  wrote:

> i have used https://github.com/tj/node-monquery but beware, the
> maintainer isn't doing node anymore.
>
> Am Freitag, 7. November 2014 20:29:10 UTC+1 schrieb Jeremy:
>
>> This seems like a common enough scenario that their is probably already a
>> module for it, so I'm asking before I start writing one :).
>>
>> Given a generic free form text search input on a webpage I would like to
>> have it converted over to a query to be executed against my data.  My
>> target is MongoDB like query instructions, but doesn't have to be MongoDB
>> as could easily transform it again.
>>
>> Something like:
>>
>> foo and bar
>>
>> might result in something like:
>>
>> {
>>   $or: [
>> {name: /foo and bar/i},
>> {description: /foo and bar/i},
>> {$and: [
>>   {name: /foo/i},
>>   {name: /bar/i},
>> ]},
>> {$and: [
>>   {description: /foo/i},
>>   {description: /bar/i},
>> ]},
>> ...etc...
>>   ]
>> }
>>
>> Has anyone already done something similar that is out there and easy to
>> include, or is this something that still needs to be created?
>>
>> Thanks,
>>  - Jeremy
>>
>  --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/ce4a5368-fa04-455a-bdeb-0a172c4738d6%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7EiAoO5KrzK8q%3DEV7UvEyYpCv5XpCRAZvo%2BduiFd%2BY3tfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[nodejs] Plain text search to ... modules?

[Jeremy Darling]

This seems like a common enough scenario that their is probably already a
module for it, so I'm asking before I start writing one :).

Given a generic free form text search input on a webpage I would like to
have it converted over to a query to be executed against my data.  My
target is MongoDB like query instructions, but doesn't have to be MongoDB
as could easily transform it again.

Something like:

foo and bar

might result in something like:

{
  $or: [
{name: /foo and bar/i},
{description: /foo and bar/i},
{$and: [
  {name: /foo/i},
  {name: /bar/i},
]},
{$and: [
  {description: /foo/i},
  {description: /bar/i},
]},
...etc...
  ]
}

Has anyone already done something similar that is out there and easy to
include, or is this something that still needs to be created?

Thanks,
 - Jeremy

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7Eh8oPoDs6YH_X0xVjRXnnkMkB%3D5bW_2%2Bh3U1gSUXNctCw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[nodejs] Re: Linking C sources files in CC files?

[Jeremy Darling]

Nevermind, found my own answer after finally hitting the right google
search terms.

Added
#ifdef __cplusplus
extern "C" {
#endif

... source code here...

#ifdef __cplusplus
}
#endif

So that the CPP compiler would know I was talking C and not CPP :)

On Mon, Oct 20, 2014 at 3:16 PM, Jeremy Darling 
wrote:

> Ok, stuck again.  Got everything working with the integer and pointer
> thing from all the help before (thanks!) but now I'm stuck in another
> place.  The source files I have are .C files with .H headers.  I can
> compile them using node-gyp with no issues and apparently bind them to my
> .CC file with no issue.
>
> When I try and actually USE them though I get back an error saying
> undefined symbol:  where  is always _Z11v
> the _Z11 and v never changes.  The  part is always the name of
> the method from the .C file.
>
> I'm guessing this is something really simple, but I don't know enough
> about C/CC/whatever to know where I'm screwing up.
>
> Here is a simple example, while this isn't the real code it blows up just
> like the real code :)
>
> /* lib.c */
> #include lib.h
> int test_linked(void){
>   return 1;
> }
>
> /* lib.h */
> #ifndef _LIB_
> #define _LIB_
> int rest_linked(void);
> #endif
>
> /*lib.cc*/
> #include 
> #include 
>
> #include "lib.h"
>
> using namespace v8;
>
> Handle Test(const Arguments& args){
>   HandleScope scope;
>   return scope.Close(Number::New(test_linked()));
> }
>
> void init(Handle exports) {
>   exports->Set(String::NewSymbol("test"),
>   FunctionTemplate::New(Test)->GetFunction());
> }
>
> NODE_MODULE(lib, init)
>
> /* binding.gyp */
>
> {
>   "targets": [
> {
>   "target_name": "lib",
>   "sources": [
> "src/lib.c",
> "src/lib.cc"
>   ]
> }
>   ]
> }
>
> Building with node-gyp rebuild results in all proper .O files put where
> you would expect (build/Release/obj.target/lib/src) and the .NODE file
> going where it should (build/Release)
>
> Then using:
> var lib = require('./build/Release/lib');
> lib.test();
>
> Fails with:
> node: symbol lookup error: /home/.../build/Release/lib.node: undefined
> symbol: _Z11test_linkedv
>
>
> I know this is something I'd doing wrong, but not sure what.  I'm guessing
> there is some reference to the .O files missing or they are where they
> shouldn't be so when the .NODE file loads it can't find the .O files and
> thus can't link the methods.
>
> As always, any help greatly appreciated.
>
>  - Jeremy
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7Egx4p5wSojHCSMr%2B0ZM3r9DeteeHy5hbsEDURoKMoX%2BMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[nodejs] Linking C sources files in CC files?

[Jeremy Darling]

Ok, stuck again.  Got everything working with the integer and pointer thing
from all the help before (thanks!) but now I'm stuck in another place.  The
source files I have are .C files with .H headers.  I can compile them using
node-gyp with no issues and apparently bind them to my .CC file with no
issue.

When I try and actually USE them though I get back an error saying
undefined symbol:  where  is always _Z11v
the _Z11 and v never changes.  The  part is always the name of
the method from the .C file.

I'm guessing this is something really simple, but I don't know enough about
C/CC/whatever to know where I'm screwing up.

Here is a simple example, while this isn't the real code it blows up just
like the real code :)

/* lib.c */
#include lib.h
int test_linked(void){
  return 1;
}

/* lib.h */
#ifndef _LIB_
#define _LIB_
int rest_linked(void);
#endif

/*lib.cc*/
#include 
#include 

#include "lib.h"

using namespace v8;

Handle Test(const Arguments& args){
  HandleScope scope;
  return scope.Close(Number::New(test_linked()));
}

void init(Handle exports) {
  exports->Set(String::NewSymbol("test"),
  FunctionTemplate::New(Test)->GetFunction());
}

NODE_MODULE(lib, init)

/* binding.gyp */

{
  "targets": [
{
  "target_name": "lib",
  "sources": [
"src/lib.c",
"src/lib.cc"
  ]
}
  ]
}

Building with node-gyp rebuild results in all proper .O files put where you
would expect (build/Release/obj.target/lib/src) and the .NODE file going
where it should (build/Release)

Then using:
var lib = require('./build/Release/lib');
lib.test();

Fails with:
node: symbol lookup error: /home/.../build/Release/lib.node: undefined
symbol: _Z11test_linkedv


I know this is something I'd doing wrong, but not sure what.  I'm guessing
there is some reference to the .O files missing or they are where they
shouldn't be so when the .NODE file loads it can't find the .O files and
thus can't link the methods.

As always, any help greatly appreciated.

 - Jeremy

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7EgWnAMob7jn-HpUWS1gjQyTKCKjVHC2utFmjnsc8gF8sA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] V8::Number to unsigned int?

[Jeremy Darling]

Worked perfectly, thanks greatly!

On Thu, Oct 16, 2014 at 11:07 PM, Louis Santillan 
wrote:

> The code you want is:
>
> int n = ( int )( args[ idx ]->Int32Value() );
>
> On Thu, Oct 16, 2014 at 8:46 PM, Jeremy Darling
>  wrote:
> > I'm trying to wrap up some hardware libraries for use with Node.js and
> have
> > run into a casting issue.  I did some searching around, but Google and
> the
> > cheat sheets failed me.  Can anyone answer how I should properly convert
> an
> > argument to a unsigned int?
> >
> >   Local pin = Uint32::New(args[0]->NumberValue());
> >   Local value = Uint32::New(args[1]->NumberValue());
> >
> >   if(set_pin(pin, value) < 0){
> > ThrowException(Exception::TypeError(String::New("Could not set value
> on
> > port")));
> > return scope.Close(Undefined());
> >   }
> >
> > Results in:
> >
> >   CXX(target) Release/obj.target/gpio/src/gpio.o
> > ../src/gpio.cc: In function 'v8::Handle Method(const
> > v8::Arguments&)':
> > ../src/gpio.cc:51:37: error: cannot convert 'v8::Local' to
> > 'unsigned int' for argument '1' to 'int set_pin(unsigned int, unsigned
> int)'
> >
> > I'm no C expert, so any advice greatly appreciated.
> >
> >  - Jeremy
> >
> > --
> > Job board: http://jobs.nodejs.org/
> > New group rules:
> > https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> > Old group rules:
> > 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 unsubscribe from this group and stop receiving emails from it, send an
> > email to nodejs+unsubscr...@googlegroups.com.
> > To post to this group, send email to nodejs@googlegroups.com.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/nodejs/CAAhs7Eh77uyvBsuxhk6xw0QN6Vg-7bTFnNMzhAs7J9%2BphUZigQ%40mail.gmail.com
> .
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/CAB9Rao-tO64kZH_bCrDiNqbMmZrj-rF4BtdjhqCjS3SH2Dbz-g%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7EgPjnat5uhX0BdVMspigq8N1AN3e3S6RTjPzKAO3bT_mQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[nodejs] V8::Number to unsigned int?

[Jeremy Darling]

I'm trying to wrap up some hardware libraries for use with Node.js and have
run into a casting issue.  I did some searching around, but Google and the
cheat sheets failed me.  Can anyone answer how I should properly convert an
argument to a unsigned int?

  Local pin = Uint32::New(args[0]->NumberValue());
  Local value = Uint32::New(args[1]->NumberValue());

  if(set_pin(pin, value) < 0){
ThrowException(Exception::TypeError(String::New("Could not set value on
port")));
return scope.Close(Undefined());
  }

Results in:

  CXX(target) Release/obj.target/gpio/src/gpio.o
../src/gpio.cc: In function 'v8::Handle Method(const
v8::Arguments&)':
../src/gpio.cc:51:37: error: cannot convert 'v8::Local' to
'unsigned int' for argument '1' to 'int set_pin(unsigned int, unsigned int)'

I'm no C expert, so any advice greatly appreciated.

 - Jeremy

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7Eh77uyvBsuxhk6xw0QN6Vg-7bTFnNMzhAs7J9%2BphUZigQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] Where to deploy node app on ubuntu

[Jeremy Darling]

We create a specific limited user for execution of our application (call it
appuser) and place the code in the home of that user
(/home/appuser///...) then create init script to setup
and start the app under the same user.  Make sure you setup the user so it
doesn't have SSH rights is a good idea.

 - Jeremy

On Wed, Oct 15, 2014 at 12:03 PM, Clarkie  wrote:

> I'm happy with the installation of nodejs itself; my question is around
> where to put our actual js files.
>
> Does anyone have any suggested locations and reasons why they use them?
>
> We've considered /usr/local and /opt but I'm not a linux or node expert so
> I'd love to hear your thoughts.
>
> Thanks, Clarkie
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/b0bb6702-2bb0-4711-a868-6f59e572dac4%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7Eg4j1YtfgD70h%2BEJ1FaTh5FmoLMHBjTsM%2BL9OpcO3Ppug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] Re: ANN: ssh2 module

[Jeremy Darling]

You may have to specify your shell on your embedded device.  What device
and shell are you using?

On Fri, Oct 10, 2014 at 3:29 PM, cesdaile  wrote:

> Yep on the current version of ssh2 - just installed this week.
>
> Ok - I think I am closer to figuring this out now with your help.
>
> The code on your gist works just as expected on a regular centos host but
> when I try it against my target server the *exec* option does trigger.
> The difference I suspect is that my target server is an embedded device and
> maybe it has some funky terminal settings I am not accounting for.
>
> The ssh login presents a banner and prompt as follows:
>
> Last login: Fri Oct 10 12:19:01 2014 from 10.240.106.106
>
>
>
> (console) #
>
> I seem to only have success when using *shell* and performing a
> *stream.write* with \n to execute the desired commands.
>
> On Friday, October 10, 2014 5:04:04 AM UTC-7, mscdex wrote:
>>
>> On Friday, October 10, 2014 1:46:41 AM UTC-4, cesdaile wrote:
>>>
>>> What I meant by 'choking' is that I am seeing a premature close on the
>>> stream when the output exceeds approx. 400 lines. Smaller output sizes seem
>>> to complete reliably and I can parse the entire command output without any
>>> troubles.
>>>
>>
>> I haven't experienced that at all. Are you using the latest version of
>> ssh2?
>>
>> Also, I don't think you need to use `shell()` for your purposes. I think
>> `exec()` should work fine, you just have to prefix your actual command with
>> "no paging;" (assuming that is a valid remote command) since it seems like
>> that's what you're currently trying to do. Your script should be something
>> as simple as this (substituting the 'cat /var/log/messages' with your `cmd`
>> variable): https://gist.github.com/anonymous/1a786c62927c632a23ed
>>
>  --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/ad22bb9e-804c-4aab-8b06-6bc81989a682%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7EiCNQ2L0PJvvmJ%2B7%2BDoKo1MwgpxyauqV0uhOqe98yyBUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] worry.... of ES6 and Node & errors

[Jeremy Darling]

I'm not on the Node team but I would assume that it would depend on what
the V8 team decides to do since Node is basically a wrapper around V8 at
the end of the day.  If the V8 team decides to enforce ES6 only (unlikely)
and not provide backward compatibility with ES5 then Node would most
certainly be forced to go this route as well, that or fork and maintain
their own version of the V8 core.

As ES6 is vastly different than ES5 it would seem more likely that a
directive will be added (similar to that of "use strict") that would
provide an indicator to the browser/javascript engine to switch into ES6
mode.  A real trick to that flag though would have to be the ability for it
to be queried thus allowing older (or non-ES6) browsers to prompt the user
or fall back to a different code base.

Course, as I said, I'm not a member of the Node Core nor am I a V8
developer, so my 2 cents is pretty much worthless :)

 - Jeremy


On Tue, Sep 9, 2014 at 3:44 PM, Ep Ga  wrote:

>  Are you going to force user to use ES6? A lot of dislike ES6 and are for
> ES5+; staying complaint with our code style and syntax as ES5, with the
> addition of new feature such as let and const, +. Which does not change the
> syntax but just add on new statement and operand.
>
> Are you going to force user to use new feature of ES6 or are you just
> going to make them available to be use in node, and node, not changing the
> code module where we will be force to use ES6 feature.
>
> Like I said, a lot of us disprove of some... most the majority of the new
> features in ES6, and are only looking forward to those that does not change
> the language, but add on... i.e.: ES5+
>
> Also, do you have documentation of all errors that could take place in the
> node environment?
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/bf8a0e1d-6128-4f84-9d2c-773b2b6cf5ee%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAAhs7EjmukFJo%2B__ga5KDG5Uy-T6eCzKstBKO_s_K8EjO81TTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] Re: Node/Javascript alternative to Graphite?

[Jeremy Darling]

D3 (or any of its wrappers) combined with just about any of the NoSQL DB's
tuned for performance should get you something similar.

Take a look at look at DC.js (http://nickqizhu.github.io/dc.js/) and just
log everything to your DB of choice then dump to Crossfilter to perform
your translations, render and go.

A basic charting application shouldn't be difficult to hack together.


On Sat, Apr 19, 2014 at 9:20 PM, // ravi  wrote:

> On Apr 19, 2014, at 9:19 PM, // ravi  wrote:
>
>
> Anyone know of a NodeJS based (JavaScript) equivalent of Graphite (
> http://graphite.wikidot.com) the metric/stats collection engine/server?
> I'd prefer a Node/JS version simply because I know I'll end up hacking the
> server a month into usage and I'd prefer to stick to JS for now.
>
>
> I did find Cube+Cubism, both of which are very neat, but Cubism's
> visualisation seems to be limited to horizontal time-series graphs (horizon
> charts) and ideally I'd like some counters, etc.
>
> --ravi
>
>
>  --
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] Introducing: KeystoneJS, a new cms / web app framework built on Express and Mongoose

[Jeremy Darling]

I actually ran across KeystoneJS a couple of days ago while looking for a
boxed CMS solution to recommend for some projects I've been working on.  It
looked interesting enough, but fell short in the same areas as almost every
other Node.js based offering on the market today (IMHO):

1) The example or tutorial if followed to the letter doesn't work when
complete.  If you clone the repo then it works, but following it line by
line something goes wonky.  I'd suggest just starting the tutorial with the
cloning the sample code (actually just supply a download link to the zip
from github) and then explain what it does.
2) The tutorial focuses almost completely on Jade.  This is great if you
want Jade, but sucks if you don't want Jade.  I much prefer to use static
HTML, JS, and CSS (read pre-compiled) rather than having the server do some
magic for me.
3) It appears that KeystoneJS focuses on a single endpoint delivery system
only (IE: One website per instance).  Sure, most users will only have a
single website that they want to support, but there are some of us that
have to support 100's of sites all at the same time.  It would be nice to
have a CMS/F that made this type of hosting easy.  Built in per-site and
global user, content, and feature management while still being hosted under
the "single instance" model.  We currently use a custom platform built
using cluster and the HTTP Headers to load content.
4) Lack of video tutorials.  Text is great and needed, but sometimes seeing
is so much easier, both of course is the best of both worlds :).  For
comparison its great to have a quick video you can watch so you can get a
basic understanding of how "difficult" it may be.
5) Lack of documentation on extension or replacement of parts (for example
what if I don't want to use Mongoose)
6) Forced static data structure even though your using MongoDB.  Why force
ORM/ORD if you use MongoDB?  Minimal Schema would go much further and
provide the same support in most cases.
7) Enforced storage engine.  Would be nice if your storage engine could be
switched out.  We have clients who would like to play with FoundationDB,
some that use Mongo, some like Redis.  This is one of those things that
would be difficult to retrofit into a solution, but would make lives like
mine easier :)

All of that being said, Keystone looks great.  It isn't confusing like
Calipso, overly complicated, or to focused on one single thing.  Long story
short it is in our shortlist of concepts outside of rebuilding our current
solution.

On the website you might think about having each blurb (Simpler Code, Form
Processing, Email, etc) link out to an example/video focused on that topic.

Thanks for all the hard work, and I look forward to seeing where you go
with KeystoneJS as well as contributing back if I can :)

 - Jeremy


On Wed, Jan 8, 2014 at 9:27 AM,  wrote:

> Hi,
>
> I just wanted to introduce myself and a project I've been working on (with
> a few collaborators) called KeystoneJS.
>
> It's an open source cms / web app framework built on express and mongoose.
>
> The idea is to make setting up node.js content managed websites easier,
> and provide a beautiful admin system out of the box.
>
> I use the term "cms" loosely, because it's more of a content management
> framework (unlike Ghost, which is a specifically blogging platform), and I
> use the term "framework" loosely because we don't want it to be a
> traditional framework, and because really, express is the framework.
> Keystone is a collection of patterns on top of it that make it simpler to
> set up for common uses.
>
> Many other languages have systems and frameworks that help developers get
> productive (django for python, rails for ruby, etc). Node.js has a lot of
> incredibly good packages thanks to npm and the community, but little to
> help people get started or bring it all together. I'm not saying that this
> is "django / rails for node", just that there's the potential for a
> platform here that will hopefully help a lot of people, and we're hoping to
> get it right.
>
> Node.js is a brilliant platform to work on, made even more so by the
> incredible packages that have been published. If we can build something
> that lets developers choose to start a project in node where they otherwise
> might have used wordpress, drupal or django because they needed a cms,
> that's the core of our vision.
>
> It's early days for Keystone. There's a lot to do to add documentation /
> examples, make it modular and extensible, improve the Admin UI and build
> all the features we've got in mind. But it's a start.
>
> Late last year I presented Keystone at SydJS (the Sydney Javascript meet
> up) and as part of it, built a new site (http://www.sydjs.com) which is
> currently the best demo of it in action (although my company has used it
> for a number of larger commercial projects too).
>
> We'd really appreciate feedback and suggestions on where we're heading
> with this. We'd also love to have peo

Re: [nodejs] soap module for node

[Jeremy Darling]

Oh, yeah, just put the changes into your project.  If the changes are part
of a module (node-soap as an example) then you would want to change those
libraries inside the node_modules folder.


On Mon, Nov 11, 2013 at 5:25 PM, Reza Razavipour
wrote:

> m question is how to run with the code with my changes? do I just add the
> files to my project?
> I am very new to node...
>
>
>
> On Monday, November 11, 2013 3:04:26 PM UTC-8, Jeremy wrote:
>
>> You would create a fork of the repository to your own Git Repository,
>> make the fix in your version, and then use that git path as your dependency
>> (http://github.com/...//node-soap.git)
>>
>> Also you should submit your fork as a PULL request back to fix the defect.
>>
>>
>> On Mon, Nov 11, 2013 at 5:01 PM, Reza Razavipour wrote:
>>
>>> please explain how i can run with my own modified version of the
>>> node-soap module or any open source module for that matter.
>>>
>>> so i download the source, make changes, what comes next? how do i start
>>> using it?
>>>
>>>
>>> On Monday, November 11, 2013 2:55:40 PM UTC-8, 3rdEden wrote:
>>>
  You could always consider fixing the bug, and opening a pull request
 for it. It’s open source after all.

 On Monday 11 November 2013 at 23:22, Reza Razavipour wrote:

 I have been evaluating soap packages for node and was very happy using
 node-soap. I am running into an issue, have opened one for it in github. It
 is either a bug or not but am getting functions that are getting called
 with wrong namespaces...

 What other node packages have you all used and your feedback is very
 much appreciated.


  --
 --
 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 nod...@googlegroups.com

 To unsubscribe from this group, send email to
 nodejs+un...@googlegroups.com

 For more options, visit this group at
 http://groups.google.com/group/nodejs?hl=en?hl=en

 ---
 You received this message because you are subscribed to the Google
 Groups "nodejs" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to nodejs+un...@googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.


   --
>>> --
>>> 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 nod...@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> nodejs+un...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to nodejs+un...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>  --
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] soap module for node

[Jeremy Darling]

You would create a fork of the repository to your own Git Repository, make
the fix in your version, and then use that git path as your dependency (
http://github.com/...//node-soap.git)

Also you should submit your fork as a PULL request back to fix the defect.


On Mon, Nov 11, 2013 at 5:01 PM, Reza Razavipour
wrote:

> please explain how i can run with my own modified version of the node-soap
> module or any open source module for that matter.
>
> so i download the source, make changes, what comes next? how do i start
> using it?
>
>
> On Monday, November 11, 2013 2:55:40 PM UTC-8, 3rdEden wrote:
>
>>  You could always consider fixing the bug, and opening a pull request
>> for it. It’s open source after all.
>>
>> On Monday 11 November 2013 at 23:22, Reza Razavipour wrote:
>>
>> I have been evaluating soap packages for node and was very happy using
>> node-soap. I am running into an issue, have opened one for it in github. It
>> is either a bug or not but am getting functions that are getting called
>> with wrong namespaces...
>>
>> What other node packages have you all used and your feedback is very much
>> appreciated.
>>
>>
>>  --
>> --
>> 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 nod...@googlegroups.com
>>
>> To unsubscribe from this group, send email to
>> nodejs+un...@googlegroups.com
>>
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "nodejs" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to nodejs+un...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>   --
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] Re: Debugging running node process

[Jeremy Darling]

I'd suggest looking at Theseus (for Brackets)
http://blog.brackets.io/2013/08/28/theseus-javascript-debugger-for-chrome-and-nodejs/

Has helped me debug callback soup more than once.  I use it frequently on
my Lenovo IdeaPad u310 for debugging, but not for editing, so it doesn't
require a ton of resources.  On my I7 desktop I use it for both editing and
debugging.


On Thu, Sep 19, 2013 at 9:36 AM, Vivek Goel  wrote:

>
>
> On Thursday, September 19, 2013 12:08:59 PM UTC+5:30, Andrey wrote:
>>
>> From debugger you have an option to 1) break on next js statement 2)
>> enable statistical profiler (and later analyse with v8.log tick processor
>> what functions are repeatedly executed)
>>
> Sorry , If I am getting any thing wrong here.
> My problem is callback hanged *(lost some where).* No next function is
> getting executed for particular one request here.
> I think then attaching breakpoint on next statement or enabling
> statistical profile will not help here.
>
> Please correct me if I am wrong.
>
>
>
>>
>> On Thursday, 19 September 2013 15:11:00 UTC+10, Vivek Goel wrote:
>>>
>>> But that will not give stack trace of all current callbacks.
>>> I need to attach a breakpoint and wait,  but problem is I don't know
>>> where  is it  waiting. So breakpoint will be blind guess.
>>> On 19-Sep-2013 4:09 AM, "Andrey"  wrote:
>>>
 You can enable debugger agent in your process by sending SIGUSR1 ( see
 http://nodejs.org/api/**debugger.html#debugger_**advanced_usage)

 On Wednesday, 18 September 2013 21:21:04 UTC+10, Vivek Goel wrote:
>
> Hi,
> I have node daemon (gearman worker). Sometime I am facing the problem
> that the process don't respond to some particular requests (gearman jobs).
>
> I am using following modules
>
>- gearman
>- mysql
>- redis
>- aws sdk
>- node-gcm
>- node-apn
>
> I don't know in which module the program is hanging. Is it hanging in
> my code or some of third party code.
>
> Is there a way to find out in which module it is hanged  (while
> process is in running state) ?
>
>
> What are the methods used for debugging already running process in
> node ?
>
>
>
>
>  --
 --
 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 nod...@googlegroups.com
 To unsubscribe from this group, send email to
 nodejs+un...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/**group/nodejs?hl=en?hl=en

 ---
 You received this message because you are subscribed to a topic in the
 Google Groups "nodejs" group.
 To unsubscribe from this topic, visit https://groups.google.com/d/**
 topic/nodejs/WvqEUTu5DcM/**unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to
 nodejs+un...@googlegroups.com.
 For more options, visit 
 https://groups.google.com/**groups/opt_out
 .

>>>  --
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google

Re: [nodejs] Re: How i can deploy nodejs in vps

[Jeremy Darling]

Assuming your on linux:
http://stackoverflow.com/questions/11275870/how-can-i-automatically-start-a-node-js-application-in-amazon-linux-ami-on-aws

Also, wrap your process in forever to keep it up and running in case of
faults.

If you want to go all out, services like AppFog, NodeJitsu, and etc have
opensourced the source to their systems.  You could always stand it up on
your VIP


On Mon, Aug 26, 2013 at 4:35 PM, Tim Caswell  wrote:

>
>
>
> On Mon, Aug 26, 2013 at 11:30 AM, Michael Pisarski wrote:
>
>> I use forever and have not had any issues.
>>
>
> Does forever handle machine reboots?
>
>
>> On Sunday, August 25, 2013 4:57:10 AM UTC-4, Fernando Segura Gòmez wrote:
>>>
>>> Hi.
>>> I need help, im very newbie about how deploy my nodejs app in
>>> production,i have always worked in localhost, but  i dont know how i can
>>> deploy an app and run always, when i run with the command node, and  i
>>> close my ssh program, my nodejs app is stopped.
>>> How i can deploy and keep running my app?
>>>
>>  --
>> --
>> 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 nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "nodejs" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to nodejs+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] Re: Java APi for Node.js

[Jeremy Darling]

I would look to Rhino for use with Tibco EMS as a BW Process.

That or, the way that we actually did this, create an EMS BW Process that
acts as a bridge between a MongoMQ (MongoDB Capped Collection used as a
message queue) and TibcoEMS.

If there were a JMS Adapter for Node.js then we could put Node.js processes
on EMS.  But alas, I know of none.

 - Jeremy


On Sun, Jul 21, 2013 at 2:00 PM, Matthew Dalrymple wrote:

> What is your suggestion for a way of hooking up node.js to a Tibco EMS?
> Would you wrap a native Tibco EMS library as a package for node and do it
> that way? Just trying to figure this out as node would work very well with
> Tibco EMS.
>
> Thanks
>
>
>
> On Friday, July 13, 2012 6:29:19 PM UTC-4, Jeremy wrote:
>
>> Rhino is the "Node.js" of the Java world (traditionally speaking).
>>
>> But, a distributed MQ like Zero is a way to integrate via message
>> passing.  My MongoMQ could also be used as could just about any other MQ
>> that is supported by Java and Node.
>>
>> If your already using an enterprise system like Tibco EMS you can also
>> place your Node handlers on that bus without too much work.
>>
>> As for directly integrating the Node runtime into Java, that isn't going
>> to happen (again look to Rhino for that).  Node is native, Java is a VM.
>>  In memory IPC via a C/C++ wrapper is about as close as you could get.
>>
>>  - Jeremy
>>
>> On Fri, Jul 13, 2012 at 4:12 PM, Alexey Petrushin 
>> wrote:
>>
>>> ZeroMQ may be an option
>>>
>>> On Friday, July 13, 2012 11:28:16 AM UTC+4, pushpinder rattan wrote:

 Folks,


 Is there any integration of Java and  NodeJs?? Can we invoke nodejs
 using Java?


 thanks
 Pushpinder

  --
>>> 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 nod...@googlegroups.com
>>>
>>> To unsubscribe from this group, send email to
>>> nodejs+un...@**googlegroups.com
>>>
>>> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] windows-service - Run Node.JS programs as native Windows Services.

[Jeremy Darling]

Stephen, no offense taken at all.  As for WinSer, its what we use today in
our production environment without NPM, so that is a bit of a misnomer.
 Simply place it in a Vendor folder and away you go.

I'll be looking at Windows-Service as well.

Would be nice if it were on GitHub though :)

 - Jeremy

On Fri, Feb 22, 2013 at 7:17 AM, José F. Romaniello
wrote:

> Sure thing Stephen! I am the author of winser and I gave my point of view
> on your project and as I said it looks *very nice*, I will consider next
> time i have to deploy something to a windows server.
>
> for me node.js is about alternatives, so i am really glad winser is not
> the only option to run node programs as windows services now
>
> regards
>
>
> 2013/2/22 Stephen Vickers 
>
>> I should also add, I don't want to appear to be critical of WinSer, or
>> nssm.exe for that matter.  It's just that I have my own motivations,
>> requirements and preferences, as do the authors of those programs.
>>
>>
>> On Friday, 22 February 2013 12:17:56 UTC, Stephen Vickers wrote:
>>>
>>> Hi Jeremy,
>>>
>>> A number of small reasons why I would use windows-service instead (some
>>> people may consider some of these points moot, I don't):
>>>
>>>- Node.js and program path detection is automatic and obvious
>>>- Supports spaces in service names (although this could be fixed
>>>quite easily in WinSer)
>>>- Doesn't depend on npm to add, remove and run services
>>>- Doesn't depend on nssm.exe which means one less task of trying to
>>>keep that up to date (not assuming the module author will always want to
>>>update nssm.exe to the latest version when available)
>>>   - Which also may have library dependency issues - unless
>>>   you compile it yourself
>>>
>>> Then there a couple of major reasons, which are probably
>>> more in-line with my requirements.
>>>
>>> I've already written something similar for Perl, for the company I work
>>> for, but have never been allowed to make that code public.
>>>
>>> I'm just getting into Node.js with the view of writing an application
>>> delivered using a Windows installer (NSIS based) as the end systems will
>>> have no build environment available.
>>>
>>> So, in part this was a learning exercise to see if it was possible, and
>>> to remove dependency on npm for a deployed application.
>>>
>>> It's also worth considering that the service code base is much smaller
>>> than the nssm.exe code base, and this is not a criticism of nssm.exe (quite
>>> the opposite, it seems like a very good program), the point is that there
>>> is less to go wrong and maintain.
>>>
>>> Steve
>>>
>>> On Friday, 22 February 2013 03:06:14 UTC, Jeremy wrote:

 What is the difference in this and WinSer using NSSM?  I'm not picking
 I'm just curious.


 On Thu, Feb 21, 2013 at 4:41 PM, Stephen Vickers 
 wrote:

> Hi All,
>
> I've created a new module named "windows-service" providing the
> ability to run Node.JS programs as native Windows Services.
>
> The new module can be installed using npm:
>
> https://npmjs.org/package/**windows-service
>
>  Steve
>
> --
> --
> 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 nod...@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/**group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to nodejs+un...@googlegroups.com.
> For more options, visit 
> https://groups.google.com/**groups/opt_out
> .
>
>
>

  --
>> --
>> 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 nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "nodejs" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to nodejs+unsubscr...@googlegroups.com.
>> For more options,

Re: [nodejs] windows-service - Run Node.JS programs as native Windows Services.

[Jeremy Darling]

What is the difference in this and WinSer using NSSM?  I'm not picking I'm
just curious.


On Thu, Feb 21, 2013 at 4:41 PM, Stephen Vickers wrote:

> Hi All,
>
> I've created a new module named "windows-service" providing the ability to
> run Node.JS programs as native Windows Services.
>
> The new module can be installed using npm:
>
> https://npmjs.org/package/windows-service
>
> Steve
>
> --
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] Re: Java APi for Node.js

[Jeremy Darling]

Rhino is the "Node.js" of the Java world (traditionally speaking).

But, a distributed MQ like Zero is a way to integrate via message passing.
 My MongoMQ could also be used as could just about any other MQ that is
supported by Java and Node.

If your already using an enterprise system like Tibco EMS you can also
place your Node handlers on that bus without too much work.

As for directly integrating the Node runtime into Java, that isn't going to
happen (again look to Rhino for that).  Node is native, Java is a VM.  In
memory IPC via a C/C++ wrapper is about as close as you could get.

 - Jeremy

On Fri, Jul 13, 2012 at 4:12 PM, Alexey Petrushin <
alexey.petrus...@gmail.com> wrote:

> ZeroMQ may be an option
>
> On Friday, July 13, 2012 11:28:16 AM UTC+4, pushpinder rattan wrote:
>>
>> Folks,
>>
>>
>> Is there any integration of Java and  NodeJs?? Can we invoke nodejs using
>> Java?
>>
>>
>> thanks
>> Pushpinder
>>
>>  --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] node-mongodb-native problems with sort

[Jeremy Darling]

try:

col.find({username:**username}, {}, {sort: {date: -1}}, function(err,
records){
  console.log(records);
});

1st param is the query, 2nd param is options object, sort is an object
under the options object as entered in the Mongo CLI.  In your examples
your using arrays instead of objects.

 - Jeremy

On Fri, Jul 13, 2012 at 3:03 PM, john.tiger wrote:

> have tried various syntax but nothing seems to be working - and which is
> right docs vs examples vs tests (I would think tests - some show "desc"
> some show "-1"
>
> here's an example:
>
> coll.find({"username":**username}, {"sort":['date','desc']},
> function(err,cursor) {
>
> also tried as per test:
> coll.find({"username":**username}, {"sort":[['date', -1]]},
> function(err,cursor) {
>
> thks for any help on this
>
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscribe@**googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[nodejs] [ANN] MongoMQ - A basic MQ based on Node.js and MongoDB tailable cursors

[Jeremy Darling]

MongoMQ is a messaging queue built on top of Node.js and MongoDB's tailable
cursors. It allows for distributed of messages across workers in both a
single reciever and broadcast method.

MongoMQ does NOT (currently) support callback's once a message is
processed. Instead it is recommended that you use a one time listener to
pickup responses if this is required.

Requires MongoDB 2.x+ and Node.js 0.8.2+

Git it from: https://github.com/jdarling/MongoMQ

Get it from npm: npm install mongomq

 - Jeremy

-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[nodejs] [ANN?] Windows 64 bit SQL Client for Node.js

[Jeremy Darling]

I've looked and looked for a good SQL Client that worked on Windows 64 bit
for Node.js and didn't find any, so I build one myself.  I started with
code from other projects but in the end just used the MS examples and
expanded them to the point that they worked.

This is being used in production products, so I know it works and works
well.  The binary that is packaged with the repo is for 64 bit Windows.
This is a pure C++ implementation so, it should build in 32 bit with VC++
express.

sqlnative2.node is a native (binary) library for Node.js that allows you to
connect to SQL Server and execute SQL Statements (Stored Procedures,
Queries, whatever can be done through a command object). It was developed
due to the lack of working SQL clients for Node.js. The code is C++ and
compiles in Visual Studios 2010 (professional required for 64 bit). The
current library contains the 64 bit build of sqlnative2.node

https://github.com/jdarling/node-sqlnative

 - Jeremy

-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] NodeJS login in Chrome 17.x - global sessions/cookie issue

[Jeremy Darling]

I'm not completely familiar with how express handles encoding, but when you
send over your content make sure you do a toString('utf-8') on it and on
your response object headers specify the uft-8 encoding as well.

Something similar to:
var headers = {
  "Content-Type": "text/html; charset=utf-8"
}

res.setEncoding('utf-8');
res.write(myContent.toString('utf-8');
res.end();

If UTF-8 doesn't work switch back to ASCII standard (change utf-8 to ascii)
and try again.  Also make sure that you have all of the updates put on your
XP box.  I know there have been several language updates for it that may be
affecting your results with Russian.  If you can get your server up and
running again I'll be happy to run my XP64 US-EN install against it to see
if it has any problems.

 - Jeremy

2012/6/26 Ilya Rusanen 
>
>> Do you mean I should specify encoding in the page html-code > http-equiv='Content-Type' content='Type=text/html; charset=utf-8'>
>> or somewhere on the backend? I should mention, most of site content is in
>> russian (UTF-8 is prefered), however credentials (login, pass, email) may
>> be only latin.
>>
>>
>>

-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] node.js install to BlueHost configuration error

[Jeremy Darling]

Just because I'm curious what hosting package do you have with BlueHost?  I
only see where they have an unlimited plan running $5 a month.  If that is
the same one you are using I'd love to know more details about how you
setup Node and what the performance has been.

 - Jeremy

On Mon, May 21, 2012 at 6:13 PM, Matt Clark  wrote:

> Sweet! Thanks so much! Seems to be working now! Just have to figure out
> the server management stuff!
>
> On Monday, May 21, 2012 5:48:09 PM UTC-5, Ben Noordhuis wrote:
>>
>> On Tue, May 22, 2012 at 12:40 AM, Matt Clark 
>> wrote:
>> > So since I'm having to do this all in my home directory, how would I
>> point
>> > the make to a local build of libuv? (sorry if this is a noob question,
>> but
>> > I'm pretty new to restrictive builds like this)
>>
>> You don't because it won't compile. The version of libuv that node
>> v0.6.x uses is massively behind libuv master.
>>
>> As a stop-gap measure, replace the line that says `fl = O_CLOEXEC`
>> with `fl = 0`, it will do the Right Thing.
>>
>  --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Nodejs scaling by running multiple processes: what's the optimal number of processes?

[Jeremy Darling]

Our experience has shown that 2 processes per core thread (IE: On an i7 you
get 8 core threads on 4 cores due to hyperthreading) balances quite well.
 This isn't to say that your experience won't differ.  We have all of our
code broke into logical families and utilize Hook.io as a message bus
between.  Scaling has been as simple as spinning up a new machine into the
mesh.

We are running on VM's with 4 cores, 8 GB Ram, and 50GB DAS currently and
besides a few minor issues with resource slice time have been unable to
saturate our current 4 machine mesh.  Each stack has MongoDB and Node
installed with all families copied with some only being spun up on a
machine or two (background processes that don't tax the mesh, basically
dedicated processing boxes).

 - Jeremy

On Wed, May 16, 2012 at 7:28 PM, Isaac Schlueter  wrote:

> Chances are that the workers are going to be spending the most time on
> CPU.  If you have a few too many, it's not super bad.
>
> I'd try going with the same number of workers as you have CPUs.
>
> On Wed, May 16, 2012 at 4:33 PM, Qi Fan  wrote:
> > Hi,
> >
> > On an 8-core computer, is it better to run 8 node.js processes, or is it
> > better to run fewer?
> >
> > I'm speculating that if both the event loops and system IO are busy then
> 8/8
> > configuration may freeze at a lower load than 7/8 configuration since
> each
> > IO operations will suspend nodejs processes.
> >
> > --
> > 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 nodejs@googlegroups.com
> > To unsubscribe from this group, send email to
> > nodejs+unsubscr...@googlegroups.com
> > 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Re: Node Concepts

[Jeremy Darling]

you hit a running filly?

On Wed, May 2, 2012 at 1:08 PM, codepilot Account wrote:

> This shit is getting skilly.
>
>
> On Wed, May 2, 2012 at 11:06 AM, Mark Hahn  wrote:
>
>> This skit is getting silly.
>>
>>
>> On Wed, May 2, 2012 at 11:05 AM, Marak Squires 
>> wrote:
>>
>>> But how to node?
>>>
>>>
>>> On Wed, May 2, 2012 at 11:04 AM, Stewart Mckinney 
>>> wrote:
>>>
 My head asplode!

 On Wed, May 2, 2012 at 2:01 PM, Marak Squires 
 wrote:

> You send node?
>
>
> On Wed, May 2, 2012 at 11:00 AM, Mark Hahn  wrote:
>
>> I hab a code.
>>
>>
>> On Wed, May 2, 2012 at 10:54 AM, Stewart Mckinney <
>> lordma...@gmail.com> wrote:
>>
>>> It's similar to a rose..
>>>
>>>
>>> On Wed, May 2, 2012 at 9:44 AM, David Whitten <
>>> whit...@worldvista.org> wrote:
>>>
 Wanna avoid process load?


 On Wed, May 2, 2012 at 1:25 AM, Marak Squires <
 marak.squi...@gmail.com> wrote:

> Can you code?
>
>
> On Tue, May 1, 2012 at 10:24 PM, rajesh wrote:
>
>> What is node?
>>
>> On May 2, 10:22 am, rajesh  wrote:
>> > Guys plz use this thread to let people learn node as tutorial.
>>
>> --
>> 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 nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>
>
>
> --
> --
> Marak Squires
> Co-founder and Chief Evangelist
> Nodejitsu, Inc.
> marak.squi...@gmail.com
>
>  --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
 To unsubscribe from this group, send email to
 nodejs+unsubscr...@googlegroups.com
 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 nodejs@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> nodejs+unsubscr...@googlegroups.com
>>> 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 nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>
>
>
> --
> --
> Marak Squires
> Co-founder and Chief Evangelist
> Nodejitsu, Inc.
> marak.squi...@gmail.com
>
>  --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

  --
 Job Board: http://j

Re: [nodejs] Opinions on self hosting stacks for Node apps

[Jeremy Darling]

Sorry for the late reply to everyone was at the track with my Kids all
weekend racing so now to play catchup :).

I probably didn't word that very well at all. I was saying that since each
instance of Node will run in a separate process that the # of cores matters
more than processor speed from what I have seen.  Now I will say that we
have our code separated into service families with each family running in a
different instance of node and communicating either over IPC (local), TCP
(in network remote), and REST over HTTP (public remote) for RPC.  (on
second read that seems more complex LOL)

We have matched down our stack per machine to 2 node processes per core +1
(each) for OS and MongoDB usage.  Nearness is used to decide what gets
turned on on each stack (everything gets deployed but machines don't run
the full stack), so two families that are likely to call between each other
(hopefully one high load and one low) are placed on the same physical
machine.  Things that don't call one another are placed on completely
separate machines.  Replication is handled by MongoDB.

When we placed it all on one single "machine" (I have to admit its a VM in
a service center and I have no idea what "it" is) having the same # of
cores, RAM, etc the server actually ran slower than when it was balanced
across multiple "smaller" machines totaling the same specifications (# of
cores and RAM).

Thinking about this (and going back some years so my info is dated) this
makes perfect sense as you should be lowering the task switch (even if it
is pico seconds per switch) and there is no need to balance across multiple
processors since in the case of i series processors the cores are on the
same silicon pointing at the same IO Bus.  In the server I'm guessing (4x4,
4x8, or 8x8) that we are running into the VM "load balancing" across the
processors thus causing more latency than we experience on the multiple
machines config.  Course I could be wrong :)

But, I digress, what I'm really interested in is what others
experiences have been with hardware setups and hosting?

 - Jeremy

On Fri, Apr 20, 2012 at 12:04 PM, Tim Caswell  wrote:

> Jeremy, are you saying that 3 node processes on three dedicated machines
> is faster than one node process on one beefy machine?
>
> If you want to use all n cores on a machine you need n node processes on
> that machine.  And yes, node is mostly single threaded.  Some things like
> fs.* and zlib.* use a thread-pool so that they don't block the main thread,
> but your js code will always run in the main thread.
>
>
> On Fri, Apr 20, 2012 at 12:00 PM, Ryan Schmidt  > wrote:
>
>>
>> On Apr 20, 2012, at 07:40, Jeremy Darling wrote:
>>
>> > Just curious what experiences others have had with hardware and hosting
>> multi-process Node app stacks using MongoDB (or similar)?  So far my
>> testing has shown that a cluster of smaller (3 - i5's with 8GB Ram and
>> 120GB SSD's) machines out performs a single massive server (4x4 with 64GB
>> Ram and 120GB NAS fiber attached storage).  This isn't too surprising
>>
>> It is to me.. why would that be the case?
>>
>> > since node basically allocates a single core per running process,
>>
>> What do you mean? I didn't think node "allocates" anything; I thought
>> *you* allocate node processes by using cluster to start as many of them as
>> is appropriate for the size of your server.
>>
>>
>> --
>> 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 nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[nodejs] Opinions on self hosting stacks for Node apps

[Jeremy Darling]

Just curious what experiences others have had with hardware and hosting
multi-process Node app stacks using MongoDB (or similar)?  So far my
testing has shown that a cluster of smaller (3 - i5's with 8GB Ram and
120GB SSD's) machines out performs a single massive server (4x4 with 64GB
Ram and 120GB NAS fiber attached storage).  This isn't too surprising since
node basically allocates a single core per running process, but have others
seen the same results?  I know core speed will make a difference and other
things come into play but what are the basic experiences, have I just been
lucky so far?

Also, what is the best OS flavor to run for best support across libraries
and other such things?  So far I've tried MS Windows 2008 Server, Windows 7
Enterprise, and RHEL.  Curious about best Linux flavor more than anything,
experiences with one being any better than another, better support for
install (RHEL sucks to install into) etc, etc, etc?

Thanks for any feedback,
 - Jeremy

-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] cool home automation stuff in node?

[Jeremy Darling]

ROLF so keeping that link for future reference :)

On Monday, April 16, 2012, Dean Landolt wrote:

>
>
> On Mon, Apr 16, 2012 at 1:18 PM, Mark Hahn  'cvml', 'm...@hahnca.com');>
> > wrote:
>
>> Is this a server from home?
>
>
> http://lmgtfy.com/?q=home+automation
>
>
>
>>
>> On Mon, Apr 16, 2012 at 10:07 AM, Kevin O 
>> 
>> > wrote:
>>
>>> I am currently working on a couple of node modules for home automation.
>>> The first is a module for interfacing with the Elk M1 Automation
>>> Controllerover
>>>  their ASCII RS-232 protocol. I am probably going to release it into
>>> NPM this week.
>>>
>>> I am also going to be starting a module for integration to the ISY-99i
>>> controller . Not sure when I
>>> am going to start this but this should be way easier than the Elk.
>>>
>>> Anyone else doing interesting home automation stuff in node?
>>>
>>> --
>>> 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 
>>> nodejs@googlegroups.com>> 'nodejs@googlegroups.com');>
>>> To unsubscribe from this group, send email to
>>> nodejs+unsubscr...@googlegroups.com >> 'nodejs%2bunsubscr...@googlegroups.com');>
>>> 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 
>> nodejs@googlegroups.com> 'nodejs@googlegroups.com');>
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com > 'nodejs%2bunsubscr...@googlegroups.com');>
>> 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 
> nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com  'nodejs%2bunsubscr...@googlegroups.com');>
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] SMTP client that works with Windows

[Jeremy Darling]

I've had really good luck with mailer ( https://github.com/Marak/node_mailer ),
but I don't think it supports attachments.  Might be easy to modify it to
support them though as basically its just Base64 encoded into the headers
based on Mime Type.  Conversion of something like the code here (
http://webcheatsheet.com/PHP/send_email_text_html_attachment.php )
could/would add the ability.

 - Jeremy

On Fri, Apr 13, 2012 at 7:38 AM, Alan Hoffmeister  wrote:

> Hello there!
>
> I know there is some good npm modules for sending e-mail by SMTP
> account, but none of them are working with Windows, what I need is to
> be able to send e-mail from an SMTP account with attachments.
>
> Any good sugestion?
>
> --
> Att,
> Alan Hoffmeister
>
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Any good rest module?

[Jeremy Darling]

Have a look at Hook.io ( https://github.com/hookio ) and Hook.io-restful (
https://github.com/jdarling/hook.io-restful  ).  Might just suite your
needs.  Note that Hook.io 0.9 will introduce some type of balancing
mechanic that doesn't currently exist today.  Restful may be a bit out of
date, but I have the updated version ready if you find a need (just haven't
had time to setup GIT and do the push on this new machine).

 - Jeremy

On Wed, Apr 11, 2012 at 9:58 AM, Alan Hoffmeister  wrote:

> I was thinking about something like this on the server side:
>
> rest-module.on('hello', function(req, res, data){
> res.send('Hello ' + data.world);
> });
>
> And on the client side:
>
> $('#button').click(function(){
> var data = { world : 'world' };
> rest-module.emit('hello', data, function(res){
> console.log(res);
> });
> });
>
> Is there anything like that already? Tried node-restify, but that's not
> quite simple as I wished.
>
> Thank's!
>
>
> --
> --
> Att,
> Alan Hoffmeister
>
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[nodejs] Re: ENOBUFS - How to catch/deal with it?

[Jeremy Darling]

I'll see if I can't create one that just uses EventEmitter, though I have
to admit that my skills are not so (as the kids say) mad :)

- Jeremy

On Monday, March 26, 2012, Bert Belder  wrote:
> On Mar 26, 2:22 pm, Jeremy Darling  wrote:
>> From everything that I've read this primarily deals with Windows and its
>> ability to cache network communications.  I have a hook.io app that with
>> occasionally bomb out with the ENOBUFS exception and for all of my
efforts
>> I can't figure out how to catch and deal with this error.
>>
>> I realize that the exception is raised when the OS can no longer buffer
up
>> incoming/outgoing messages.  What I'm wondering is if there is a way to
>> deal with it?  Can I write all incoming messages to a DB (MongoDB is our
>> current DB) and minimalize this issue?  On outgoing is there a way to
catch
>> the issue, wait for the buffer to catch up, and then retry some how
(again
>> maybe a DB cache)?  How are others dealing with this when they see it?
>>
>> try/catch doesn't seem to get notified and instead the app just exits
>> writing basic details to the console.  This also appears to strand memory
>> from what I can tell.  Of course it could also be the OS trying to catch
up
>> and basically giving up.
>>
>> Any help greatly appreciated, I've copied both the Hook.io and Node.js
>> groups in hopes that someone has/knows a work around or solution.
>>
>>  - Jeremy
>>
>> PS: An "easy" way to duplicate this (although in a completely different
>> manor) is to have a hook that when called emits multiple calls to another
>> hook, this in turn calls the caller a number of times as well.  This
>> basically just sets up a quick scenario and is not what is happening in
our
>> production code.
>
> Do you have a test case that does not rely on hook.io?
>
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] ENOBUFS - How to catch/deal with it?

[Jeremy Darling]

I've tried on all of the following and see it (at different levels) on each:

Windows 7 - 32 bit
Windows 7 - 64 bit
Windows XP - 32 bit
Windows 2008 Server - 64 bit

All with different ram and drive setups but it seems to match the 50Mb
limits I've seen posted on a few different MS boards.

 - Jeremy

On Mon, Mar 26, 2012 at 8:48 AM, Ben Noordhuis  wrote:

> On Mon, Mar 26, 2012 at 14:22, Jeremy Darling 
> wrote:
> > From everything that I've read this primarily deals with Windows and its
> > ability to cache network communications.  I have a hook.io app that with
> > occasionally bomb out with the ENOBUFS exception and for all of my
> efforts I
> > can't figure out how to catch and deal with this error.
> >
> > I realize that the exception is raised when the OS can no longer buffer
> up
> > incoming/outgoing messages.  What I'm wondering is if there is a way to
> deal
> > with it?  Can I write all incoming messages to a DB (MongoDB is our
> current
> > DB) and minimalize this issue?  On outgoing is there a way to catch the
> > issue, wait for the buffer to catch up, and then retry some how (again
> maybe
> > a DB cache)?  How are others dealing with this when they see it?
> >
> > try/catch doesn't seem to get notified and instead the app just exits
> > writing basic details to the console.  This also appears to strand memory
> > from what I can tell.  Of course it could also be the OS trying to catch
> up
> > and basically giving up.
> >
> > Any help greatly appreciated, I've copied both the Hook.io and Node.js
> > groups in hopes that someone has/knows a work around or solution.
> >
> >  - Jeremy
> >
> > PS: An "easy" way to duplicate this (although in a completely different
> > manor) is to have a hook that when called emits multiple calls to another
> > hook, this in turn calls the caller a number of times as well.  This
> > basically just sets up a quick scenario and is not what is happening in
> our
> > production code.
>
> Jeremy, on what platform are you seeing that? You don't explicitly say
> it (or I failed to grasp a subtlety) but you mention Windows?
>
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[nodejs] ENOBUFS - How to catch/deal with it?

[Jeremy Darling]

>From everything that I've read this primarily deals with Windows and its
ability to cache network communications.  I have a hook.io app that with
occasionally bomb out with the ENOBUFS exception and for all of my efforts
I can't figure out how to catch and deal with this error.

I realize that the exception is raised when the OS can no longer buffer up
incoming/outgoing messages.  What I'm wondering is if there is a way to
deal with it?  Can I write all incoming messages to a DB (MongoDB is our
current DB) and minimalize this issue?  On outgoing is there a way to catch
the issue, wait for the buffer to catch up, and then retry some how (again
maybe a DB cache)?  How are others dealing with this when they see it?

try/catch doesn't seem to get notified and instead the app just exits
writing basic details to the console.  This also appears to strand memory
from what I can tell.  Of course it could also be the OS trying to catch up
and basically giving up.

Any help greatly appreciated, I've copied both the Hook.io and Node.js
groups in hopes that someone has/knows a work around or solution.

 - Jeremy

PS: An "easy" way to duplicate this (although in a completely different
manor) is to have a hook that when called emits multiple calls to another
hook, this in turn calls the caller a number of times as well.  This
basically just sets up a quick scenario and is not what is happening in our
production code.

-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Problem with node-waf

[Jeremy Darling]

I can't help you with your problem but I will say that maybe you should be
moving to node-gyp since it is the replacement for node-waf?  At least
according to TTN it is :)

https://github.com/TooTallNate/node-gyp
" node-gyp is a cross-platform command-line tool written in Node.js for
compiling native addon modules for Node.js, which takes away the pain of
dealing with the various differences in build platforms. It is the
replacement to the node-waf program which is removed for node v0.8. If you
have a native addon for node that still has a wscript file, then you should
definitely add a bindings.gyp file to support the latest versions of node."

I've actually had better experiences getting things to  build with GYP than
WAF

 - Jeremy

On Fri, Mar 2, 2012 at 7:10 AM, Thierry Templier  wrote:

> Hello,
>
> I recently updated Node to version 0.6.11 and I have now problems when
> trying to use node-waf to compile a native addon.
>
> Here is the error I have:
>
> Traceback (most recent call last):
>  File "/usr/local/bin/node-waf", line 16, in 
>Scripting.prepare(t, os.getcwd(), VERSION, wafdir)
>  File "/usr/local/bin/../lib/node/**wafadmin/Scripting.py", line 145, in
> prepare
>prepare_impl(t, cwd, ver, wafdir)
>  File "/usr/local/bin/../lib/node/**wafadmin/Scripting.py", line 135, in
> prepare_impl
>main()
>  File "/usr/local/bin/../lib/node/**wafadmin/Scripting.py", line 188, in
> main
>fun(ctx)
>  File "/usr/local/bin/../lib/node/**wafadmin/Scripting.py", line 386, in
> build
>return build_impl(bld)
>  File "/usr/local/bin/../lib/node/**wafadmin/Scripting.py", line 399, in
> build_impl
>bld.add_subdirs([os.path.**split(Utils.g_module.root_**path)[0]])
>  File "/usr/local/bin/../lib/node/**wafadmin/Build.py", line 981, in
> add_subdirs
>self.recurse(dirs, 'build')
>  File "/usr/local/bin/../lib/node/**wafadmin/Utils.py", line 634, in
> recurse
>f(self)
>  File "/home/templth/work/projects/**node.js/manning/node.js-in-**
> practice/source-code/addons/**technique4/wscript", line 11, in build
>t = ctx.new_task_gen('cxx', 'shlib', 'node_addon')
>  File "/usr/local/bin/../lib/node/**wafadmin/Build.py", line 335, in
> new_task_gen
>ret = cls(*k, **kw)
>  File "/usr/local/bin/../lib/node/**wafadmin/Tools/ccroot.py", line 162,
> in __init__
>TaskGen.task_gen.__init__(**self, *k, **kw)
>  File "/usr/local/bin/../lib/node/**wafadmin/TaskGen.py", line 118, in
> __init__
>self.env = self.bld.env.copy()
> AttributeError: 'NoneType' object has no attribute 'copy'
>
> Thanks very muc for your help!
> Thierry
>
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscribe@**googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Re: Connection dies with ECONNREFUSED

[Jeremy Darling]

Notice I said process.on('error') and process.on('exit') NOT
connection.on(*).  If this is something that is happening lower than the
socket level you may not be able to catch it at the socket level.  Since
your getting an ECONREFUSED error after the socket is stableized (sp?) and
running I'd see if I couldn't catch the app error instead.

BTW: Are you using any IPC stuff in your code, if so you may be chasing the
wrong crash?  I've had that same error come from Hook's (unrelated I'm
sure) when trying to use fork instead of spawn.

 - Jeremy

On Wed, Feb 22, 2012 at 1:24 PM, Demián Andrés Rodriguez  wrote:

> But the thing is that now the connection ends without emitting any 'error'
> or 'end' event. I've registered a listener for every damn event the request
> & response emits, what am I missing?
>
> We are not behind a firewall:
>
> root@w5:/var/www/nsnode# lscpu
> Architecture:  x86_64
> CPU op-mode(s):32-bit, 64-bit
> CPU(s):16
> Thread(s) per core:2
> Core(s) per socket:4
> CPU socket(s): 2
> NUMA node(s):  2
> Vendor ID: GenuineIntel
> CPU family:6
> Model: 44
> Stepping:  2
> CPU MHz:   2399.956
> Virtualization:VT-x
> L1d cache:     32K
> L1i cache: 32K
> L2 cache:  256K
> L3 cache:  12288K
>
>
> On Wed, Feb 22, 2012 at 4:16 PM, Jeremy Darling 
> wrote:
>
>> OS, Num CPUs, Firewall or no Firewall, etc etc please.  Lots of things
>> can cause a connection to be terminated that are in and out of scope for
>> any application.
>>
>> As for catching you can use process.on('error') or process.on('exit') or
>> try{}catch(e){} and retry logic depending on where the line is getting cut.
>>
>>  - Jeremy
>>
>>
>> On Wed, Feb 22, 2012 at 10:01 AM, Rambo  wrote:
>>
>>> I'm also experiencing random disconnects without any emitted errors,
>>> that's just bizarre. I'm sure the server is not causing the disconnection.
>>> What could be happening?
>>>
>>> --
>>> 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 nodejs@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> nodejs+unsubscr...@googlegroups.com
>>> 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 nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Re: Connection dies with ECONNREFUSED

[Jeremy Darling]

OS, Num CPUs, Firewall or no Firewall, etc etc please.  Lots of things can
cause a connection to be terminated that are in and out of scope for any
application.

As for catching you can use process.on('error') or process.on('exit') or
try{}catch(e){} and retry logic depending on where the line is getting cut.

 - Jeremy

On Wed, Feb 22, 2012 at 10:01 AM, Rambo  wrote:

> I'm also experiencing random disconnects without any emitted errors,
> that's just bizarre. I'm sure the server is not causing the disconnection.
> What could be happening?
>
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Memory leak

[Jeremy Darling]

Are you using a custom web server or something like express?  What
type/level of caching are you using or did you implement for pages/stores?

This sounds a lot like a closure leak.

 - Jeremy

On Wed, Feb 22, 2012 at 8:24 AM, Chris Casey  wrote:

> Unfortunately I know the pattern very well.
> Somewhere in node it is storing all of the served pages.
> memory increasing by the number of pages served.
> Just can't figure out exactly where and how to stop it.
>
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Memory leak

[Jeremy Darling]

LOL I know the feeling, my servers just got an "Upgrade" to 2k8 R2 64 from
2k3 R2 64.  BIG difference especially from the admin side of things.
 Actually has been a painful migration for me as learning all the changes
from 2k3 to 2k8 was painful (we are a MS shop for the most part so I have
to "utilize" IIS's built in FTP and SSH :()

I'm assuming these are bare metal boxes and not VM's?  Are they also
dedicated and do you have Admin rights?  If so, you might try running a few
of the admin tools like Memory Diagnostic, running your app in PowerShell
and see if that helps (would point out if this is a STDOUT issue or not),
also try running Resource Monitor and monitoring your node.exe's running
with history enabled.  You might start to see a pattern.

Sorry I don't have a silver bullet here, but am more than willing to help
pop off ideas.

 - Jeremy

On Wed, Feb 22, 2012 at 7:43 AM, Chris Casey  wrote:

> This is running on windows server as a service but we have the same memory
> leak if we run it on the console.
> We manage our own logging which goes to file.
>
> The o/s version id server 2003 R2 x64 SP2 (yes, I know but I have no
> control over this)
>
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Automatically populate dependencies based on node_modules folder contents?

[Jeremy Darling]

Thanks for the answer, didn't know that myself :).  Might want to update
the docs you linked to as I don't actually see --save or -S mentioned
anywhere on that page or the install package page.  Though I could be
missing it.

On Tue, Feb 21, 2012 at 10:02 PM, Thomas Blobaum  wrote:

> yes.
>
> npm install package --save
> or npm install package -S
>
> http://npmjs.org/doc/
>
> Thomas Blobaum
> https://github.com/tblobaum
>
>
>
> On Tue, Feb 21, 2012 at 8:40 AM, dhruvbird  wrote:
>
>> Hello,
>>
>> While developing stuff, I tend to "npm install packageX" for packages
>> I want and then I need to manually add it to my package.json. Is there
>> a way to make npm do this for me automatically?
>>
>> Regards,
>> -Dhruv.
>>
>> --
>> 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 nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Memory leak

[Jeremy Darling]

What OS are you on and how are you running the parent and child processes?
 In Windows when running via console or startup script with lots of things
written to the console I've noticed that the OS starts to slow down on
console writes and tends to each tons of memory when under high
utilization.  In Linux (or if I redirect the output of the console in
Windows) I haven't seen any issue.

On Wed, Feb 22, 2012 at 7:19 AM, Chris Casey  wrote:

> I am having great problems tracking down a memory leak.
> I have dumped out my global and am sure that nothing is getting stored
> there so it has to be somewhere in nodes memory structures.
>
> Without being able to do snapshots due to the current state of the
> v8-profiler it is proving very difficult to find out where the problem is.
>
> I have done a complete memory dump and just looked at that in a text
> editor and it is clear that the memory leak involves the storage of the
> pages being returned.
> Not 100% sure whether this is on the webserver or child side but suspect
> the child which are permanently attached telnet connections.
> Closing the child and reopening certainly clears out the memory.
>
> Are there any problems with long term child processes. Maybe something
> related to a flush out of the child process STDOUT.
>
> On the http side every response end with response.end(); and I am
> assuming that that will clear out things on that side?
>
> Any suggestions would be gratefully received as this is now the main block
> on us doing a large scale roll-out.
>
>  --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Free nodejs services

[Jeremy Darling]

Here are some I've played with.  Takes a while to get invites, and in the
case of cloudno.de can be painful if you don't understand GIT very well
(I'm still learning), but it seems the better option IMHO so far

http://cloudno.de/
https://no.de/

 - Jeremy

On Mon, Feb 20, 2012 at 12:31 PM, Raffaele Sena  wrote:

> VMWare CloudFoundry also offer node.js hosting but I am not sure of
> what their free plan allows you to do.
>
> -- Raffaele
>
> On Mon, Feb 20, 2012 at 9:54 AM, Jann Horn 
> wrote:
> > 2012/2/20 Peng Yu :
> >> Hi,
> >>
> >> To set a nodejs service without setting up a website myself, could
> >> anybody recommend some free services?
> >
> > Well, there's heroku, which has kind of a free plan - you get a bit
> > more than one CPU-month per month. However, I think its node version
> > is pretty outdated (0.4.something). Also, there's nodejitsu, which atm
> > is free because it's in beta. It has an up-to-date node version and a
> > relatively active IRC channel. Oh, and there's nodester, but in my
> > experience, nodester isn't excatly good.
> >
> > Thise are the ones that immediately come to my mind.
> >
> > --
> > 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 nodejs@googlegroups.com
> > To unsubscribe from this group, send email to
> > nodejs+unsubscr...@googlegroups.com
> > 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Node as a CGI or FastCGI module

[Jeremy Darling]

I have a cloudnode account, but I've been going NUTS trying to figure out
how to separate my github git and my cloudnode git.  So far I can't get
anything to go to cloudnode, instead it all gets pushed to my public github
account :(

 - Jeremy

On Fri, Feb 17, 2012 at 1:11 PM, Kevin Burke  wrote:

> If you were just looking to play around, you could sign up for something
> like nodester (http://nodester.com/)
>
>
> On Fri, Feb 17, 2012 at 11:46 AM, Jeremy Darling  > wrote:
>
>> Honestly, I didn't realize there was a free EC2 instance.  Its been a few
>> years since I worked with EC2 but I do remember it was interesting.
>>
>> I had asked (on another board) about some type of node playground and
>> basically met with the "you need a dedicated server or EC2 instance"
>> answer.  Not wanting to put out any fundage at this point I figured I'd
>> look into CGI hosting options instead.  I already have hosting for other
>> sites and it seemed like a fit.
>>
>> I'll have to start some more googling around EC2 Micro and setting up
>> Node.  Any links to step by step articles would be greatly appreciated :)
>>
>>  - Jeremy
>>
>>
>> On Fri, Feb 17, 2012 at 12:22 PM, Matt  wrote:
>>
>>> On Fri, Feb 17, 2012 at 1:19 PM, Jeremy Darling <
>>> jeremy.darl...@gmail.com> wrote:
>>>
>>>> I realize the loss of async in the overall view and that it really
>>>> isn't ideal, but I'm just wanting to experiment a bit.  I also realize it
>>>> would be like running PHP in CGI mode, you loose a lot, but at least you
>>>> can play with the language a bit in a web environment :)
>>>
>>>
>>> But why not just get an EC2 micro instance (for free) and play how it's
>>> supposed to be used?
>>>
>>> --
>>> 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 nodejs@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> nodejs+unsubscr...@googlegroups.com
>>> 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 nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Node as a CGI or FastCGI module

[Jeremy Darling]

Honestly, I didn't realize there was a free EC2 instance.  Its been a few
years since I worked with EC2 but I do remember it was interesting.

I had asked (on another board) about some type of node playground and
basically met with the "you need a dedicated server or EC2 instance"
answer.  Not wanting to put out any fundage at this point I figured I'd
look into CGI hosting options instead.  I already have hosting for other
sites and it seemed like a fit.

I'll have to start some more googling around EC2 Micro and setting up Node.
 Any links to step by step articles would be greatly appreciated :)

 - Jeremy

On Fri, Feb 17, 2012 at 12:22 PM, Matt  wrote:

> On Fri, Feb 17, 2012 at 1:19 PM, Jeremy Darling 
> wrote:
>
>> I realize the loss of async in the overall view and that it really isn't
>> ideal, but I'm just wanting to experiment a bit.  I also realize it would
>> be like running PHP in CGI mode, you loose a lot, but at least you can play
>> with the language a bit in a web environment :)
>
>
> But why not just get an EC2 micro instance (for free) and play how it's
> supposed to be used?
>
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Node as a CGI or FastCGI module

[Jeremy Darling]

Never heard of those, but will take a look at them.

Thanks,
 - Jeremy

On Fri, Feb 17, 2012 at 12:08 PM, Louis Santillan wrote:

> Write to stdout (not stdin).
>
> SilkJS, v8cgi, may be more appropriate for your needs if you're in an
> F/CGI environment.
>
> The basics of CGI are:
>
> * Web server calls an executable
> * Print headers (including required content type)
> * Print two (or more) new lines ("\n")
> * Print content (should match "Content-type: " header)
> * Returns to web server without causing an exception, crashing, or
> returning an error code
>
> -L
>
> On Fri, Feb 17, 2012 at 9:50 AM, Brett Ritter 
> wrote:
> > On Fri, Feb 17, 2012 at 12:44 PM, Jeremy Darling
> >  wrote:
> >> I know you can build c/c++ applications as a CGI app, but I just can't
> seem
> >> to figure out how to build node as a CGI app.  Anyone had any real luck
> with
> >> this or know where to get the binaries (Linux hosting of course)?
> >
> > I'm a little confused...basic CGI just involves calling the program.
> > So to make a node.js program usable as a CGI would be a matter of
> > writing a node.js program that output HTML to STDIN, and having a
> > shebang line at the top to call the node interpreter (which is why
> > node has to be on the server).  It seems this is not what you're
> > looking for...can you explain in more detail?
> >
> > (I'll assume you realize that the only benefit to calling node in this
> > way is writing in javascript - you'd be losing most of the async
> > benefits)
> >
> > --
> > Brett Ritter / SwiftOne
> > swift...@swiftone.org
> >
> > --
> > 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 nodejs@googlegroups.com
> > To unsubscribe from this group, send email to
> > nodejs+unsubscr...@googlegroups.com
> > 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Node as a CGI or FastCGI module

[Jeremy Darling]

I realize the loss of async in the overall view and that it really isn't
ideal, but I'm just wanting to experiment a bit.  I also realize it would
be like running PHP in CGI mode, you loose a lot, but at least you can play
with the language a bit in a web environment :)

 - Jeremy

On Fri, Feb 17, 2012 at 11:50 AM, Brett Ritter wrote:

> On Fri, Feb 17, 2012 at 12:44 PM, Jeremy Darling
>  wrote:
> > I know you can build c/c++ applications as a CGI app, but I just can't
> seem
> > to figure out how to build node as a CGI app.  Anyone had any real luck
> with
> > this or know where to get the binaries (Linux hosting of course)?
>
> I'm a little confused...basic CGI just involves calling the program.
> So to make a node.js program usable as a CGI would be a matter of
> writing a node.js program that output HTML to STDIN, and having a
> shebang line at the top to call the node interpreter (which is why
> node has to be on the server).  It seems this is not what you're
> looking for...can you explain in more detail?
>
> (I'll assume you realize that the only benefit to calling node in this
> way is writing in javascript - you'd be losing most of the async
> benefits)
>
> --
> Brett Ritter / SwiftOne
> swift...@swiftone.org
>
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[nodejs] Node as a CGI or FastCGI module

[Jeremy Darling]

I know this has been asked before and I've been all over Google trying to
find the solution, but I'm just not having any luck.  Is there a .cgi or
.fcgi application for node?  I've seen the tootallnate references to
server.cgi that makes the assumption that node is installed on the server
to begin with, but this doesn't really help if node isn't installed.

I know you can build c/c++ applications as a CGI app, but I just can't seem
to figure out how to build node as a CGI app.  Anyone had any real luck
with this or know where to get the binaries (Linux hosting of course)?

 - Jeremy

-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en