But then, integrating the custom protocol might not be possible right? The
custom protocol is used for admin purposes. This is currently a python
codebase. We are porting it to nodejs. So the client wants to keep the
architecture same.
On Wednesday, 6 February 2013 19:04:11 UTC-8, bryce...@gmai
I hope you guys find great success with your powers combined! Appreciate
all you do for node core.
On Thursday, February 7, 2013 2:10:11 PM UTC-8, Bert Belder wrote:
>
> Hello everyone,
>
> As you may have noticed Ben, me and a couple of other guys started a new
> company called StrongLoop. We'r
On Feb 7, 8:41 pm, Kevin Baker wrote:
> I don't think these are the correct init functions, though? Looking
> athttps://www.cloudkick.com/blog/2010/aug/23/writing-nodejs-native-exte...
> for example and from Ben's response suggests a separate init() call
> that I cannot find anywhere in node-sqli
On Thu, Feb 7, 2013 at 6:41 PM, Jorge Chamorro wrote:
> On 07/02/2013, at 22:03, Kevin Baker wrote:
>
>> Unfortunately the library that is getting built doesn't work in the target
>> environment:
>>
>> root@device:/usr/lib/node_modules/npm/node_modules/sqlite3# node
>> > var sqlite3 = require('./
You should check it now. I just upgraded it to include simple load balancing
(instead of round-robin rotation): https://github.com/racbart/node-clusterpool
--
Bartosz Raciborski
On Thursday, 7 February 2013 at 16:18, Envy wrote:
> That's a great start, I'll probably build on top of that! Th
On 07/02/2013, at 22:03, Kevin Baker wrote:
> Unfortunately the library that is getting built doesn't work in the target
> environment:
>
> root@device:/usr/lib/node_modules/npm/node_modules/sqlite3# node
> > var sqlite3 = require('./node-sqlite3.node').verbose();
> Error: /usr/lib/node_modules/
and 0.8.17 is what I yam...
On Thursday, February 7, 2013 7:26:39 PM UTC-5, am_p1 wrote:
>
> So most of the time request.abort from inside setTimeout drives only the
> request error callback and gets "socket hang up". No problem and I call my
> routine again recursively to reconnect to the serve
So most of the time request.abort from inside setTimeout drives only the
request error callback and gets "socket hang up". No problem and I call my
routine again recursively to reconnect to the server in the big sky. Works
great.
But some of the time request.abort from inside setTimeout drives
On Thu, Feb 7, 2013 at 10:03 PM, Kevin Baker wrote:
> Hello all,
>
> I am working on Node.JS's OpenEmbedded support for a project here, test
> platform is Yocto "danny"/armv7a-vfp-neon-poky-linux-gnueabi/OMAP3730.
>
> So far I have updated the recipe to v0.8.15 and it builds, compiles, and
> runs
On Thu, Feb 7, 2013 at 10:02 PM, Sven Knuth wrote:
> at least I found the reason for the abuse.
>
> node.js starts many tests and one test
> (test/simple/test-dgram-send-error.js) is sending 1000-Request to random IPs
> to test the error handling, because the IPs should be unreachable, because
> i
Hey Everybody,
I released all the remaining NodeConf tickets yesterday :)
Everything there is to know about NodeConf is up at http://www.nodeconf.com/
-Mikeal
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You
I love you Bert.
Cheers,
Fedor.
On Fri, Feb 8, 2013 at 2:27 AM, Nuno Job wrote:
> Really excited for you guys!
>
> Best of luck, cant wait to see the great things coming out of this!
>
> Nuno
>
> Sent from my iPhone
>
> On Feb 7, 2013, at 10:10 PM, Bert Belder wrote:
>
> Hello everyone,
>
> A
Hi,
I have a node.js web application where I need process some mongodb
records (something like 20k records).
For each record I will do some processing and then write it back to the
database.
My code looks like this (not valid code just the idea) :
db.mycol.find({}, function(err, records)
Really excited for you guys!
Best of luck, cant wait to see the great things coming out of this!
Nuno
Sent from my iPhone
On Feb 7, 2013, at 10:10 PM, Bert Belder wrote:
> Hello everyone,
>
> As you may have noticed Ben, me and a couple of other guys started a new
> company called StrongLoo
Hello all,
I am working on Node.JS's OpenEmbedded support for a project here, test
platform is Yocto "danny"/armv7a-vfp-neon-poky-linux-gnueabi/OMAP3730.
So far I have updated the recipe to v0.8.15 and it builds, compiles, and
runs node correctly, with support for npm and pure js libraries. I p
Hello everyone,
As you may have noticed Ben, me and a couple of other guys started a new
company called StrongLoop. We're now offering consulting and training for
all things node. There are also some products in the pipeline but I'm not
going to spill the beans yet - you can follow
@strongloop
Hello everyone,
As you may have noticed Ben, me and a couple of other guys started a new
company called StrongLoop. We're now offering consulting and training for all
things node. There are also some products in the pipeline but I'm not going to
spill the beans yet - you can follow @stronglo
Sounds like the test needs a process.chdir() somewhere. Post an issue, please.
On Thu, Feb 7, 2013 at 1:17 PM, TJ wrote:
> I've triggered a bug in the test suite when working from the out-of-tree
> build directory.
>
> The bug is in test/simple/test-fs-realpath.js:268:test_relative_input_cwd()
I've triggered a bug in the test suite when working from the out-of-tree build
directory.
The bug is in test/simple/test-fs-realpath.js:268:test_relative_input_cwd()
In particular the assumption that process.cwd() and common.tmpDir are directly
related causes
var entry = common.tmpDir.substr(
at least I found the reason for the abuse.
node.js starts many tests and one test
(test/simple/test-dgram-send-error.js) is sending 1000-Request to random IPs
to test the error handling, because the IPs should be unreachable, because
its RANDOM.
But due to ipv4 shortage many existing hosts have
The following changes since commit 2b81cc4238cd90b4831e2c5258f129a465eab80f:
Makefile: Add automatic out-of-tree build support (2013-02-07 17:25:11 +)
are available in the git repository at:
git://github.com/iam-TJ/node.git out-of-tree-builds-auto
for you to fetch changes up to 433da47a
Static Web Framework for Node.js. Enjoy!
http://asset-rack.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 t
Hi
>> I need to built very simple application for file synchronization (like
>> dropbox or google drive) it should do three things:
Sorry not node but maybe take a look at git-annex assistant
(http://git-annex.branchable.com/assistant/). Linux and OSX work but
Windows not yet. If you know that OS
> Do you realize how insulting that is?
It's Marak - did you expect different? He's not known for his communication
skills on this list :)
On Thu, Feb 7, 2013 at 12:42 PM, Mark Hahn wrote:
> Do you realize how insulting that is?
>
>
> On Wed, Feb 6, 2013 at 10:17 PM, Marak Squires wrote:
>
>>
It's not a great idea to do this in Node due to the UI requirements you
have. There's a couple of UI options out there for Node but none of them
are great, and none of them will give you access to the system tray (or
menu bar on Mac).
I've written a Dropbox-like tool in node (for mirroring files o
I decided to tackle the harder solution: making out-of-tree builds automatic.
The patches are lighter and I've separated them out into discrete changes. My
only
concern is I needed to touch the Gyp generator for Makefiles to make this
possible
(Gyp's messing with relative paths everywhere preven
2013.02.07, Version 0.9.9 (Unstable)
* tls: port CryptoStream to streams2 (Fedor Indutny)
* typed arrays: only share ArrayBuffer backing store (Ben Noordhuis)
* stream: make Writable#end() accept a callback function (Nathan Rajlich)
* buffer: optimize 'hex' handling (Ben Noordhuis)
* dns, care
Thanks for the feedback Daniel. I will try to explain how I arrived at the
current design.
The one change I might suggest is not to have message delivery not be a
> method on the actor. That is instead of writing "tom.tell('bob', message);"
> it would either 1) use the director "director.tell('bob
It seems node.js available on all major platforms (Mac, Unix, MS).
I need to built very simple application for file synchronization (like
dropbox or google drive) it should do three things:
- One-click installation, so node.js should be be bundled with app (not
required to be installed separate
Verify the hash of whatever you downloaded.
http://nodejs.org/dist/v0.8.19/SHASUMS.txt
On 02/07/2013 06:30 PM, Sven Knuth wrote:
> another try before giving up:
>
> I started the nodes.js self test with "make test". ( I think it is
> an self test, because I didn't found a description of the test
Do you realize how insulting that is?
On Wed, Feb 6, 2013 at 10:17 PM, Marak Squires wrote:
> I'm not the one who posted the link to BIg and started asking questions.
>
> On Thu, Feb 7, 2013 at 11:41 AM, Ruben Tan wrote:
>
>> In this case, should we just lock this thread or delete it, since no
@Ben
This is a standard Solaris 10 shell installed with the system. /bin/sh
links to /sbin/sh but I don't think there is a way of checking which
version is it (/sbin/sh --version doesn't work, just runs the shell). The
file itself shows date Sep 22 2010 (which is probably when it has been
packa
On Feb 7, 2013, at 10:30, Sven Knuth wrote:
> I started the nodes.js self test with "make test". ( I think it is an self
> test, because I didn't found a description of the test)
>
> And what happens then? It is testing and everything is fine. At one point,
> the python script tools/test.py (t
On Thu, Feb 7, 2013 at 4:54 PM, Grzegorz Junka wrote:
> Hi, I'm trying to install node.js on Solaris 10. The binary distribution
> that can be downloaded from node.js website is compiled on Solaris 11 and
> doesn't work on Solaris 10 (libsocket.so.1: version 'SUNW_1.7' not found).
Packages for So
On Thu, Feb 7, 2013 at 5:54 PM, Grzegorz Junka wrote:
> Hi, I'm trying to install node.js on Solaris 10. The binary distribution
> that can be downloaded from node.js website is compiled on Solaris 11 and
> doesn't work on Solaris 10 (libsocket.so.1: version 'SUNW_1.7' not found).
>
> I tried to c
Hi, I'm trying to install node.js on Solaris 10. The binary distribution
that can be downloaded from node.js website is compiled on Solaris 11 and
doesn't work on Solaris 10 (libsocket.so.1: version 'SUNW_1.7' not found).
I tried to compile from sources but I am getting this error:
/bin/sh: syn
another try before giving up:
I started the nodes.js self test with "make test". ( I think it is an self
test, because I didn't found a description of the test)
And what happens then? It is testing and everything is fine. At one point,
the python script *tools/test.py* (the script started by "m
That's a great start, I'll probably build on top of that! Thanks!
On Thursday, February 7, 2013 2:26:29 AM UTC+1, Bartosz Raciborski wrote:
>
> You just inspired me to write a module for this:
> https://github.com/racbart/node-clusterpool
>
> It's basically a cluster of pools. You put multiple sl
Hi All,
I just released the second version of OneJS, my alternative of browserify.
It now lets you split your bundles to multiple files and load them
asynchronously.
Check it out here; https://github.com/azer/onejs
Best
Azer
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
http
The one change I might suggest is not to have message delivery not be a
method on the actor. That is instead of writing "tom.tell('bob', message);"
it would either 1) use the director "director.tell('bob', message)" or 2)
have the director return an actor reference (to allow runtime switching
betwe
Best to post these Mongoose specific questions on the dedicated Google
group:
https://groups.google.com/forum/?fromgroups#!forum/mongoose-orm
-- Daniel R. [http://danielr.neophi.com/]
On Wed, Feb 6, 2013 at 4:12 PM, Declan Elcocks wrote:
> I have a Team Schema holding details about teams, an
Thanks was looking for something like this.
On Wednesday, February 6, 2013 12:09:10 AM UTC-5, Jacob wrote:
>
> Hello everyone, I wanted to share a module I've been working on called
> Federation.
>
> Federation is a message network that works cross-process and cross-host.
>
> - Project http://und
has somebody tried to reimplement some existing logic using do?
I would like to know if there are any troubles and if yes to see the code.
Thanks,
Oleg
Am 02.02.2013 um 20:21 schrieb Jake Verbaten :
> triggering an error when done is called more times then expected is a
> difficult design.
Or better yet, redirect :80 to https://yourserver.com and wholly avoid
mixed secure/insecure code paths.
// a simple listener to redirect 80 to https
http.createServer(function (req, res) {
res.writeHead(301, {"Location": "https://"; + HOST + req.url});
res.end();
}).listen(80);
On
Ismael,
You will end up writing a lot of custom code for that, or at least I did.
Would be interesting to see if someone wrote a performance testing
streaming parser framework?
Hopefully :)
My code is MIT, so use all you want :) I also wrote a blog post about how I
made the performance measurem
Lots of information for me too :)
But I created a strings parser for XCode .strings file. In these files you
can found multilines comment /* */ or /** */, simple line comment // , and
strings key-value separated by '=' and ended by ';'.
For this parser I need events or callbacks when comments,
Would like to help, but got lost in the information here.
What is it that you are trying to do again? :) Test a parser? It doesn't
matter what you use, it matters most the coverage you have.
Go find a similar parser in another language that has a ton of tests. Make
sure they all pass (e.g. I used
I'm working on something similar too actually, based on zeromq. Not sure if
our objectives intersect enough to merge the two projects though. Give me
some time to play around with federation first. :)
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/
Hi people!
Ah, Ismael, now I have more context. And sorry for my English, too.
Well, your code reflects your ideas, and I didn't try it yet. But for the
final purpose, it looks a bit overwhelming. Try Floby's ideas.
The only difference in my position: you still don't need parse stream, so
you ca
It is true that it does not answer my question, but your answer makes me
ask more questions and review the logic and improve myself.
Your links will help me a lot I think.
Thank you.
Le jeudi 7 février 2013 10:15:44 UTC+1, Floby a écrit :
>
> I know this doesn't quite answer your question but I f
I know this doesn't quite answer your question but I find your approach a
bit heavy for such (apparently) simple files to parse. Instanciating
objects for each state will not help performance if that's what your aiming
at.
This leads me to my shameless plug: you should have a look at my
tokeniz
51 matches
Mail list logo
