Agree.
Still think that HTTP should be into core because most of us need it and we
need some common ground to be able to mix and match modules. But it should
be as lean and efficient as possible. Your experiment is interesting!
But why put object mode streams into core? That's clearly a
Hi,
I've tried this change:
https://github.com/paddybyers/node/commit/ab8ca2779c0a767063ff4af6097e40e1d2207e4e
which seems to make things build ok on xcode.
... but broke the make build :(
I think this works:
https://github.com/paddybyers/node/commit/9efd361ca5510cca92365ee6471e75b6d3091e98
Thanks a lot.
On Thursday, March 28, 2013 12:05:25 AM UTC+8, Nathan Rajlich wrote:
The options are not all properly documented as well as they should be.
Some not at all. It's on my TODO list, but patches welcome of course.
On Wed, Mar 27, 2013 at 5:16 AM, Jerry Yin
On April 2, 2013 4:03:23 PM TJ Koury tjko...@gmail.com wrote:
Good advice; I've used dependency injection when building shared backbone
views that need to initialize different client-side libraries.
I'm not a fan of AMD in general; I think the app should be delivered
complete in one request, so
I recently discovered NAP (https://github.com/craigspaeth/nap/) and I must
say that after trying about 10 different tools I think this is the best one
out there. Straightforward, minimal configuration, supports css and js
preprocessors (stylus, less, coffee, etc), and template precompilation
I'm learning node and decided to build a web crawler. It works well enough,
but when i try to crawl a site like reddit I start running into severe
memory issues.
The goal of the crawler would be to take a provided url, crawl the page,
gather all internal links and crawl them, then store all
On Wed, Apr 3, 2013 at 11:14 AM, Jorge Chamorro jo...@jorgechamorro.com wrote:
I can't compile my module without headers... they're missing, is it a bug?
No, it's intentional. There is a feature request for adding a `make
install-dev` target:
https://github.com/joyent/node/issues/5112
I want
On 03/04/2013, at 11:40, Ben Noordhuis wrote:
On Wed, Apr 3, 2013 at 11:14 AM, Jorge Chamorro jo...@jorgechamorro.com
wrote:
I can't compile my module without headers... they're missing, is it a bug?
No, it's intentional.
How so? May I ask why? They used to come even with the pre-built
On 03/04/2013, at 11:40, Ben Noordhuis wrote:
https://github.com/joyent/node/issues/5112
I'm in the Saying 'just get used to our build system' is easy to say when
you're not the one with an exiting build system camp.
--
( Jorge )();
--
--
Job Board: http://jobs.nodejs.org/
Posting
On Wed, Apr 3, 2013 at 12:14 PM, Jorge Chamorro jo...@jorgechamorro.com wrote:
On 03/04/2013, at 11:40, Ben Noordhuis wrote:
On Wed, Apr 3, 2013 at 11:14 AM, Jorge Chamorro jo...@jorgechamorro.com
wrote:
I can't compile my module without headers... they're missing, is it a bug?
No, it's
use ejs https://github.com/visionmedia/ejs#includes its as much plain html
as you wish
Am Dienstag, 2. April 2013 19:56:25 UTC+2 schrieb // ravi:
On Apr 2, 2013, at 11:38 AM, Dominik Kienzler
d.kie...@dominik-kienzler.de javascript: wrote:
you need SOME kind of template engine if you
We are migrating from node 0.8 to node 0.10. Currently we see this:
node: ../deps/uv/src/unix/stream.c:483: uv__server_io: Assertion `events ==
1' failed.
on a CentOS 6.4 machine if we use the cluster module
If we do not use the cluster module it runs fin on CentOS too.
On OS X (developer
Hello,
I am trying to code a stream which can handle two sorts of byte-frames:
1. Byte-frames which are transmitted byte-after-byte
2. Byte-frames which are transmitted together (so that the chunk contains
two byte-frames)
My current implementation is stuck at the second point.
This issue is
Wonderful, thanks guys. The last commit by Paddy works out for me.
Regards,
Marcus
Am Mittwoch, 3. April 2013 09:37:54 UTC+2 schrieb paddybyers:
Hi,
I've tried this change:
https://github.com/paddybyers/node/commit/ab8ca2779c0a767063ff4af6097e40e1d2207e4e
which seems to make things build
On Wed, Apr 3, 2013 at 1:17 PM, Michael michael.wit...@cinovo.de wrote:
We are migrating from node 0.8 to node 0.10. Currently we see this:
node: ../deps/uv/src/unix/stream.c:483: uv__server_io: Assertion `events ==
1' failed.
on a CentOS 6.4 machine if we use the cluster module
If we do
The one downside I have noted with node-gyp is how much of a pain it is to
bundle some package as a dependency that includes a different build manager
like cmake. Perhaps that is the situation here.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
Anyone have any suggestions? Naming of .finish to something else? Would
anyone use this if I published it? I thought the most useful part of it is
that it can interop with regular callback style.
On Monday, April 1, 2013 1:10:28 PM UTC-4, Paul wrote:
Btw, you also CAN return the promise from
On Apr 3, 9:37 am, Bradley Meck bradley.m...@gmail.com wrote:
The one downside I have noted with node-gyp is how much of a pain it is to
bundle some package as a dependency that includes a different build manager
like cmake. Perhaps that is the situation here.
Well, you can either gypify the
Jade does seem to be the most popular on npm, with 235k downloads in the
last month, but it's not a landslide (handlebars has 74k, EJS has 59k, and
there are *four pages* of packages with the keyword template).
Is everyone burnt out arguing over template engines?
I suspect so. Since your
Garbage collection in node can/should be automatic. When you run into
memory pressure, the garbage collector will run. You can expose it and call
it yourself if you absolutely must control when the garbage collector is
run, but in general you shouldn't need to do that. The garbage collector
Hi
How can I use this code in nodejs mysql
update users set point=point+100 where id=1
--
--
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
That gist is a 404.
On Wed, Apr 3, 2013 at 5:08 AM, Bodo Kaiser bodo.kai...@enabre.com wrote:
Hello,
I am trying to code a stream which can handle two sorts of byte-frames:
1. Byte-frames which are transmitted byte-after-byte
2. Byte-frames which are transmitted together (so that the chunk
thanks bruno. it wasn't my intention to suggest this for core though - it
is a module and a very experimental one so let's not have any more
discussion about what should and shouldn't be in core on this thread
please. the intention is to build a module that will be small and very fast
as a
Thanks for the responses.
@arunoda -- I've used half a dozen templating engines, and have already
made my choice. I was simply questioning why lately Jade is not only the
most often recommended choice, but seems to be the only recommendation. I
have to assume it is because people recommend what
@tauren
For us it really works the opposite way - we filter out people who are not
willing/able to learn Coffeescript/Stylus/Jade - it is a good test to
judge if people are flexible. I trained a few people in those technologies
and the good ones were productive within a day or two, with some
Thanks for the reply Paul!
I am going to try implementing your solution and see if it helps! I'll let
you know what I find!
On Wednesday, April 3, 2013 7:14:03 AM UTC-7, Paul wrote:
Garbage collection in node can/should be automatic. When you run into
memory pressure, the garbage collector
On Wed, Apr 3, 2013 at 9:24 AM, Isaac Schlueter i...@izs.me wrote:
That gist is a 404.
Delete the extra a at the end of the URL:
https://gist.github.com/bodokaiser/5300586
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
Hi, fellows
I need a node js soap web service client in which I can set web service
timeout. I review some modules, bot none of them has this option. Does
anybody know whether exists such module where I can set timeout.
Thanks in advance.
--
--
Job Board: http://jobs.nodejs.org/
Posting
So i took your advice and things got a little better. Then I took out the
jquery module i was using to parse the html out of the request response and
everything started working! Seems like jquery was retaining references to
all the html it had parsed!
Thanks for the help!
On Wednesday, April
Jorge, would you like a pull request for TAGG to build with node-gyp? I
really don't understand your reluctance to give it a try, but I'll do the
dirty work for you if you'd rather.
On Wed, Apr 3, 2013 at 7:03 AM, mscdex msc...@gmail.com wrote:
On Apr 3, 9:37 am, Bradley Meck
I'm trying to decide on the right way to have node services listening on
ports 80 and/or 443. The two main approaches I'm considering are:
1. process started as superuser, server listens on port 80/443, process
downgrades to regular user on 'listening' event
2. process started as
3. Make sure to not do anything even slightly wrong!
This part is really hard. I don't think I've written a single stream module
that complies with it. (and I've written 60. it's really hard)
On Mon, Apr 1, 2013 at 5:39 PM, Isaac Schlueter i...@izs.me wrote:
Compared with the stuff that you
2013.04.03, Version 0.10.3 (Stable)
* npm: Upgrade to 1.2.17
* child_process: acknowledge sent handles (Fedor Indutny)
* etw: update prototypes to match dtrace provider (Timothy J Fontaine)
* dtrace: pass more arguments to probes (Dave Pacheco)
* build: allow building with dtrace on osx (Dave
Paddy, that patch looks good to me I think. Care to submit a pull request
upstream?
On Wed, Apr 3, 2013 at 5:13 AM, Marcus marcus.suemn...@gmail.com wrote:
Wonderful, thanks guys. The last commit by Paddy works out for me.
Regards,
Marcus
Am Mittwoch, 3. April 2013 09:37:54 UTC+2 schrieb
On Wed, Apr 3, 2013 at 1:53 PM, Ken ken.woodr...@gmail.com wrote:
For me the advantage to 1 is the port and user logic is self contained,
and the service knows the real port that it is exposed on (i.e. calling
server.address() returns { port: 80 }). (This matters to me because I'd
like
I almost always front it with nginx unless I need WebSockets, then I use
iptables.
*I know that the latest nginx has WS support, but from my tests it doesn't
fully work or I configured it incorrectly*
--
Dav Glass
davgl...@gmail.com
blog.davglass.com
+ Windows: n. - The most successful
Dude, tell me about it! Even the streams in core were a total mess!
Having a single place where most of the implementation lives is a huge win.
On Wed, Apr 3, 2013 at 11:06 AM, Jake Verbaten rayn...@gmail.com wrote:
3. Make sure to not do anything even slightly wrong!
This part is really
On Apr 3, 2013, at 12:39 PM, Tauren Mills tau...@tauren.com wrote:
I tried out a completely logic-less engine called Plates [3], but it was far
too buggy at the time. I haven't used transparency [4] yet, but it appears
very similar to plates. Unfortunately, I doubt I would use it since it
I was recently excited to find out that V8 is starting work on adding
generators support. Then I heard about asm.js and looked into Firefox's
*Monkey (OdinMonkey, SpiderMonkey, etc.) series of JS engines. Performance
is good, they've already implemented many ECMAScript 6 features, and now
On Wed, Apr 3, 2013 at 4:08 PM, cpprototypes cpprototy...@gmail.com wrote:
Looking at all this, it feels like V8 is falling behind and stagnant.
Also Google is working on Dart which is a competitor to JS technologies.
Mozilla seems to be all in on JS tech instead of divided like Google.
I
My main problem is not with JS but having native modules break if we do
this. V8's C++ API is significantly easier to use than the other JS VMs
when I have done experiments, however, that C++ API makes some assumptions
that are not always true across JS Core, Nitro, or the Monkey engines.
I think this might be of interest:
https://github.com/creationix/luvmonkey
quoting:
This project is an effort to create a custom SpiderMonkey runtime that
has libuv built-in. This will give it very node.js-like semantics, but
using a different JavaScript engine.
2013/4/3 cpprototypes
I would love to see luvmonkey finished. Once the core spidermonkey -
libuv bindings were complete, the rest could be implemented in pure JS on
top. Someone could clone the node.js APIs in pure JS on top of luvmonkey.
From what I know about node's development, changing engines will never
happen
Yep. Native node modules use V8 calls directly, so any existing native bindings
would need to be rewritten.
On Wednesday, 3 April, 2013 at 1:55 PM, Tim Caswell wrote:
I would love to see luvmonkey finished. Once the core spidermonkey - libuv
bindings were complete, the rest could be
Hi!
I'm developing on a large project on ARM processor with NodeJS.
This project uses several native addons.
I can manually build each addons with the simple
*nodegyp -arch arm rebuild*
*
*
command without any problem.
However, when I install these addons with `npm install` and it fails with
Hi all,
Apologies for the tediously high-level app developer question...
Has anyone come across any modules for managing multi-page workflows for
Node?
Cheers,
Richard
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
You should be able to do:
npm install --arch=arm
On Wed, Apr 3, 2013 at 2:49 PM, Tim Wu changti...@gmail.com wrote:
Hi!
I'm developing on a large project on ARM processor with NodeJS.
This project uses several native addons.
I can manually build each addons with the simple
*nodegyp
On Wed, Apr 3, 2013 at 10:55 PM, Tim Caswell t...@creationix.com wrote:
I would love to see luvmonkey finished. Once the core spidermonkey -
libuv bindings were complete, the rest could be implemented in pure JS on
top. Someone could clone the node.js APIs in pure JS on top of luvmonkey.
Hi,
Is there currently a way to automatically require module before executing
any other scripts (or have .rc/profile javascript file executed on
startup)?
Something like this: `node -r /path/to/myhelpers.js test.js` - same as
having implicit `require(/path/to/myhelpers.js)` as first line in
Hi everyone!
First idea:
do.js
for (var k=2; kprocess.argv.length; k++) {
require(process.argv[k]);
}
one.js
console.log(1)
two.js
console.log(2)
Run
node do.js ./one.js ./two.js
Maybe, instead of explicit ./ in arguments, use path.combine of current dir
in require
Angel Java Lopez
I'm having issue setting up a node app as a service under Fedora 17.
If I start the app/service manually by using:
node server.js
All works fine, the server starts and uses almost no CPU.
But this needs to be an always running service that needs to be restarted
if it crashes and needs to be
On Thu, Apr 4, 2013 at 3:00 AM, node newbie karl.brid...@gmail.com wrote:
I'm having issue setting up a node app as a service under Fedora 17.
If I start the app/service manually by using:
node server.js
All works fine, the server starts and uses almost no CPU.
But this needs to be an
Hello again Marc :)
I'm investigating a possibility to use
https://github.com/flite/winston-graylog2 in my project. And found that it
has become orphan
recentlyhttps://github.com/flite/winston-graylog2/commit/8836d0f80f3d464f8ebe1d46be823c7d543aa138
.
Along with that, it seems that the project
And also... have you compared your project with these:
https://github.com/egorFiNE/node-graylog
https://github.com/stelcheck/node-graylog2
https://github.com/robertkowalski/gelf-node
?
воскресенье, 7 октября 2012 г., 6:38:27 UTC+7 пользователь wavded написал:
https://github.com/wavded/graygelf
It may be worth pointing out that the V8/*Monkey comparison isn't totally
fair here. While it's true that Mozilla has done an amazing job at
implementing all the new ES5/6/7/.next goodness quickly, this is partially
due to the fact that they've been implementing new features before they
were
Suppose you build a node clone with mozilla js engine and you can use
asm.js, would that, to some extend, reduce the need of native addons?
Ps: +1 on kickstarter.
El 03/04/2013 21:23, Stephen Belanger cyruzdr...@gmail.com escribió:
To Kickstarter! :O
On 3 Apr 2013 17:12, Ben Noordhuis
Thanks for your reply.
Is that strace output from your node process or node-supervisor's?
Good point, I didn't think about that - I just checked and it is indeed
the node supervisor and not the target process!
Which makes sense why I don't have issues when starting it without the
Seems like ur process getting crashed while its trying to start.
Try to see the app's stderr.
On Thursday, April 4, 2013, Ben Noordhuis wrote:
On Thu, Apr 4, 2013 at 3:00 AM, node newbie karl.brid...@gmail.com
wrote:
I'm having issue setting up a node app as a service under Fedora 17.
If
Solved (or worked around).
The problem seems to be the way that supervisor works.
If anyone else has this issue check this thread:
https://github.com/isaacs/node-supervisor/issues/76 which led me to this
thread: https://github.com/isaacs/node-supervisor/issues/71 where they
mention a fork of
I think this is a little out of scope for node-core, some test runners for
example do automatically include various bootstraps and/or globals (chai in
particular comes to mind). Having this in included as a CLI flag would need
to have some serious points about why this would be beneficial over
Also https://github.com/mhart/gelfling
and https://github.com/mhart/gelf-stream :-)
On Thursday, 4 April 2013 12:57:10 UTC+11, Alexey Kupershtokh wrote:
And also... have you compared your project with these:
https://github.com/egorFiNE/node-graylog
https://github.com/stelcheck/node-graylog2
61 matches
Mail list logo
