actually my hosting provider has fixed 256MB RAM for one application mysql
will be handled by other ram. so what do you think how much request nodejs
can service in a month in this ram?
That will be fine initially.
@WIL MILLER why dont you share your experience about how to actually
A few random thoughts...
Unless you have specific inter-operability requirements, or something else,
I would consider looking at different database solutions. Mongo melds
nicely to JavaScript - natively dealing with json data transport (bson
internally) and processing js functions internally. But
On Tue, Oct 9, 2012 at 10:12 PM, Isaac Schlueter i...@izs.me wrote:
You can also use canonical-host for this: [...]
Thanks! It's good to know the options.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received
Too nice : )
I could be misguided, but I find that I gravitate toward low-level IO, like
the interface that fs provides. The cool thing about fs (not the streams,
but the posix functions), is that I can wrap them in whatever abstraction
makes sense at the time. I can create my own stream
wait, what? *all* readable streams have a write() callback now?
-Mikeal
On Oct 10, 2012, at October 10, 20127:05 AM, Isaac Schlueter i...@izs.me
wrote:
Ok, fair enough. Writable stream write() callbacks landed on streams2 branch.
On Tue, Oct 9, 2012 at 6:52 PM, khs4473 khs4...@gmail.com
Hi All,
I am very new to Node, please provide some guidelines on start up,
prerequisites.
Thanks,
Ketan
--
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
Hi,
I am using *Window 7* and I have installed Node.js from
http://nodejs.org/download/ (*Windows Installer (.msi) 64 bit*). Is there
anything apart from this needs to be installed to work with Node?
In Node window, even if I just type console.log('hello'); and press
enter, it prints the
Hello,
Pushed a couple of middlewares for connect:
https://github.com/jondot/connect-cdncache
https://github.com/jondot/connect-ping
Hope this helps
-
@jondot
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You
On Wed, Oct 10, 2012 at 9:29 AM, ketan mehta ketanmah...@gmail.com wrote:
Hi,
I am using Window 7 and I have installed Node.js from
http://nodejs.org/download/ (Windows Installer (.msi) 64 bit). Is there
anything apart from this needs to be installed to work with Node?
In Node window,
I've added the node_modules folder to my .gitignore file, which works fine
thanks to NPM Shrinkwrap (after deploying I need to run npm install using
the shrinkwrap.json file).
However, I've got some private modules now that I won't publish to NPM. I
would like to require these modules like the
You have 2 choices:
1. Change your .gitignore
2. Change your require() calls
Example for 1:
(instead of having node_modules)
node_modules/a
node_modules/b
...
Example for 2:
(in case you put your module in priv_modules)
var xpto = require(./priv_modules/xpto);
--
Diogo Resende
On
-
# Hands on node.js
Wed Oct 24, 2012, 7 PM - 10 PM
Please RSVP: http://www.eventbrite.com/event/4571262770
Bocoup Loft
Guiffre's Building
355 Congress St
Boston, MA 02210
* come out and meet the Boston node.js community: everyone is welcome
* get help setting up your machine
If you are ok with putting them in github then you can just add dependency
that points to a github tarball, for example
dependencies: {
foo: https://github.com/USER/foo/tarball/TAG;
}
where TAG is a named git tag (version), a branch name, or a commit sha. I
would recommend using a named git
Thanks.
I think I will simply go with changing my .gitignore to list all NPM
published modules, assuming this is acceptable behavior.
Tom
Op woensdag 10 oktober 2012 22:32:13 UTC+7 schreef Diogo Resende het
volgende:
You have 2 choices:
1. Change your .gitignore
2. Change your require()
No, all *writable* streams in core will, and the Writable base class will
provide it.
On Wednesday, October 10, 2012, Mikeal Rogers wrote:
wait, what? *all* readable streams have a write() callback now?
-Mikeal
On Oct 10, 2012, at October 10, 20127:05 AM, Isaac Schlueter
For private github repos
git+ssh://g...@github.com:username/repo.git
On Wednesday, October 10, 2012 8:09:27 AM UTC-7, Tom wrote:
I've added the node_modules folder to my .gitignore file, which works fine
thanks to NPM Shrinkwrap (after deploying I need to run npm install using
the
I suggest using a proper git repository. Use bitbucket.org who provides
free private repos, and reference them in your package json like this
git+ssh://g...@bitbucket.org:USER/PROJECT.git
On Wednesday, October 10, 2012 8:09:27 AM UTC-7, Tom wrote:
I've added the node_modules folder to my
var nowww = require('nowww');
connect.use(nowww);
I believe `express.use(nowww);` should work the same.
https://npmjs.org/package/nowww
https://github.com/coolaj86/steve/tree/master/connect-nowww
On Wednesday, October 10, 2012 8:22:32 AM UTC-6, Felix E. Klee wrote:
On Tue, Oct 9, 2012 at
typo. should be
connect.use(nowww())
On Wednesday, October 10, 2012 12:13:55 PM UTC-6, CoolAJ86 wrote:
var nowww = require('nowww');
connect.use(nowww);
I believe `express.use(nowww);` should work the same.
https://npmjs.org/package/nowww
So, here's part of a totally subjective, non-comprehensive list of
frustrations and best practices I've been collecting. Some are based on
personal experience and others are ideals from the node community that I'm
trying to incorporate.
I'm looking for more tips like this. Please share your
To get a decent answer you probably need to ask a more specific question.
On Wednesday, 10 October 2012 16:07:23 UTC+10, ketan mehta wrote:
Hi All,
I am very new to Node, please provide some guidelines on start up,
prerequisites.
Thanks,
Ketan
--
Job Board: http://jobs.nodejs.org/
That's pretty awesome. There's a couple of items I'd like to discuss, the
first one being ...
Always wrap callbacks in process.nextTick if they're not behind an async
operation. Simple.
This doesn't seem necessary to me and it seems inefficient and dangerous.
I make sure to write in a style
Check nodejs.org and/or google nodejs tutorial.
On Wed, Oct 10, 2012 at 11:56 AM, Tim Oxley sec...@gmail.com wrote:
To get a decent answer you probably need to ask a more specific question.
On Wednesday, 10 October 2012 16:07:23 UTC+10, ketan mehta wrote:
Hi All,
I am very new to Node,
Always wrap callbacks in process.nextTick if they're not behind an async
operation. Simple.
Oh, of course… to clarify:
If a module is possibly going to execute an async operation, ensure any
otherwise synchronous callbacks are inside in process.nextTick. i.e. If
it's sync it should always
OK, I realize now that all your points were about writing good modules. I
took your point from the view of the module user, not the author. I really
should read more carefully.
On Wed, Oct 10, 2012 at 12:14 PM, Tim Oxley sec...@gmail.com wrote:
Always wrap callbacks in process.nextTick if
Usual links mentioned in other emails:
Ryan Dahl presentation:
http://www.youtube.com/watch?v=jo_B4LTHi3I
Online book:
http://www.nodebeginner.org/
Other resources
Felix's Node.js Beginners Guide http://nodeguide.com/beginner.html
Felix's Node.js Convincing the boss guide
I'm in a situation where I'm serving a handful of 1MB static files to
clients. We have our logic that determines which file to serve in node, so
putting nginx or varnish in front of our node app isn't a great solution.
Our first naive attempt was to load the entire file into a Buffer and cache
Great writeup! Most these points are right on. I take issue with a
couple of them and have a different opinion. (That's right, this is
my opinion, not saying you're wrong)
## Inconsistent sync/async
When functions are sometimes sync and sometimes async lead to hard to
use apis, subtle bugs
I find that using a simple Stream.prototype.pipe from the file stream
to the response stream works equally great for fast and slow clients.
What really speeds things up is making sure to implement conditional
and partial requests. (If-Modified-Since, If-No-Match, Range, ...)
Node's stream pipe
On http://jstherightway.com/ there's some links about Node.js, from
beginning to advanced topics.
Hope it helps! :-)
On Wed, Oct 10, 2012 at 4:21 PM, Angel Java Lopez ajlopez2...@gmail.comwrote:
Usual links mentioned in other emails:
Ryan Dahl presentation:
There's also a book that I like: http://smashingnode.com/
On Wed, Oct 10, 2012 at 5:32 PM, William Oliveira sudowill...@gmail.comwrote:
On http://jstherightway.com/ there's some links about Node.js, from
beginning to advanced topics.
Hope it helps! :-)
On Wed, Oct 10, 2012 at 4:21 PM,
Go for it.
a) Go for it. This won't affect me, and if by chance it does, I don't
mind putting 'binary' args here and there.
b) Please wait. Mark the API as unstable in 0.10, but don't change it
until 0.12.
c) I have no opinion, because I don't use the crypto API directly.
--
On Wednesday, October 10, 2012 6:29:51 PM UTC+2, Michael Nutt wrote:
I'm in a situation where I'm serving a handful of 1MB static files to
clients. We have our logic that determines which file to serve in node, so
putting nginx or varnish in front of our node app isn't a great solution.
b)
Remember the sys/util situation in 0.8?
1. What is the cost of keeping sys throwing?
2. What is the cost of putting it back?
This is a different type of change entirely but I think the general
idea of the questions is still applicable:
1. What is the cost of this change being made as soon
34 matches
Mail list logo
