[nodejs] Re: [ANN] pkgcloud

[Tim Dickinson]

whats the support for the OpenStack API?

On Friday, November 23, 2012 3:07:39 PM UTC-5, Nuno Job wrote:
>
> Hi, 
>
> One of the main objectives we have at Nodejitsu is that developers should 
> not change their code according to different OSs / or cloud providers. We 
> can run on Rackspace, Joyent, aws, etc. We believe our users will stay for 
> our better software and support —not because they are "locked in".
>
> To make this possible we have been working on a module called `pkgcloud` 
> for the past year or so.
>
> Today, we decided to open source this module. This reinforces our 
> commitment to open-source, and to every one of you as nodejs developers.
>
> * http://blog.nodejitsu.com/introducing-pkgcloud
>
> `pkgcloud` is a hassle free way to talk to all these providers (plus 
> azure) using the same apis, so migrating from amazon to joyent is as simple 
> as replacing a json property in your code!
>
> `pkgcloud` doesnt depend on the sdks from specific providers, and instead 
> has a subset of what those sdks provide implemented with mikeal/request. 
>
> This way you know that you are not using something that "only works on 
> amazon". The tests that are run are also the same across different 
> providers, which is designed to keep us honest.
>
> I leave you all with an idea: With `pkgcloud` you can create a cli that 
> works for all cloud providers the same. That is pretty cool, especially 
> considering the state of most of the sdks out there.
>
> Hope you guys enjoy it, feedback is welcome.
> Nuno (& a very proud nodejitsu team)
>

-- 
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: [ANN] pkgcloud

[Tim Dickinson]

Oh yes I forgot that rackspace was OpenStack.

Thanks

On Monday, November 26, 2012 1:15:44 PM UTC-5, Nuno Job wrote:
>
> Sorry, got sent while I was still writing — feel free to post issues if 
> you find any with the implementation.
>
> Thank you,
> Nuno
>
>
> On Mon, Nov 26, 2012 at 6:09 PM, Nuno Job 
> > wrote:
>
>> Can you clarify your question?
>>
>> It supports rackspace, which is open stack.
>>
>> Feel fre
>>
>>
>> On Mon, Nov 26, 2012 at 6:00 PM, Tim Dickinson 
>> 
>> > wrote:
>>
>>> whats the support for the OpenStack API?
>>>
>>>
>>> On Friday, November 23, 2012 3:07:39 PM UTC-5, Nuno Job wrote:
>>>>
>>>> Hi, 
>>>>
>>>> One of the main objectives we have at Nodejitsu is that developers 
>>>> should not change their code according to different OSs / or cloud 
>>>> providers. We can run on Rackspace, Joyent, aws, etc. We believe our users 
>>>> will stay for our better software and support —not because they are 
>>>> "locked 
>>>> in".
>>>>
>>>> To make this possible we have been working on a module called 
>>>> `pkgcloud` for the past year or so.
>>>>
>>>> Today, we decided to open source this module. This reinforces our 
>>>> commitment to open-source, and to every one of you as nodejs developers.
>>>>
>>>> * 
>>>> http://blog.nodejitsu.com/**introducing-pkgcloud<http://blog.nodejitsu.com/introducing-pkgcloud>
>>>>
>>>> `pkgcloud` is a hassle free way to talk to all these providers (plus 
>>>> azure) using the same apis, so migrating from amazon to joyent is as 
>>>> simple 
>>>> as replacing a json property in your code!
>>>>
>>>> `pkgcloud` doesnt depend on the sdks from specific providers, and 
>>>> instead has a subset of what those sdks provide implemented with 
>>>> mikeal/request. 
>>>>
>>>> This way you know that you are not using something that "only works on 
>>>> amazon". The tests that are run are also the same across different 
>>>> providers, which is designed to keep us honest.
>>>>
>>>> I leave you all with an idea: With `pkgcloud` you can create a cli that 
>>>> works for all cloud providers the same. That is pretty cool, especially 
>>>> considering the state of most of the sdks out there.
>>>>
>>>> Hope you guys enjoy it, feedback is welcome.
>>>> Nuno (& a very proud nodejitsu team)
>>>>
>>>  -- 
>>> 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

[nodejs] Re: What happens to hook.io?

[Tim Dickinson]

What about the forked version people had? I dont really know how GitHub 
works but shouldn't other people have a copy of the code? Just recreate the 
repo.

Take a look. https://github.com/TooTallNate/hook.io

On Tuesday, November 27, 2012 12:54:42 AM UTC-5, Arunoda Susiripala wrote:
>
> Hi,
>
> I've notice that hook.io's source code has been 
> removedfrom Github.
> Anyone know why it has been removed?
> Or is it moved to some other place?
>
> -- 
> Arunoda Susiripala
>
> @arunoda 
> https://github.com/arunoda
> http://www.linkedin.com/in/arunoda
>
>  

-- 
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: What happens to hook.io?

[Tim Dickinson]

Yeah this is a great idea. lets close the thread and not fix the 
core problem. Who is going to re-fork the repo so users can start using the 
software again.



On Tuesday, November 27, 2012 12:54:42 AM UTC-5, Arunoda Susiripala wrote:
>
> Hi,
>
> I've notice that hook.io's source code has been 
> removedfrom Github.
> Anyone know why it has been removed?
> Or is it moved to some other place?
>
> -- 
> Arunoda Susiripala
>
> @arunoda 
> https://github.com/arunoda
> http://www.linkedin.com/in/arunoda
>
>  

-- 
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: Federation: A Distributed Message Network Module

[Tim Dickinson]

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://underflow.ca/federation/
> - Github https://github.com/jacobgroundwater/federation
>
> It's loosely actor-based; you can create as many actors as you wish, and 
> give them any names you like. Actors can send message to each other by 
> name, regardless of their location on the network.
>
> On a single process, Federation works with zero configuration. It can be 
> expanded to multiple processes quite easily with a single routes file. 
> Federation separates out host-to-host-wiring from the application logic. 
> You can re-arrange your hosts without rewriting your code.
>
> Federation supports peer-to-peer messaging, as well as routed messaging. 
> The actual network transport is done via HTTP, or Axon. New transport 
> protocols can also be written quickly.
>
> My goal with Federation was to build upon a library like Axon. Axon is 
> great for peer-to-peer messaging, but what I needed was a way to multiplex 
> messages over a single socket. The project started as a multiplexer, but 
> grew to fit what I think is a good set of use-cases. 
>
> I would love for people to give it a test. I have included several key 
> examples that are immediately runnable. For the multi-process examples I 
> recommend starting the example with Node-Foreman. Examples include:
>
> - simple, one-off messaging
> - request-reply pattern
> - routed messaging via central server
> - multi-process via axon
> - multi-process via http
>
> This project is in its initial stages, and I would love to find some early 
> adopters. I am happy to answer any questions, thanks!
>
> - Jacob Groundwater
>
>

-- 
-- 
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.

[nodejs] [ANN] Raft v0.2.0

[Tim Dickinson]

Raft is a PaaS for node. Raft supports a wide range of functions to run 
multi-user, multi-app, mulit-infa. A lot of inspiration has come from the 
great people at nodejitu, nodester and AppFog.

Raft features

   - App spawn-er
  - Dependency support with npm
  - File-system chroot
  - Scalable
  - Methods start, stop, restart
  - Viewing app logs, npm logs and more.
  - App load and memory usage
  - Multi versions of node 0.4.x+
   - Mulit transport RPC
  - nssocket
  - socket.io
  - More to come
   - Proxy/Balancer
  - Scalable
  - Request stats
  - Bandwidth stats
  - Per app bandwidth stats
  - Per app request stats
   - User Accounts
  - Create, Remove, Update
   
Main Site: http://mangoraft.com/
GitHub: https://github.com/MangoRaft/Raft

Let me know what you think.
Thanks
Tim

-- 
-- 
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.

[nodejs] Re: Node v0.9.9 (Unstable)

[Tim Dickinson]

The next version is 1.0.0 or 0.10.0?

When would it be released?

On Thursday, February 7, 2013 2:36:09 PM UTC-4, Isaac Schlueter wrote:
>
> 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, cares: don't filter NOTIMP, REFUSED, SERVFAIL (Ben Noordhuis) 
>
> * readline: treat bare \r as a line ending (isaacs) 
>
> * readline: make \r\n emit one 'line' event (Ben Noordhuis) 
>
> * cluster: support datagram sockets (Bert Belder) 
>
> * stream: Correct Transform class backpressure (isaacs) 
>
> * addon: Pass module object to NODE_MODULE init function (isaacs, Rod 
> Vagg) 
>
> * buffer: slow buffer copy compatibility fix (Trevor Norris) 
>
> * Add bytesWritten to tls.CryptoStream (Andy Burke) 
>
>
> Source Code: http://nodejs.org/dist/v0.9.9/node-v0.9.9.tar.gz 
>
> Macintosh Installer (Universal): 
> http://nodejs.org/dist/v0.9.9/node-v0.9.9.pkg 
>
> Windows Installer: http://nodejs.org/dist/v0.9.9/node-v0.9.9-x86.msi 
>
> Windows x64 Installer: 
> http://nodejs.org/dist/v0.9.9/x64/node-v0.9.9-x64.msi 
>
> Windows x64 Files: http://nodejs.org/dist/v0.9.9/x64/ 
>
> Linux 32-bit Binary: 
> http://nodejs.org/dist/v0.9.9/node-v0.9.9-linux-x86.tar.gz 
>
> Linux 64-bit Binary: 
> http://nodejs.org/dist/v0.9.9/node-v0.9.9-linux-x64.tar.gz 
>
> Solaris 32-bit Binary: 
> http://nodejs.org/dist/v0.9.9/node-v0.9.9-sunos-x86.tar.gz 
>
> Solaris 64-bit Binary: 
> http://nodejs.org/dist/v0.9.9/node-v0.9.9-sunos-x64.tar.gz 
>
> Other release files: http://nodejs.org/dist/v0.9.9/ 
>
> Website: http://nodejs.org/docs/v0.9.9/ 
>
> Documentation: http://nodejs.org/docs/v0.9.9/api/ 
>
> Shasums: 
> ``` 
> 643c26c2fc0c9ddeee99d346af86a022e6b470bc  node-v0.9.9-darwin-x64.tar.gz 
> f3ffeb08ceab15fd24a33c8d1974be952177b623  node-v0.9.9-darwin-x86.tar.gz 
> 63d6ce5e4333a0cd203753a3153998076baa23a7  node-v0.9.9-linux-x64.tar.gz 
> f1008b823b6010bd3ed3fd4f422eac3af5bd61da  node-v0.9.9-linux-x86.tar.gz 
> 679b09328f1a0c3225286a891bb5b4de131777d6  node-v0.9.9-sunos-x64.tar.gz 
> 4253f2e976a05ee6ea6ecc3b583e942b812d0b86  node-v0.9.9-sunos-x86.tar.gz 
> 0436ee0e57d12d5fc53914f9157521427d016629  node-v0.9.9-x86.msi 
> 8a98bc39e9c99a1a1dad6f38a47f56eeb9ad6ecd  node-v0.9.9.pkg 
> af1deb80c79f256b319a727f8593740ff99cdbc8  node-v0.9.9.tar.gz 
> ab3db4d6ffab88bb1bab96ca8d2c6caf4625  node.exe 
> 56f5a3c72992463435f6649b31da81fd679e91ae  node.exp 
> e77f0097ce66317fc255b8e1642eaa675c190267  node.lib 
> 5ff7b6d7f1001383b4bd97e1315c67e7b223477d  node.pdb 
> 5b4dcf545eace51a4cae58e9c42b73604f6eb0f9  x64/node-v0.9.9-x64.msi 
> 43fd59cf0df5bdf21690a43a68a8f16160e28ec6  x64/node.exe 
> b4845d2318dd5b1030eeca02703d7f19ebf2ef15  x64/node.exp 
> 2726441e5ff354bc51a841fa9a5a193d39831ac0  x64/node.lib 
> df9083c37cf13109326df30df01e9692238ac381  x64/node.pdb 
> ``` 
>

-- 
-- 
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] Node v0.9.9 (Unstable)

[Tim Dickinson]

Yeah after posting I remembered that we are on 0.8.18

On Friday, February 8, 2013 11:10:29 AM UTC-4, Arunoda Susiripala wrote:
>
> you have to wait  some more :-)
>
> On Friday, February 8, 2013, Tim Dickinson wrote:
>
>> The next version is 1.0.0 or 0.10.0?
>>
>> When would it be released?
>>
>> On Thursday, February 7, 2013 2:36:09 PM UTC-4, Isaac Schlueter wrote:
>>>
>>> 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, cares: don't filter NOTIMP, REFUSED, SERVFAIL (Ben Noordhuis) 
>>>
>>> * readline: treat bare \r as a line ending (isaacs) 
>>>
>>> * readline: make \r\n emit one 'line' event (Ben Noordhuis) 
>>>
>>> * cluster: support datagram sockets (Bert Belder) 
>>>
>>> * stream: Correct Transform class backpressure (isaacs) 
>>>
>>> * addon: Pass module object to NODE_MODULE init function (isaacs, Rod 
>>> Vagg) 
>>>
>>> * buffer: slow buffer copy compatibility fix (Trevor Norris) 
>>>
>>> * Add bytesWritten to tls.CryptoStream (Andy Burke) 
>>>
>>>
>>> Source Code: 
>>> http://nodejs.org/dist/v0.9.9/**node-v0.9.9.tar.gz<http://nodejs.org/dist/v0.9.9/node-v0.9.9.tar.gz>
>>>  
>>>
>>> Macintosh Installer (Universal): http://nodejs.org/dist/v0.9.9/**
>>> node-v0.9.9.pkg <http://nodejs.org/dist/v0.9.9/node-v0.9.9.pkg> 
>>>
>>> Windows Installer: 
>>> http://nodejs.org/dist/v0.9.9/**node-v0.9.9-x86.msi<http://nodejs.org/dist/v0.9.9/node-v0.9.9-x86.msi>
>>>  
>>>
>>> Windows x64 Installer: http://nodejs.org/dist/v0.9.9/**
>>> x64/node-v0.9.9-x64.msi<http://nodejs.org/dist/v0.9.9/x64/node-v0.9.9-x64.msi>
>>>  
>>>
>>> Windows x64 Files: 
>>> http://nodejs.org/dist/v0.9.9/**x64/<http://nodejs.org/dist/v0.9.9/x64/> 
>>>
>>> Linux 32-bit Binary: http://nodejs.org/dist/v0.9.9/**
>>> node-v0.9.9-linux-x86.tar.gz<http://nodejs.org/dist/v0.9.9/node-v0.9.9-linux-x86.tar.gz>
>>>  
>>>
>>> Linux 64-bit Binary: http://nodejs.org/dist/v0.9.9/**
>>> node-v0.9.9-linux-x64.tar.gz<http://nodejs.org/dist/v0.9.9/node-v0.9.9-linux-x64.tar.gz>
>>>  
>>>
>>> Solaris 32-bit Binary: 
>>> http://nodejs.org/dist/v0.9.9/**node-v0.9.9-sunos-x86.tar.gz<http://nodejs.org/dist/v0.9.9/node-v0.9.9-sunos-x86.tar.gz>
>>>  
>>>
>>> Solaris 64-bit Binary: 
>>> http://nodejs.org/dist/v0.9.9/**node-v0.9.9-sunos-x64.tar.gz<http://nodejs.org/dist/v0.9.9/node-v0.9.9-sunos-x64.tar.gz>
>>>  
>>>
>>> Other release files: http://nodejs.org/dist/v0.9.9/ 
>>>
>>> Website: http://nodejs.org/docs/v0.9.9/ 
>>>
>>> Documentation: 
>>> http://nodejs.org/docs/v0.9.9/**api/<http://nodejs.org/docs/v0.9.9/api/> 
>>>
>>> Shasums: 
>>> ``` 
>>> 643c26c2fc0c9ddeee99d346af86a0**22e6b470bc 
>>>  node-v0.9.9-darwin-x64.tar.gz 
>>> f3ffeb08ceab15fd24a33c8d1974be**952177b623 
>>>  node-v0.9.9-darwin-x86.tar.gz 
>>> 63d6ce5e4333a0cd203753a3153998**076baa23a7 
>>>  node-v0.9.9-linux-x64.tar.gz 
>>> f1008b823b6010bd3ed3fd4f422eac**3af5bd61da 
>>>  node-v0.9.9-linux-x86.tar.gz 
>>> 679b09328f1a0c3225286a891bb5b4**de131777d6 
>>>  node-v0.9.9-sunos-x64.tar.gz 
>>> 4253f2e976a05ee6ea6ecc3b583e94**2b812d0b86 
>>>  node-v0.9.9-sunos-x86.tar.gz 
>>> 0436ee0e57d12d5fc53914f9157521**427d016629  node-v0.9.9-x86.msi 
>>> 8a98bc39e9c99a1a1dad6f38a47f56**eeb9ad6ecd  node-v0.9.9.pkg 
>>> af1deb80c79f256b319a727f859374**0ff99cdbc8  node-v0.9.9.tar.gz 
>>> ab3db4d6ffab88bb1bab96ca8d**2c6caf4625  node.exe 
>>> 56f5a3c72992463435f6649b31da81**fd679e91ae  node.exp 
>>> e77f0097ce66317fc255b8e1642eaa**675c190267  node.lib 
>>> 5ff7b6d7f1001383b4bd97e1315c67**e7b223477d  node.pdb 
>>> 5b4dcf545eace51a4cae58e9c42b73**604f6eb0f9  x64/node-v0.9.9-x64.msi 
>>> 43fd59cf0df5bdf21690a43a68a8f1**6160e28ec6  x64/node.exe 
>>> b4845d2318dd5b1030eeca02703d7f**19ebf2ef15  x64/node.exp 
>>> 2726441e5ff354bc51a841fa9a5a19**3d39831

[nodejs] Re: Need an "offline" npm-style repository - what's a good approach?

[Tim Dickinson]

You might want to 
read https://blog.caurea.org/2012/01/31/local-npm-registry-mirror.html

On Monday, February 18, 2013 2:23:05 PM UTC-4, andy wrote:
>
> Apologies in advance because I've only glanced at this problem, but we 
> work in a unique environment where we have no Internet connectivity.
> So, with our Java apps, we run an instance of Artifactory on our LAN and 
> load it by running an instance that is connected, which we then export and 
> bring into the 'offline' instance. That gives us a sort of mirror of Java 
> dependencies for maven and what not when we're developing.
>
> Is there anything like Artifactory for npm? Do I need to roll my own 
> somehow (i.e. would a simple WebDAV server work or is it more complex)? 
>
> I've glanced at Mike's node-reggie idea so maybe that is a place to start (
> https://github.com/mbrevoort/node-reggie).
>
> We don't need anything fancy - just a way to add npm modules to a project 
> without having to check them in or pass around a giant .zip copy with all 
> possible repos...etc. (Right now I just have a "node_modules_for_work" 
> folder where I load up a ton of modules, then I zip that up and bring it 
> in.)
>
> I'm happy to go off and do some reading/digging, so links to similar 
> ideas/attempts are appreciated. 
>
> Thanks,
>
> Andy
>

-- 
-- 
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.

[nodejs] Install for specific version of node through npm

[Tim Dickinson]

I have a build of node version 0.6.12 but my main install of node is 0.8.20

This is my output

[bob@bob-workstation test]$ /tests/tmp/node/0.6.12/bin/npm install daemon
npm http GET https://registry.npmjs.org/daemon
npm http 304 https://registry.npmjs.org/daemon

> daemon@0.5.1 preinstall /test/node_modules/daemon
> bash ./install

Checking for program g++ or c++  : /usr/bin/g++ 
Checking for program cpp : /usr/bin/cpp 
Checking for program ar  : /usr/bin/ar 
Checking for program ranlib  : /usr/bin/ranlib 
Checking for g++ : ok  
Checking for node path   : not found 
Checking for node prefix : ok /usr/local 
'configure' finished successfully (0.044s)
Waf: Entering directory `/test/node_modules/daemon/build'
[1/2] cxx: src/daemon.cc -> build/Release/src/daemon_1.o
[2/2] cxx_link: build/Release/src/daemon_1.o -> build/Release/daemon.node
Waf: Leaving directory `/test/node_modules/daemon/build'
'build' finished successfully (0.237s)
daemon@0.5.1 ./node_modules/daemon
[bob@bob-workstation test]$ ls ./node_modules/daemon/lib/
daemon.js  daemon.v0.8.20.node
[bob@bob-workstation test]$ 


Im trying to install daemon for node version 0.6.12 not 0.8.20

-- 
-- 
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] Install for specific version of node through npm

[Tim Dickinson]

How would i override PATH so i dont have to set the version for each node 
install that i have.
So I could have node 0.6.12 or 0.8.12 or 0.9.12 I dont really want to set 
PATH for each version im running. I might have more then one instance of 
npm and node running at once. setting 0.6.12 in the PATH might now work 
when wanting to run 0.8.12

On Wednesday, February 27, 2013 5:52:34 PM UTC-5, Ben Noordhuis wrote:
>
> On Wed, Feb 27, 2013 at 11:44 PM, Tim Dickinson 
> > 
> wrote: 
> > I have a build of node version 0.6.12 but my main install of node is 
> 0.8.20 
> > 
> > This is my output 
> > 
> > [bob@bob-workstation test]$ /tests/tmp/node/0.6.12/bin/npm install 
> daemon 
> > npm http GET https://registry.npmjs.org/daemon 
> > npm http 304 https://registry.npmjs.org/daemon 
> > 
> >> daemon@0.5.1 preinstall /test/node_modules/daemon 
> >> bash ./install 
> > 
> > Checking for program g++ or c++  : /usr/bin/g++ 
> > Checking for program cpp : /usr/bin/cpp 
> > Checking for program ar  : /usr/bin/ar 
> > Checking for program ranlib  : /usr/bin/ranlib 
> > Checking for g++ : ok 
> > Checking for node path   : not found 
> > Checking for node prefix : ok /usr/local 
> > 'configure' finished successfully (0.044s) 
> > Waf: Entering directory `/test/node_modules/daemon/build' 
> > [1/2] cxx: src/daemon.cc -> build/Release/src/daemon_1.o 
> > [2/2] cxx_link: build/Release/src/daemon_1.o -> 
> build/Release/daemon.node 
> > Waf: Leaving directory `/test/node_modules/daemon/build' 
> > 'build' finished successfully (0.237s) 
> > daemon@0.5.1 ./node_modules/daemon 
> > [bob@bob-workstation test]$ ls ./node_modules/daemon/lib/ 
> > daemon.js  daemon.v0.8.20.node 
> > [bob@bob-workstation test]$ 
> > 
> > 
> > Im trying to install daemon for node version 0.6.12 not 0.8.20 
>
> Make sure that the directory that contains the 0.6.12 binary and 
> scripts comes first on your PATH. 
>

-- 
-- 
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.

[nodejs] Re: [ANN| mongo-metrics - Mongo backed metrics engine

[Tim Dickinson]

Oh very nice!

On Saturday, February 16, 2013 12:34:11 PM UTC-5, Arunoda Susiripala wrote:
>
> Hi,
>
> I just released mongo-metrics - https://github.com/arunoda/mongo-metrics
>
> Which is metrics tracking and aggregation tool/module build on top of the 
> MongoDB.
> Hope you guys find it useful.
>
> Thank You.
>
> -- 
> Arunoda Susiripala
>
> @arunoda 
>  https://github.com/arunoda
> http://www.linkedin.com/in/arunoda
>  

-- 
-- 
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.

[nodejs] Re: Install for specific version of node through npm

[Tim Dickinson]

The example I shows was just the basic concept of what im trying to do. 

What I'm really doing is spawning a new process from within node. each 
spawn might be a different version of node and i need to install 
all dependencies for the specific version of node. So each spawn has its 
own dependencies and its own version. To give you wan idea you can see this 
file https://github.com/MangoRaft/Raft/blob/v3/raft/common/spawn.js

>I'd recommend looking into using nvm or another tool like it to manage 
multiple versions of node.
I have looked at nvm but i dont know if it does what I want. I dont 
know enough about nvm to really see if its a fit for what i want. With nvm 
can i spawn two version of node at the same time? Or do i have to set the 
version then spawn that version then set the other and spawn with other 
version?

On Wednesday, February 27, 2013 5:44:40 PM UTC-5, Tim Dickinson wrote:
>
> I have a build of node version 0.6.12 but my main install of node is 0.8.20
>
> This is my output
>
> [bob@bob-workstation test]$ /tests/tmp/node/0.6.12/bin/npm install daemon
> npm http GET https://registry.npmjs.org/daemon
> npm http 304 https://registry.npmjs.org/daemon
>
> > daemon@0.5.1 preinstall /test/node_modules/daemon
> > bash ./install
>
> Checking for program g++ or c++  : /usr/bin/g++ 
> Checking for program cpp : /usr/bin/cpp 
> Checking for program ar  : /usr/bin/ar 
> Checking for program ranlib  : /usr/bin/ranlib 
> Checking for g++ : ok  
> Checking for node path   : not found 
> Checking for node prefix : ok /usr/local 
> 'configure' finished successfully (0.044s)
> Waf: Entering directory `/test/node_modules/daemon/build'
> [1/2] cxx: src/daemon.cc -> build/Release/src/daemon_1.o
> [2/2] cxx_link: build/Release/src/daemon_1.o -> build/Release/daemon.node
> Waf: Leaving directory `/test/node_modules/daemon/build'
> 'build' finished successfully (0.237s)
> daemon@0.5.1 ./node_modules/daemon
> [bob@bob-workstation test]$ ls ./node_modules/daemon/lib/
> daemon.js  daemon.v0.8.20.node
> [bob@bob-workstation test]$ 
>
>
> Im trying to install daemon for node version 0.6.12 not 0.8.20
>

-- 
-- 
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.

[nodejs] Raft - Open-Source PaaS

[Tim Dickinson]

Raft - Open-Source PaaS

The idea behind raft and mangoraft.com is to give the node community a 
fully-featured Platform as a Service (PaaS). Raft gives you a provision of 
CPU, memory, disk space and bandwidth. From this the sky's the limit in 
what can be build. Sites and services ranging from the weekend projects to 
large scale production sites are able to take advantage of raft. Full 
instances of a UNIX system is available from with in the running 
allocation. Each application is run in its own chroot jail. Keeping all 
other applications sharing the system safe.
Convenient

Deploy your application in under 30 seconds. Fast deploys mean even more 
time to build and debug your applications.
Scalable

Run more than one instance of your application. A global footprint is no 
problem, run your application independent to any LaaS providers or even run 
it on your own hardware.
Distributed

To take advantage of today's cloud provider. raft has been built to run on 
more then one server that is running in more than one data center. Raft 
uses a distributed event system allowing you to run more than one instance 
of each service. So if you wanted to host tens of thousands of your 
favorite express app, raft can do it.
Open-source

All the code is open source. If you would like to run your own copy of raft 
you can. Even better then the git repo is that you can install it all with 
one command. "npm install raft-hooks -g" this will install a program called 
hooks. Take a look at "hooks -h" for help on how to use the client.
Status

Lots of work is been done on Raft. If you would like to know more please 
drop us a line!
Installation

Install raft

$ npm install raft

Install raft-hooks

$ sudo npm install raft-hooks -g

Core

The core features of raft are a set of hooks that allow ease of adding more 
Feature latter one. With a distributed process module adding and removing 
part is no problem
FeatureStatusCommentDistributed Event SystemcompleteThe system used to 
distribute event to all processesRoutercompleteThe router is in working 
state. Over all seems to work well.SpawnercompleteWorking copy of the 
spawn/spawner. All feature are in placeLoggercompleteFull package logging 
in real-time.StatscompleteLoad and memory usage for each spawn.Deploy/SnapShot 
ServerincompleteDeploy server creating each package snapshot.API Server
incompleteREST api server for managing user 
packages
Hooks

Raft-hooks are a set of command line programs for running raft.
CommandStatusCommenthooks hubcompleteThe main event serverhooks router
completestart the router processhooks spawncompletestart the spawn processhooks 
loggercompletestart the logger process
Cli

The comamnd-line program for managing packages hosted by raft
CommandStatusCommentraft deloyincompleteDeploy to 
raft
Addons

Other hooks that could be added on latter. Any action could be an addons to 
the system.
AddonsStatusCommentWebUIincompleteWebui will be the web console to raft. 
Allowing users to manage their app from the webEmailerincompleteEmail addon 
for each packageffmpegincompleteVideo encoding service / Image resizeing

The raft services are a set of hooks that make up the event system. It 
consists of 2 modules that are on npm. The first is "raft" and the second 
is "raft-hooks". Raft is the core components of the system as a whole. 
Raft-hooks is a command program to run the event system.
The hub

The hub service is the event distributor for all other services. The hub 
service is the first service that must start. The idea behind the hub to to 
start it and forget it. You will never have to interact with the hub once 
it has started.
Router

The Router is used to proxy http and web-sockets to the corresponding 
application. You can run more than one instance of the Router. The idea is 
that the Router sit in front all other services and applications and proxy 
from a URL to host:port. If you where to query test.mangoraft.com your 
request would first go the the Router then be piped to the next application 
port. The Router does not have to be on the same server your applications, 
as long as the two processes can connect to one another thats all it take. 
To deal with many hundreds of thousands of request you may run 5, 10, 25+ 
instances of the Router. So that would be 25+ servers running an instance 
each of the balanRoutercer. The Router uses the native node.js cluster API 
to take full advantage of multicore processors.

Re: [nodejs] Raft - Open-Source PaaS

[Tim Dickinson]

CloudFoundry is a very nice peace of software and might just be best the 
open-source paas systems. I have taken a lot of inspirations from 
how cloudfoundry/appfog is built. The idea of the event system 
that Raft uses comes from how cloudfoundry's system works. Having a mesh 
like network or servers that can be used to host node applications. 

Its hard to say that Raft has any advantage over cloudfoundry. The 
only advantage's that raft has would only effect a node.js program 
developer. The Raft's stack is written in node and its make to host 
node applications. Any add-ons for raft would be written in node. So if you 
where someone who is hosting 10, 20, 100+ node applications then Raft could 
be a better fit.

Some other thing that are nice is the one-line install of a PaaS system. 
>From starting the hardware to hosting an application is very easy.

I would say Raft is more of a tool to the developer then a service.

On Friday, March 1, 2013 2:28:28 AM UTC-5, Charlie Edward wrote:
>
> Looks awesome.  What is the advantage versus cloudfoundry, and other open 
> source solutions?
>
> On Fri, Mar 1, 2013 at 7:16 AM, Tim Dickinson 
> 
> > wrote:
>
>> Raft - Open-Source PaaS
>>
>> The idea behind raft and mangoraft.com is to give the node community a 
>> fully-featured Platform as a Service (PaaS). Raft gives you a provision of 
>> CPU, memory, disk space and bandwidth. From this the sky's the limit in 
>> what can be build. Sites and services ranging from the weekend projects to 
>> large scale production sites are able to take advantage of raft. Full 
>> instances of a UNIX system is available from with in the running 
>> allocation. Each application is run in its own chroot jail. Keeping all 
>> other applications sharing the system safe.
>>  <https://github.com/MangoRaft/Raft#convenient>Convenient 
>>
>> Deploy your application in under 30 seconds. Fast deploys mean even more 
>> time to build and debug your applications.
>>  <https://github.com/MangoRaft/Raft#scalable>Scalable 
>>
>> Run more than one instance of your application. A global footprint is no 
>> problem, run your application independent to any LaaS providers or even run 
>> it on your own hardware.
>>  <https://github.com/MangoRaft/Raft#distributed>Distributed 
>>
>> To take advantage of today's cloud provider. raft has been built to run 
>> on more then one server that is running in more than one data center. Raft 
>> uses a distributed event system allowing you to run more than one instance 
>> of each service. So if you wanted to host tens of thousands of your 
>> favorite express app, raft can do it.
>>  <https://github.com/MangoRaft/Raft#open-source>Open-source 
>>
>> All the code is open source. If you would like to run your own copy of 
>> raft you can. Even better then the git repo is that you can install it all 
>> with one command. "npm install raft-hooks -g" this will install a program 
>> called hooks. Take a look at "hooks -h" for help on how to use the client.
>>  <https://github.com/MangoRaft/Raft#status>Status 
>>
>> Lots of work is been done on Raft. If you would like to know more please 
>> drop us a line!
>>  <https://github.com/MangoRaft/Raft#installation>Installation 
>>
>> Install raft
>>
>> $ npm install raft
>>
>> Install raft-hooks
>>
>> $ sudo npm install raft-hooks -g
>>
>>  <https://github.com/MangoRaft/Raft#core>Core
>>
>> The core features of raft are a set of hooks that allow ease of adding 
>> more Feature latter one. With a distributed process module adding and 
>> removing part is no problem
>> Feature StatusComment Distributed Event Systemcomplete The system used 
>> to distribute event to all processesRouter completeThe router is in 
>> working state. Over all seems to work well. SpawnercompleteWorking copy 
>> of the spawn/spawner. All feature are in place Logger completeFull 
>> package logging in real-time. StatscompleteLoad and memory usage for 
>> each spawn. Deploy/SnapShot Server incompleteDeploy server creating each 
>> package snapshot. API ServerincompleteREST api server for managing user 
>> packages  <https://github.com/MangoRaft/Raft#hooks>Hooks
>>
>> Raft-hooks are a set of command line programs for running raft.
>> Command StatusComment hooks hub completeThe main event server hooks 
>> router completestart the router process hooks spawn completestart the 
>> spawn process hooks logger completestart the logger process 
>> <https://github.com/MangoRaft/Raft#cli>Cli
>&g

Re: [nodejs] Re: Sticky sessions using the new cluster API?

[Tim Dickinson]

I read in the docs some place. I cant seems to find it again. Can anyone say 
anything about where information might be on this?

On Tuesday, June 26, 2012 10:54:04 PM UTC-4, Dominic wrote:
> I understand that the cluster api works by passing a file descriptor
> 
> to the worker process.
> 
> 
> 
> is it possible pass a file descriptor after you have started reading from it?
> 
> 
> 
> On Wed, Jun 27, 2012 at 9:30 AM, Isaac Schlueter  wrote:
> 
> > For sessions, I recommend using redis with redsess:
> 
> > https://github.com/isaacs/redsess
> 
> >
> 
> > On Tue, Jun 26, 2012 at 7:58 AM, Bradley Meck  
> > wrote:
> 
> >> +1 for not including this, sticky sessions are painful when they become the
> 
> >> least common denominator.
> 
> >>
> 
> >>
> 
> >> On Tuesday, June 26, 2012 8:48:00 AM UTC-5, Ben Noordhuis wrote:
> 
> >>>
> 
> >>> On Tue, Jun 26, 2012 at 6:02 AM, dhruvbird  wrote:
> 
> >>> > Just saw the blog post introducing 0.8 and it seems that it's a
> 
> >>> > conscious
> 
> >>> > decision to leave sticky sessions out.
> 
> >>>
> 
> >>> That's correct.
> 
> >>
> 
> >> --
> 
> >> 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

--- 
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.

[nodejs] Event bus - hook.io like.

[Tim Dickinson]

I'm looking for a pure node event bus. Something like hook.io but that 
is kept up to date.

I have been thinking of building my own module using 
https://github.com/visionmedia/axon but if something is already out there 
then why not use it.

What I'm doing is have a few processes that are Independence of each other. 
There can be a master process or peer2peer type setup. Each process and 
listen/subscribe to events as other process emit/publish events. I like the 
ruby nats system but I'm looking for something that is written in node. I 
know there is a client for node for nats but i don't want to have to run a 
ruby process if i don't have to.

I really like hook.io but it uses a lot of memory and is kind slow. if I 
have more then a few processes hook.io gets really slow.

-- 
-- 
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.

[nodejs] Re: Event bus - hook.io like.

[Tim Dickinson]

>Why Dont you try redis or zmq?
Like I say I dont really want to have to run another non-node process.

>It's still experimental, but I'm working on this module I named "verbose" 
and has similar goals:
I like it but seems very young. Has it been used in any project yet?


On Wednesday, March 6, 2013 3:35:38 PM UTC-5, Tim Dickinson wrote:
>
> I'm looking for a pure node event bus. Something like hook.io but that 
> is kept up to date.
>
> I have been thinking of building my own module using 
> https://github.com/visionmedia/axon but if something is already out there 
> then why not use it.
>
> What I'm doing is have a few processes that are Independence of each 
> other. There can be a master process or peer2peer type setup. Each process 
> and listen/subscribe to events as other process emit/publish events. I like 
> the ruby nats system but I'm looking for something that is written in node. 
> I know there is a client for node for nats but i don't want to have to run 
> a ruby process if i don't have to.
>
> I really like hook.io but it uses a lot of memory and is kind slow. if I 
> have more then a few processes hook.io gets really slow.
>
>

-- 
-- 
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: Event bus - hook.io like.

[Tim Dickinson]

No it looks very nice. I gave you a pull request for your package.json.

On Thursday, March 7, 2013 7:44:00 AM UTC-5, Pedro Teixeira wrote:
>
> Yes, very young and experimental, just a bit of a mad science project for 
> the time being.
>
> -- 
> Pedro
>
> On Thursday, March 7, 2013 at 12:31 PM, Tim Dickinson wrote:
>
> >Why Dont you try redis or zmq?
> Like I say I dont really want to have to run another non-node process.
>
> >It's still experimental, but I'm working on this module I named 
> "verbose" and has similar goals:
> I like it but seems very young. Has it been used in any project yet?
>
>
> On Wednesday, March 6, 2013 3:35:38 PM UTC-5, Tim Dickinson wrote:
>
> I'm looking for a pure node event bus. Something like hook.io but that 
> is kept up to date.
>
> I have been thinking of building my own module using 
> https://github.com/visionmedia/axon but if something is already out there 
> then why not use it.
>
> What I'm doing is have a few processes that are Independence of each 
> other. There can be a master process or peer2peer type setup. Each process 
> and listen/subscribe to events as other process emit/publish events. I like 
> the ruby nats system but I'm looking for something that is written in node. 
> I know there is a client for node for nats but i don't want to have to run 
> a ruby process if i don't have to.
>
> I really like hook.io but it uses a lot of memory and is kind slow. if I 
> have more then a few processes hook.io gets really slow.
>
>  -- 
> -- 
> 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.

[nodejs] Re: fs.createWritestream change path dynamically

[Tim Dickinson]

I dont really understand what your trying to do. You cant create a write 
stream without a file name. You could create a random file name and then 
rename it once you have the real file name.

On Thursday, March 7, 2013 9:35:00 AM UTC-5, Thorsten Moeller wrote:
>
> Hi,
>
> i am creating a writestream on a server connection event using a path join 
> of a fix path and a variable for the filename. As the filename is not known 
> on server connection event (sent later via connection data event) , it is 
> empty and therefore not working afterwards, producing errors (connot open 
> file).
>
> Is there a way to handle this more dynamically?? Perhaps creating the 
> stream first like an global object and later set the filename and then 
> using the stream via something like a method???
>
>
> Regards
>
> Thorsten
>

-- 
-- 
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: fs.createWritestream change path dynamically

[Tim Dickinson]

This is to say that he is using node 0.9.x
Also as @greelgorke  said, a large file will bring up problem with keeping 
the data in memory.

Streaming the data to a tmp file "/tnp/random-name" is the best bet.
it removes any complexity that might come up then trying to pipe the data 
back into a file.

@Thorsten Moeller You should really think about getting the name of the 
file before you write any data to it. You will have a stronger program if 
you do.

On Thursday, March 7, 2013 10:15:04 AM UTC-5, Luke Arduini wrote:
>
> @tim you're thinking of streams as just file-related things
>
> thorsten - 
>
> Using the new stream class you can do:
>
> var stream = new Stream.Readable()
> stream.push(null)
> stream.push('your data and stuff')
>
> when you're ready for a file
>
> stream.pipe(fs.createWriteStream('outputfile'))
>
> keep in mind data events wont get emitted without a listener in new 
> streams, for better/worse depending on what you're trying to do
>
>
> On Thu, Mar 7, 2013 at 9:43 AM, Tim Dickinson 
> > wrote:
>
>> I dont really understand what your trying to do. You cant create a write 
>> stream without a file name. You could create a random file name and then 
>> rename it once you have the real file name.
>>
>>
>> On Thursday, March 7, 2013 9:35:00 AM UTC-5, Thorsten Moeller wrote:
>>>
>>> Hi,
>>>
>>> i am creating a writestream on a server connection event using a path 
>>> join of a fix path and a variable for the filename. As the filename is not 
>>> known on server connection event (sent later via connection data event) , 
>>> it is empty and therefore not working afterwards, producing errors (connot 
>>> open file).
>>>
>>> Is there a way to handle this more dynamically?? Perhaps creating the 
>>> stream first like an global object and later set the filename and then 
>>> using the stream via something like a method???
>>>
>>>
>>> Regards
>>>
>>> Thorsten
>>>
>>  -- 
>> -- 
>> 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.

[nodejs] Re: process_child.fork() env and arguments

[Tim Dickinson]

So you think that passing in null as your env will give you a null env in 
the new process?

If so that is wrong.

On Monday, March 11, 2013 7:57:21 AM UTC-5, Alan Hoffmeister wrote:
>
> Hello there,
>
> Why {env : myEnvObject} it's being ignored I pass null to the [args] 
> option in process_child.fork()?
>
> Thanks.
> --
> 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

--- 
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] Raft - Open-Source PaaS

[Tim Dickinson]

Hey sorry for the delay.  

I don't think Raft is at the stage when you would want to use it. The post 
I made was really just to see what the community thought about the project. 
There are no stable versions of raft. The most text/docs/info your going to 
find about raft right now is this post. Raft would be a good good dev/build 
environment for NodeJS, but it us just to early use it with confidence. I'm 
very happy you have interest in raft and thank you for it.

As for the continuous integration  Raft does have the ability to do this, 
but it is still a far way off.

On Thursday, March 14, 2013 11:44:32 AM UTC-5, Nick Middleweek wrote:
>
> Anyone?...
>
>
> On 10 March 2013 22:01, Nick Middleweek 
> > wrote:
>
>> Hi,
>>
>> I'm after a cloud provider for hosting NodeJS apps that supports CI, 
>> perhaps in a similar way to CloudBees supports Java/ CI/ Git, etc. I'm not 
>> claiming to  be an expert with CloudBees, in fact I'm far from it but a 
>> recent company I worked at used CloudBees and the CTO had everything 
>> covered, production was deployed to AWS.
>>
>> I'm after a good dev/build environment for NodeJS - is Raft the answer to 
>> this? Does it support Jenkins or something similar?
>>
>>
>> Cheers,
>> Nick
>>
>>
>>
>> On 8 March 2013 14:19, Filirom1 > wrote:
>>
>>> Hi, 
>>>
>>> You may be interested by openruko <https://github.com/openruko>, an 
>>> OpenSource Heroku clone written in nodejs.
>>>
>>> Cheers
>>> Romain
>>>
>>> Le samedi 2 mars 2013 03:49:19 UTC+1, Tim Dickinson a écrit :
>>>
>>>> CloudFoundry is a very nice peace of software and might just be best 
>>>> the open-source paas systems. I have taken a lot of inspirations from 
>>>> how cloudfoundry/appfog is built. The idea of the event system 
>>>> that Raft uses comes from how cloudfoundry's system works. Having a mesh 
>>>> like network or servers that can be used to host node applications. 
>>>>
>>>> Its hard to say that Raft has any advantage over cloudfoundry. The 
>>>> only advantage's that raft has would only effect a node.js program 
>>>> developer. The Raft's stack is written in node and its make to host 
>>>> node applications. Any add-ons for raft would be written in node. So if 
>>>> you 
>>>> where someone who is hosting 10, 20, 100+ node applications then Raft *
>>>> *could be a better fit.
>>>>
>>>> Some other thing that are nice is the one-line install of a PaaS 
>>>> system. From starting the hardware to hosting an application is very easy.
>>>>
>>>> I would say Raft is more of a tool to the developer then a service.
>>>>
>>>> On Friday, March 1, 2013 2:28:28 AM UTC-5, Charlie Edward wrote:
>>>>>
>>>>> Looks awesome.  What is the advantage versus cloudfoundry, and other 
>>>>> open source solutions?
>>>>>
>>>>> On Fri, Mar 1, 2013 at 7:16 AM, Tim Dickinson >>>> > wrote:
>>>>>
>>>>>> Raft - Open-Source PaaS
>>>>>>
>>>>>> The idea behind raft and mangoraft.com is to give the node community 
>>>>>> a fully-featured Platform as a Service (PaaS). Raft gives you a 
>>>>>> provision 
>>>>>> of CPU, memory, disk space and bandwidth. From this the sky's the limit 
>>>>>> in 
>>>>>> what can be build. Sites and services ranging from the weekend projects 
>>>>>> to 
>>>>>> large scale production sites are able to take advantage of raft. Full 
>>>>>> instances of a UNIX system is available from with in the running 
>>>>>> allocation. Each application is run in its own chroot jail. Keeping all 
>>>>>> other applications sharing the system safe.
>>>>>>  <https://github.com/MangoRaft/Raft#convenient>Convenient 
>>>>>>
>>>>>> Deploy your application in under 30 seconds. Fast deploys mean even 
>>>>>> more time to build and debug your applications.
>>>>>>  <https://github.com/MangoRaft/Raft#scalable>Scalable 
>>>>>>
>>>>>> Run more than one instance of your application. A global footprint is 
>>>>>> no problem, run your application independent to any LaaS providers or 
>>>>>> even 
>>>>>> run

[nodejs] Re: [ANN] address-rfc2822

[Tim Dickinson]

link?

On Sunday, March 17, 2013 1:24:00 PM UTC-4, Matt Sergeant wrote:
>
> Not many people using node will need this module, but I figured I'd 
> announce it anyway...
>
> address-rfc2822 parses email addresses as seen in email From/To/CC/Bcc 
> headers. It is *not* meant for parsing or validating email addresses as 
> seen on a web form.
>
> It's useful if you have emails and need to extract out the 
> names/comments/address parts of those headers.
>
> It's a direct port of the Perl Mail::Address module, for those who have 
> experience with that module.
>
> Matt.
>

-- 
-- 
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.

[nodejs] git server built with node

[Tim Dickinson]

Hey all, I'm looking for a git server or a module to build a git server 
with node.js.

I have looked at pushover and from what I can tell I could build a git 
server with it.

Can anyone tell me more?

Thanks

-- 
-- 
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] git server built with node

[Tim Dickinson]

Anything current? I'm not looking for a project on kickstarter. 

On Monday, March 18, 2013 8:16:23 PM UTC-4, Karl Tiedt wrote:
>
> self explanatory... http://www.kickstarter.com/projects/creationix/js-git
>
> -Karl Tiedt
>
>
> On Mon, Mar 18, 2013 at 7:14 PM, Tim Dickinson 
> 
> > wrote:
>
>> Hey all, I'm looking for a git server or a module to build a git server 
>> with node.js.
>>
>> I have looked at pushover and from what I can tell I could build a git 
>> server with it.
>>
>> Can anyone tell me more?
>>
>> Thanks
>>
>> -- 
>> -- 
>> 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.

Re: [nodejs] git server built with node

[Tim Dickinson]

Ah now we are getting someplace. Thanks for the information I will use it 
when I build my server.

On Monday, March 18, 2013 10:18:20 PM UTC-4, mfcollins3 wrote:
>
> I blogged about this a while ago, but ran out of time to do anything with 
> it. This blog post discusses the git HTTP protocol and what you need to do 
> to be able to push to/pull from a remote repository:
>
>
> http://www.michaelfcollins3.me/blog/2012/05/18/implementing-a-git-http-server.html
>
> I hope that it helps.
>
> On Mar 18, 2013, at 5:14 PM, Tim Dickinson > 
> wrote:
>
> Hey all, I'm looking for a git server or a module to build a git server 
> with node.js.
>
> I have looked at pushover and from what I can tell I could build a git 
> server with it.
>
> Can anyone tell me more?
>
> Thanks
>
> -- 
> -- 
> 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.

Re: [nodejs] git server built with node

[Tim Dickinson]

Did you read my post?

On Wednesday, March 20, 2013 4:25:42 AM UTC-4, mrdnk wrote:
>
> Have you seen pushover https://github.com/substack/pushover
>
> On 20 Mar 2013, at 02:55, Tim Dickinson > 
> wrote:
>
> Ah now we are getting someplace. Thanks for the information I will use it 
> when I build my server.
>
> On Monday, March 18, 2013 10:18:20 PM UTC-4, mfcollins3 wrote:
>>
>> I blogged about this a while ago, but ran out of time to do anything with 
>> it. This blog post discusses the git HTTP protocol and what you need to do 
>> to be able to push to/pull from a remote repository:
>>
>>
>> http://www.michaelfcollins3.me/blog/2012/05/18/implementing-a-git-http-server.html
>>
>> I hope that it helps.
>>
>> On Mar 18, 2013, at 5:14 PM, Tim Dickinson  wrote:
>>
>> Hey all, I'm looking for a git server or a module to build a git server 
>> with node.js.
>>
>> I have looked at pushover and from what I can tell I could build a git 
>> server with it.
>>
>> Can anyone tell me more?
>>
>> Thanks
>>
>> -- 
>> -- 
>> 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.

[nodejs] Event loop blocking. How to detect?

[Tim Dickinson]

Hey all

So I'm looking for the best way to detect how blocked the event loop is.

What I'm thinking is to setTimeout say every 1sec and see what kind of 
delay there is. You should get 1000ms but really 1001-1005ms on a clean 
event loop.

Would it be just to say if I'm getting 1050 to even 2000ms+ on the timeout 
that the event loop is getting blocked.

I'm building a basic "load balancing" over different processes running the 
same app. I'm using bounce as the proxy and i want to know which process i 
should route the request, the least congested process.

Thanks

-- 
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] Event loop blocking. How to detect?

[Tim Dickinson]

So you suggest monitoring the process from the out side? I would like to do 
it in the apps state.

On Tuesday, June 5, 2012 5:23:51 PM UTC-4, akzhan wrote:
>
> Answer is don't block event loop, right?
>
> Extract blocking ops out of Node.
>
> Add /status url to the application and track it with monit/bluepill etc. 
> to dump/restart wrong state app.
>
> 2012/6/6 Tim Dickinson 
>
>> Hey all
>>
>> So I'm looking for the best way to detect how blocked the event loop is.
>>
>> What I'm thinking is to setTimeout say every 1sec and see what kind of 
>> delay there is. You should get 1000ms but really 1001-1005ms on a clean 
>> event loop.
>>
>> Would it be just to say if I'm getting 1050 to even 2000ms+ on the 
>> timeout that the event loop is getting blocked.
>>
>> I'm building a basic "load balancing" over different processes running 
>> the same app. I'm using bounce as the proxy and i want to 
>> know which process i should route the request, the least congested process.
>>
>> Thanks
>>
>> -- 
>> 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: Event loop blocking. How to detect?

[Tim Dickinson]

> I didn't write this, but this is how we detect when the event loop is 
getting blocked. 
Thanks for the snippet I was going to do the same thing.

>Well sure, but if it's blocked your timeout will never hit.
Never say never. The codes not blocking in that sense. At some point the 
timer will go off. There are no forever loops.

-- 
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: Event loop blocking. How to detect?

[Tim Dickinson]

>while (1); // timer will never fire 
Thats not what im asking about. There are no while loop, my for loops even 
use the nextTick. I need to know what kind of delay there is, not if the 
code is blocking. The longer the delay the more work has been quoted.

Why would someone write a forever loop in js or any other language.
> The internal setTimeout/Interval solution is completely ridiculous. Why 
is anyone even contemplating it? 
Wring forever loops is "completely ridiculous" your looking at it all wrong.


I'm going with something like Jeff Willden wrote, Thanks.

On Tuesday, June 5, 2012 11:28:07 PM UTC-4, Ben Noordhuis wrote:
>
> On Wed, Jun 6, 2012 at 3:21 AM, Tim Dickinson  
> wrote: 
> >>Well sure, but if it's blocked your timeout will never hit. 
> > 
> > Never say never. The codes not blocking in that sense. At some point the 
> > timer will go off. There are no forever loops. 
>
> Sure there are: 
>
>   setTimeout(process.exit, 1); 
>   while (1); // timer will never fire 
>

-- 
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: Event loop blocking. How to detect?

[Tim Dickinson]

Ok so there is a lot been said here.

Am I wrong to be thinking the way I am about the event loop?

On Tuesday, June 5, 2012 5:05:38 PM UTC-4, Tim Dickinson wrote:
>
> Hey all
>
> So I'm looking for the best way to detect how blocked the event loop is.
>
> What I'm thinking is to setTimeout say every 1sec and see what kind of 
> delay there is. You should get 1000ms but really 1001-1005ms on a clean 
> event loop.
>
> Would it be just to say if I'm getting 1050 to even 2000ms+ on the timeout 
> that the event loop is getting blocked.
>
> I'm building a basic "load balancing" over different processes running the 
> same app. I'm using bounce as the proxy and i want to know which process i 
> should route the request, the least congested process.
>
> Thanks
>

-- 
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: Version 0.7.10 (unstable, but please read anyway)

[Tim Dickinson]

How much is this going to break npm modules? Should i wait or should i 
upgrade? I want to upgrade but don't want to spend a week fixing broken 
packages.

On Monday, June 11, 2012 11:59:52 AM UTC-4, Isaac Schlueter wrote:
>
> 2012.06.11, Version 0.7.10 (unstable) 
>
> This is the second-to-last release on the 0.7 branch.  Version 0.8.0 
> will be released some time next week.  As other even-numbered Node 
> releases before it, the v0.8.x releases will maintain API and binary 
> compatibility. 
>
> The major changes are detailed in 
> https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8 
>
> Please try out this release.  There will be very few changes between 
> this and the v0.8.x release family.  This is the last chance to comment 
> on the API before it is locked down for stability. 
>
>
> * Roll V8 back to 3.9.24.31 
>
> * build: x64 target should always pass -m64 (Robert Mustacchi) 
>
> * add NODE_EXTERN to node::Start (Joel Brandt) 
>
> * repl: Warn about running npm commands (isaacs) 
>
> * slab_allocator: fix crash in dtor if V8 is dead (Ben Noordhuis) 
>
> * slab_allocator: fix leak of Persistent handles (Shigeki Ohtsu) 
>
> * windows/msi: add node.js prompt to startmenu (Jeroen Janssen) 
>
> * windows/msi: fix adding node to PATH (Jeroen Janssen) 
>
> * windows/msi: add start menu links when installing (Jeroen Janssen) 
>
> * windows: don't install x64 version into the 'program files (x86)' 
> folder (Matt Gollob) 
>
> * domain: Fix #3379 domain.intercept no longer passes error arg to cb 
> (Marc Harter) 
>
> * fs: make callbacks run in global context (Ben Noordhuis) 
>
> * fs: enable fs.realpath on windows (isaacs) 
>
> * child_process: expose UV_PROCESS_DETACHED as options.detached 
> (Charlie McConnell) 
>
> * child_process: new stdio API for .spawn() method (Fedor Indutny) 
>
> * child_process: spawn().ref() and spawn().unref() (Fedor Indutny) 
>
> * Upgrade npm to 1.1.25 
> - Enable npm link on windows 
> - Properly remove sh-shim on Windows 
> - Abstract out registry client and logger 
>
>
> Source Code: http://nodejs.org/dist/v0.7.10/node-v0.7.10.tar.gz 
>
> Windows Installer: http://nodejs.org/dist/v0.7.10/node-v0.7.10.msi 
>
> Windows x64 Files: http://nodejs.org/dist/v0.7.10/x64/ 
>
> Macintosh Installer (Universal): 
> http://nodejs.org/dist/v0.7.10/node-v0.7.10.pkg 
>
> Other release files: http://nodejs.org/dist/v0.7.10/ 
>
> Website: http://nodejs.org/docs/v0.7.10/ 
>
> Documentation: http://nodejs.org/docs/v0.7.10/api/ 
>

-- 
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] - Github Followers Thread

[Tim Dickinson]

Please and thanks
>
>
https://github.com/FLYBYME

-- 
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] res.setHeader is so slow

[Tim Dickinson]

Take a look at the source code and it will give you an idea.
https://github.com/joyent/node/blob/master/lib/http.js#L949

On Friday, June 15, 2012 3:14:35 AM UTC-4, Jason.桂林(Gui Lin) wrote:
>
> I found 
> writeHead
>  is 
> much faster if there is no 
> setHeader
>  before.
>
>
> -- 
> Best regards,
>
> 桂林 (Gui Lin)
>
> guileen@twitter 
> 桂糊涂@weibo 
> guileen@github 
>
> 

-- 
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: crazy ideas in proxing.

[Tim Dickinson]

I think callback style is better then just returning values for the host 
and port. If hostname is stored in a database then you might run into 
problems.

On Friday, June 15, 2012 9:45:29 AM UTC-4, Dominic wrote:
>
> so, 
>
> For a while I've been wondering, could I make a *really* simple proxy? 
>
> Although in http 1.1 multiple requests may be made in the same tcp 
> connection, a well behaved client is not allowed 
> to make requests to different hosts in the same connection, so this 
> begs the question: is it necessary to properly parse http? 
> as long as you can parse the first header, and then connect the tcp 
> stream to the right place... then every thing should just work, 
> including WebSockets. 
>
> It was marak who originally suggested this idea to me. 
>
> so, today I actually tried it... and it looks like: IT WORKED!!! 
>
> https://github.com/dominictarr/badass 
>
> npm install badass 
>
> I've implemented just enough to make a load-balancer with sticky 
> sessions. basically it just matches the text before the first empty 
> line. pulls out the headers with a few regexps, and then just sends 
> the rest through as buffers. it also extracts the first header on the 
> response, so you can force a cookie to get sticky sessions. 
>
> it's only about 100 lines, and it does next to nothing to the tcp 
> stream, so it should be really fast. 
>
> but I havn't benchmarked it yet. 
>
> also, I havn't written a detailed test suite that cover all the error 
> paths. 
> (connections unexpectedly closing etc) 
>
> There are some things that will never do, like, deliver it's own error 
> messages. 
> But thats okay. I'm trying to be ruthlessly simple. 
> If you want a fully featured proxy, use something else. 
>
> cheers, Dominic 
>

-- 
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: Version 0.7.11 (unstable)

[Tim Dickinson]

Just installed it going to see how well the code ports.

On Friday, June 15, 2012 3:48:36 PM UTC-4, Isaac Schlueter wrote:
>
> This is the most stable 0.7 release yet.  Please try it out. 
>
> Version 0.8 will be out very soon.  You can see the remaining issues 
> on the github issue tracker. 
>
>  
>
> 2012.06.15, Version 0.7.11 (unstable) 
>
> * V8: Upgrade to v3.11.10 
>
> * npm: Upgrade to 1.1.26 
>
> * doc: Improve cross-linking in API docs markdown (Ben Kelly) 
>
> * Fix #3425: removeAllListeners should delete array (Reid Burke) 
>
> * cluster: don't silently drop messages when the write queue gets big 
> (Bert Belder) 
>
> * Add Buffer.concat method (isaacs) 
>
> * windows: make symlinks tolerant to forward slashes (Bert Belder) 
>
> * build: Add node.d and node.1 to installer (isaacs) 
>
> * cluster: rename worker.unqiueID to worker.id (Andreas Madsen) 
>
> * Windows: Enable ETW events on Windows for existing DTrace probes. 
> (Igor Zinkovsky) 
>
> * test: bundle node-weak in test/gc so that it doesn't need to be 
> downloaded (Nathan Rajlich) 
>
> * Make many tests pass on Windows (Bert Belder) 
>
> * Fix #3388 Support listening on file descriptors (isaacs) 
>
> * Fix #3407 Add os.tmpDir() (isaacs) 
>
> * Unbreak the snapshotted build on Windows (Bert Belder) 
>
> * Clean up child_process.kill throws (Bert Belder) 
>
> * crypto: make cipher/decipher accept buffer args (Ben Noordhuis) 
>
>
> Source Code: http://nodejs.org/dist/v0.7.11/node-v0.7.11.tar.gz 
>
> Macintosh Installer (Universal): 
> http://nodejs.org/dist/v0.7.11/node-v0.7.11.pkg 
>
> Windows Installer: http://nodejs.org/dist/v0.7.11/node-v0.7.11-x86.msi 
>
> Windows x64 Installer: http://nodejs.org/dist/v0.7.11/node-v0.7.11-x64.msi 
>
> Windows x64 Files: http://nodejs.org/dist/v0.7.11/x64/ 
>
> Other release files: http://nodejs.org/dist/v0.7.11/ 
>
> Website: http://nodejs.org/docs/v0.7.11/ 
>
> Documentation: http://nodejs.org/docs/v0.7.11/api/ 
>

-- 
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] cp.fork with stdout

[Tim Dickinson]

How do i get the stdout from a child process fork?

Im running node 0.7.11 can i use the new stdio pipe options to get to the 
stream of stdout?

Thanks

-- 
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] cp.fork with stdout

[Tim Dickinson]

Ok so with using node 0.7.11 can i setup an ipc channel using "{ stdio: [
'ipc', 'pipe', 'pipe'] }". I've played around with it but can't seem to get 
it to work.Am I don't this I'm going about it right, Even something like "{
 stdio: 'ipc' }" shold throw an error but does not so i must be going about 
it wrong.

On Sunday, June 17, 2012 8:44:32 PM UTC-4, Ben Noordhuis wrote:
>
> On Sat, Jun 16, 2012 at 10:44 PM, Tim Dickinson  
> wrote: 
> > How do i get the stdout from a child process fork? 
> > 
> > Im running node 0.7.11 can i use the new stdio pipe options to get to 
> the 
> > stream of stdout? 
>
> Not quite. A child process spawned with .fork() inherits stdout and 
> stderr from its parent unless you pass `{silent:true}`. The silent 
> option is supposed to set up pipes but it seems to be broken right 
> now[1]. 
>
> [1] https://github.com/joyent/node/issues/3472 
>

-- 
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] cp.fork with stdout

[Tim Dickinson]

Oh i meant through cp.spawn. I've upgraded to 0.7.16-pre and it seems to 
work now.

On Tuesday, June 19, 2012 7:58:17 AM UTC-4, Ben Noordhuis wrote:
>
> On Tue, Jun 19, 2012 at 6:16 AM, Tim Dickinson  
> wrote: 
> > Ok so with using node 0.7.11 can i setup an ipc channel using "{ stdio: 
> > ['ipc', 'pipe', 'pipe'] }". I've played around with it but can't seem to 
> get 
> > it to work.Am I don't this I'm going about it right, Even something like 
> > "{ stdio: 'ipc' }" shold throw an error but does not so i must be going 
> > about it wrong. 
>
> options.stdio doesn't work with fork(). 
>
> fork() makes certain assumptions about how stdio is set up and simply 
> ignores options.stdio. Use spawn() instead. 
>

-- 
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 0.1.1 to 0.8.0

[Tim Dickinson]

So i was just looking at the source of node 
https://github.com/joyent/node/tree/v0.1.1 and I'm just amazed at how far 
it has come in the past few years. The days of res.sendBody and res.finish 
are far memory to some and unknown to others.

I don't know where i would be with out node. I love it and its amazing! 
Thanks very must to ry!

Just my 2cents.
Thanks

-- 
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: Node and developing on multiple machines

[Tim Dickinson]

Look at cloud9, its all web based.

On Friday, June 22, 2012 5:52:25 PM UTC-4, Ralphtheninja (Magnus Skog) 
wrote:
>
> Hi,
>
> It's very common that I use several machines while developing and those 
> machines might also be in different locations. I have two machines at home 
> and two machines at my moms etc. There might be more machines in the 
> future. My problem is this. No matter where I am, I just want to sit down 
> and code and not care about what modules I have installed and where. If I'm 
> visiting my mom some day I might find this uber cool module and install it 
> globally with npm on that machine. When I get back home I'd like to sync my 
> global modules on my other machines, instead of having to remember that I 
> installed module X on machine Y. Do you have any recommendations?
>
> Thanks
> /Magnus
>

-- 
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: Node 0.1.1 to 0.8.0

[Tim Dickinson]

>  Thanks very must to ry! 
should be >  Thanks very much to ry! 

I would very much like to see Ryan come back.

I would like to know why he left, there was not much said on why.


On Friday, June 22, 2012 9:14:44 PM UTC-4, Tim Dickinson wrote:
>
> So i was just looking at the source of node 
> https://github.com/joyent/node/tree/v0.1.1 and I'm just amazed at how far 
> it has come in the past few years. The days of res.sendBody and res.finish 
> are far memory to some and unknown to others.
>
> I don't know where i would be with out node. I love it and its amazing! 
> Thanks very must to ry!
>
> Just my 2cents.
> Thanks
>

-- 
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: API changes from 0.6 to 0.8

[Tim Dickinson]

>
> > The goal is to have a module compatible with both 0.6 and 0.8, not one 
> for each version.
>

At some point you will have to. No one writes code for version 0.4, the 
same should now be true for version 0.6. You should encourage the uses of 
new build's of node. The cluster module was brand new in 0.6 and from what 
I understand the api is frozen for 0.8 to account for stability.

Just pulling this from a gist.
>The v0.6 release family will continue to see releases for critical 
bugfixes and security issues through the end of 2012. However, it will not 
be the main focus of the core team's attention.

-- 
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: Determining if a cluster worker is idle

[Tim Dickinson]

When using the detached option to start a long-running process, the process 
will not stay running in the background unless it is provided with a stdio 
configuration 
that is not connected to the parent. If the parent's stdio is inherited, 
the child will remain attached to the controlling terminal.

The process will exit if no other callbacks are due. This is one way to do 
it.

On Wednesday, June 20, 2012 3:56:57 PM UTC-4, Philip Thrasher wrote:
>
> Is there a way to check if there are any registered callbacks still 
> waiting from within a worker process? For instance, I have an application 
> that spawns a number of workers, each of which can make async calls, and 
> even generate more work (handing work requests back to master) for the 
> other workers. How can I determine when my cluster is completely finished? 
> Is there a way to check and see if there are any http requests 
> yet-unfulfilled, or any setTimeouts not yet fulfilled?

-- 
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: Node and developing on multiple machines

[Tim Dickinson]

Hello github!!

Or get yourself a laptop. Your trying to have the cake and eat it too.

-- 
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 0.1.1 to 0.8.0

[Tim Dickinson]

Do you know if he would come back as a dev for node?

On Saturday, June 23, 2012 4:32:49 PM UTC-4, Ben Noordhuis wrote:
>
> On Sat, Jun 23, 2012 at 9:53 PM, Tim Dickinson  
> wrote: 
> >>  Thanks very must to ry! 
> > should be >  Thanks very much to ry! 
> > 
> > I would very much like to see Ryan come back. 
> > 
> > I would like to know why he left, there was not much said on why. 
>
> He got a job building Rails websites. 
>

-- 
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] Module requirement

[Tim Dickinson]

Hey all

So I'm writing a PaaS on top on node. What I'm doing is running each 
file/module in a custom context so that i can place my own globals inside 
of that file/module.


this is my "require"  code https://gist.github.com/3189241 it is very basic 
just so i can get the idea of how to run the code.

Can someone look at it and tell me if im doing something wrong or should be 
doing it different.

You can see the raft object that im trying to inject into the module.

Thanks

-- 
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] Raft - PaaS - Advice from nodester / nodejitsu / haibu

[Tim Dickinson]

Hey all.

So this is not a ANN but more of an request for advice from nodester / 
nodejitsu / haibu and the community in general. What i have been working on 
for the past few months is of sort a PaaS. The basic idea behind it is to 
create a server to can spawn node apps that are pushed out to it with a cli.

I'm calling it Raft as in a boat to float apps on. It has gone through a 
few iterations since it creation. It started out as a MVC style app 
container. The basic app structure was you would have your model's, view's 
and controller's, and raft would load all these into the app, kinda so 
you didn't have to code and express server or is server or what have you. 
As i worked on raft and played around with it more i found that 
the MVC style was much less dynamic then i would have liked. So from that 
the current version has evolved.

The current version... OK the current version is now very low leave, in 
fact it does not do much other then load the app and its module in a 
context with its own process. the only different between the raft context 
and plain nodejs context is that you get a global called raft. what the 
raft object does is gives you http, tcp, express server and so on. these 
servers are just like the native server but for one difference and that 
been httpserver.listen, the native httpserver.listen take a port and host, 
but what the raft httpserver.listen take is a string that is a domain that 
gets routed to the port of that app. 

OK so like i say this is not an announcement but more a request for advice.

Some of the questions:

I know that nodester is hosted on AWS's and with that how many apps are 
hosted per server? Are the server like a 8GB/RAM 4/core pc running maybe 20 
apps per server, or is is a micro server running just one app?

Nodejitsu are the developer of  haibu, but i dont think that is what they 
are using for the PaaS. Now on that is their backend a custom build 
of haibu or is it a whole new module in its own?

To nodester. why did you chose git for the pushing of apps to the backend? 

To nodester / nodejitsu. Have you guys thought of a kind of dynos (heroku 
style)? if so how would you guys go about doing that? like you spawn 2 
processes of the same app and just route request to each app like node does 
with the cluster module?

To nodester. On average what are your costs running 3000+ app on AWS's? 

OK so this is what im going to ask for now. I do have more question but i 
would like to see if i get any answers for these ones.

Gota love node!

The code for now. Please note that this is not a release but a Q&A
https://npmjs.org/package/raft
https://github.com/FLYBYME/Raft


Thanks all
Tim

-- 
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: Raft - PaaS - Advice from nodester / nodejitsu / haibu

[Tim Dickinson]

>Actually, haibu is what runs everyone's apps on nodejitsu! We have a few 
closed source extensions for haibu, but aside from that it's all the same. 
In fact, I encourage you to use haibu as a starting point for something 
like raft. 
Well haibu was the first project that i found to be like mine is.  haibu 
has heavily influenced raft, so has heroku and nodester.


>We have a similar concept, called a drone (
https://github.com/nodejitsu/haibu-carapace). Each haibu server (
https://github.com/nodejitsu/haibu) can spawn n drones running whatever 
(multiple apps, or multiple copies of the same app). Our balancers can then 
proxy to these drones however we please. 

The drones concept is very slimier to what raft has. I just thought there 
might have been more to it.

>I can tell you right now that it's non-trivial. I doubt a single person 
could realistically afford to run 3000+ apps out-of-pocket, at least 
without seriously gimping each app's resources. 
I dont see myself running 3000+ app out of pocket. You make a good point 
about how much load each app would have. Looking at nodester they seem to 
limit each app to 25mb of ram and if it goes over then it kills the app and 
re-spawns it. I dont really want to go that route, how do you guys monitor 
each app? Do you do it inside the app or from out-side the app? do you ever 
kill apps or been resouce hogs?

>From the second post
>They need 3000+ IP addresses which are a limited resource and you have to 
explain your demand to RIPE.
The way raft is setup you only need a few external ip's. These ip's would 
be pointing at the load-balancer. So 3000+ apps would not be a problem as 
they would be local ip's

>Nodejitsu uses jitsu+http because it allows us to use npm for app 
bundling. 
I have followed a very slimier approach to you guys. Do you guys feel that 
it makes user less likely to use the platform because git is not used?

>but imo you should always be able to start a single instance of an app 
without clustering by running, say, `node app.js`.
I agree with you here. I have given it some thought and was thinking of 
doing something like "raft-cli run" and this would allow the user to run 
the app locally. The whole node app.js this is far fetched for raft as it 
runs each file.js in its own context. I need to do a lot 
more thinking about this problem.


On Saturday, August 11, 2012 5:33:21 PM UTC-4, Tim Dickinson wrote:
>
> Hey all.
>
> So this is not a ANN but more of an request for advice from nodester / 
> nodejitsu / haibu and the community in general. What i have been working on 
> for the past few months is of sort a PaaS. The basic idea behind it is to 
> create a server to can spawn node apps that are pushed out to it with a cli.
>
> I'm calling it Raft as in a boat to float apps on. It has gone through a 
> few iterations since it creation. It started out as a MVC style app 
> container. The basic app structure was you would have your model's, view's 
> and controller's, and raft would load all these into the app, kinda so 
> you didn't have to code and express server or is server or what have you. 
> As i worked on raft and played around with it more i found that 
> the MVC style was much less dynamic then i would have liked. So from that 
> the current version has evolved.
>
> The current version... OK the current version is now very low leave, in 
> fact it does not do much other then load the app and its module in a 
> context with its own process. the only different between the raft context 
> and plain nodejs context is that you get a global called raft. what the 
> raft object does is gives you http, tcp, express server and so on. these 
> servers are just like the native server but for one difference and that 
> been httpserver.listen, the native httpserver.listen take a port and host, 
> but what the raft httpserver.listen take is a string that is a domain that 
> gets routed to the port of that app. 
>
> OK so like i say this is not an announcement but more a request for advice.
>
> Some of the questions:
>
> I know that nodester is hosted on AWS's and with that how many apps are 
> hosted per server? Are the server like a 8GB/RAM 4/core pc running maybe 20 
> apps per server, or is is a micro server running just one app?
>
> Nodejitsu are the developer of  haibu, but i dont think that is what they 
> are using for the PaaS. Now on that is their backend a custom build 
> of haibu or is it a whole new module in its own?
>
> To nodester. why did you chose git for the pushing of apps to the backend? 
>
> To nodester / nodejitsu. Have you guys thought of a kind of dynos (heroku 
> style)? if so how would you guys go about doing that? like you spawn 2 
> processes of the same app and just route request to each

Re: [nodejs] Re: Raft - PaaS - Advice from nodester / nodejitsu / haibu

[Tim Dickinson]

>I would rather say it would be more likely that people use the platform. 
Not everybody uses git, subversion and mercurial are still really big 
version
control systems. And by starting out with HTTP support you could actually 
support all these different kind of version control system if you a simple
hook script that deploys the code on push. While this is not the same as 
having "git" on the server, it comes really close to the functionality and 
is
much more flexible in my opinion.

I do feel the same way about your opinion, i could always just pull a git 
repo  like haibu does

>

-- 
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: Raft - PaaS - Advice from nodester / nodejitsu / haibu

[Tim Dickinson]

How do you guys Load-balance over 2 apps? are you monitoring the apps load? 
or is it like the cluster module does it with round ribbon or what ever its 
called?

On Wednesday, August 15, 2012 5:40:52 PM UTC-4, jesusabdullah wrote:
>
> > Do you have more than one Haibu server running? 
>
> Yes. Dedicated apps each get their own haibu server. Meaning we're 
> running thousands of 'em. 
>
> > how would you go about doing ReverseProxy/LoadBalancing? 
>
> We use https://github.com/nodejitsu/node-http-proxy in our balancers. 
>
> --Josh 
>
> On Wed, Aug 15, 2012 at 2:30 PM, Gustavo Machado 
> > 
> wrote: 
> > Nodejitsu/Haibu guys, 
> > 
> > Do you have more than one Haibu server running? And if so, how would 
> > you go about doing ReverseProxy/LoadBalancing? 
> > 
> > Thanks, 
> > Gustavo Machado 
> > 
> > On Mon, Aug 13, 2012 at 2:03 PM, chrismatthieu 
> > > wrote: 
> >> Hi Tim, 
> >> 
> >> I'm the founder of Nodester, the open source Node.JS PaaS.  Your 
> project 
> >> sounds really cool!  Answers to your questions are provided below: 
> >> 
> >> - I know that nodester is hosted on AWS's and with that how many apps 
> are 
> >> hosted per server? Are the server like a 8GB/RAM 4/core pc running 
> maybe 20 
> >> apps per server, or is is a micro server running just one app? 
> >> 
> >> Nodester is currently hosting over 6,000 Node.JS apps on a single Extra 
> >> Large AWS instance without a reverse proxy!  We have a team currently 
> >> working on horizontal scaling and monitoring and the ability to spin up 
> >> additional resources like Heroku's dynos.  We are calling them "Jets" 
> to go 
> >> along with our rocket theme ;) 
> >> 
> >> - To nodester. why did you chose git for the pushing of apps to the 
> backend? 
> >> 
> >> We love Git!  It's the modern way for updating code and pushing updates 
> on 
> >> many services.  Now that Windows users are becoming more familiar with 
> git, 
> >> our support efforts have decreased with trying to teach people how to 
> use 
> >> it.  Setting up an RSA key the first time for git has always been our 
> most 
> >> FAQ.  Over time, this has proven to be the right decision! 
> >> 
> >> - To nodester / nodejitsu. Have you guys thought of a kind of dynos 
> (heroku 
> >> style)? if so how would you guys go about doing that? like you spawn 2 
> >> processes of the same app and just route request to each app like node 
> does 
> >> with the cluster module? 
> >> 
> >> Jets are coming... 
> >> 
> >> - To nodester. On average what are your costs running 3000+ app on 
> AWS's? 
> >> 
> >> $500 per month (which is sponsored by @Tropo) :) 
> >> 
> >> Gotta love the Node.JS community and Tropo - http://tropo.com! 
> >> 
> >> Hack the Planet! 
> >> @ChrisMatthieu 
> >> 
> >> 
> >> 
> >> On Saturday, August 11, 2012 2:33:21 PM UTC-7, Tim Dickinson wrote: 
> >>> 
> >>> Hey all. 
> >>> 
> >>> So this is not a ANN but more of an request for advice from nodester / 
> >>> nodejitsu / haibu and the community in general. What i have been 
> working on 
> >>> for the past few months is of sort a PaaS. The basic idea behind it is 
> to 
> >>> create a server to can spawn node apps that are pushed out to it with 
> a cli. 
> >>> 
> >>> I'm calling it Raft as in a boat to float apps on. It has gone through 
> a 
> >>> few iterations since it creation. It started out as a MVC style app 
> >>> container. The basic app structure was you would have your model's, 
> view's 
> >>> and controller's, and raft would load all these into the app, kinda so 
> you 
> >>> didn't have to code and express server or is server or what have you. 
> As i 
> >>> worked on raft and played around with it more i found that the MVC 
> style was 
> >>> much less dynamic then i would have liked. So from that the current 
> version 
> >>> has evolved. 
> >>> 
> >>> The current version... OK the current version is now very low leave, 
> in 
> >>> fact it does not do much other then load the app and its module in a 
> context 
> >>> with its own process. the only different between the raft context and 
> plain 
> >>> nodejs context is tha

Re: [nodejs] Re: Raft - PaaS - Advice from nodester / nodejitsu / haibu

[Tim Dickinson]

That is a good example but what if you have a cluster of http-proxy, you 
may end up sending 10 request to on app then 10 to the other.

What are peoples take on loadbalanceing over two or more app?

On Wednesday, August 15, 2012 5:49:41 PM UTC-4, José F. Romaniello wrote:
>
> is called round-robin, I dont know if they do that  but i know in the 
> node-http-proxy there is a very nice example:
>
>
> https://github.com/nodejitsu/node-http-proxy/blob/master/examples/balancer/simple-balancer.js
>  
>
> btw, I love the level of openess of both companies :)
>
> 2012/8/15 Tim Dickinson >
>
>> round ribbon
>
>
>

-- 
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: Raft - PaaS - Advice from nodester / nodejitsu / haibu

[Tim Dickinson]

>6. Save your routing tables in memory, don't go fetch from DB on every 
request.
For now I'm query the db every time a request comes in. I tried keeping it 
in memory but i need to find a better way to push to all nodes in the 
cluster.

>7. Cluster + in memory state for apps, support nightmare
To scale out this is needed. In memory state for apps is something the 
developer would have to consider.

>8. Multi-port apps, don't do it unless you are letting people drop their 
own load balancers.
Drop their own load balancers is far fetch as the load balancing is a core 
part of raft.

Raft is very slimier to how heroku works in fact heroku has been 
a meager influence to raft. I need to do more reading about how heroku does 
scaling with their dynos.

I was thinking about multi request from the same user to different app. 
Maybe something like a session or by ip to route the same user to the same 
app every time. This would stop one request to one app and another request 
to the second app from the same user. This would help the developer to keep 
an in app state.

On Thursday, August 16, 2012 12:04:36 AM UTC-4, Bradley Meck wrote:
>
> When using multiple load balancers for multiple domains:
>
> 1. SNICallback in https is your friend for figuring out domains.
> 2. You will want to be grabbing data from a shared storage facility like a 
> Database where you can replicate down to your balancers. This information 
> will hold info on where to route requests, when to remove drones from the 
> tables, and even info such as load averages ideally.
> 3. RoundRobin works better than you might think #2 is overkill usually.
> 4. Use IP hashes to determine consistently where your connection/session 
> should go to, sending reconnect and session logic to 2 different drones can 
> lead to bad behavior.
> 5. Terminate SSL for the love of all that is holy if you have already 
> locked down your workers.
> 6. Save your routing tables in memory, don't go fetch from DB on every 
> request.
> 7. Cluster + in memory state for apps, support nightmare
> 8. Multi-port apps, don't do it unless you are letting people drop their 
> own load balancers.
>

-- 
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] Raft 0.0.1 PaaS

[Tim Dickinson]

I would like to say hello to the node community!

I have been working on the Raft module for a few weeks now. It 
is functional but it is still in the early stages.
The concept is very slimier to nodester or haibu. It allows you to host 
many apps on a single server or even multiple servers. There is a cli to 
deploy your app, check logs, start, stop, restart and get the status of the 
app.

 At this point there is still lots to do and many bugs to fix. I am more 
then happy to get any contribution to the code!

Links
https://github.com/FLYBYME/Raft
https://github.com/FLYBYME/Raft-worker
https://github.com/FLYBYME/Raft-node
https://github.com/FLYBYME/Raft-cli
https://github.com/FLYBYME/Raft-proxy

Things I have imperilment

   - Node
  - App API start, stop, deploy, create and logs
  - User API register and login
   - Worker
  - App API start, stop, restart, deploy, create and logs 
  - NPM dependence management
  - App build fail notice
   - Cli
  - Start, stop, restart, deploy, create and logs  
  - User register, login
   - Proxy
  - The old code works but the new code still needs to be written
   

Things I want to imperilment

   - Windows support
   - Worker status
   - Node status
   - Chroot jail for each app
   - Worker choke status
   - Better authorization for users
   - Coupon request for new users
   - Password reset
   - Heroku dyno style multi apps
   - Admin panel
   - Main site
   - And many more!


Let me know know people think. If you think its crap or is its really cool, 
let me know! I'm looking for advice on the best way to approach the idea.

Thanks again
Tim

-- 
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: [ANN] Raft 0.0.1 PaaS

[Tim Dickinson]

> Awesome! Building these tools is a lot of fun.  
Yeah I had great fun building this framework. I learnt a lot about node 
building it.

> One small piece of advice...a lot of your packages are using * for the 
npm dependency version. 
Well right now I'm still building it. At some point I will add version 
numbers to the package.json

>It's really cool, Thanks!
Thanks dude!


On Monday, August 27, 2012 6:46:33 PM UTC-7, Tim Dickinson wrote:
>
> I would like to say hello to the node community!
>
> I have been working on the Raft module for a few weeks now. It 
> is functional but it is still in the early stages.
> The concept is very slimier to nodester or haibu. It allows you to host 
> many apps on a single server or even multiple servers. There is a cli to 
> deploy your app, check logs, start, stop, restart and get the status of the 
> app.
>
>  At this point there is still lots to do and many bugs to fix. I am more 
> then happy to get any contribution to the code!
>
> Links
> https://github.com/FLYBYME/Raft
> https://github.com/FLYBYME/Raft-worker
> https://github.com/FLYBYME/Raft-node
> https://github.com/FLYBYME/Raft-cli
> https://github.com/FLYBYME/Raft-proxy
>
> Things I have imperilment
>
>- Node
>   - App API start, stop, deploy, create and logs
>   - User API register and login
>- Worker
>   - App API start, stop, restart, deploy, create and logs 
>   - NPM dependence management
>   - App build fail notice
>- Cli
>   - Start, stop, restart, deploy, create and logs  
>   - User register, login
>- Proxy
>   - The old code works but the new code still needs to be written
>
>
> Things I want to imperilment
>
>- Windows support
>- Worker status
>- Node status
>- Chroot jail for each app
>- Worker choke status
>- Better authorization for users
>- Coupon request for new users
>- Password reset
>- Heroku dyno style multi apps
>- Admin panel
>- Main site
>- And many more!
>
>
> Let me know know people think. If you think its crap or is its really 
> cool, let me know! I'm looking for advice on the best way to approach the 
> idea.
>
> Thanks again
> Tim
>

-- 
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: Giving up on node.js / Flatiron / hook.io

[Tim Dickinson]

Ah dude you must be supper pissed. 

My point of view is there's no reason to go public with this. I don't care 
what happens as you would be replaced with the next open-source project. I 
look at your git page and you have nearly 1000+ follower.. Man I only have 
9! You need to get off your high horse.  if everyone felt the way you do 
there would be nothing. Step into my shoes.. no one uses my code.. hell no 
one has even read my code. Does that matter? NO! Its not about the fame or 
glory, its about the love for coding and that's all that matters!

On Tuesday, September 11, 2012 11:56:45 AM UTC-4, Marak Squires wrote:
>
> Internet Friends -
>
> I'm sure it will come as a pleasant surprise for most of you to hear I'm 
> leaving node.js for good. I'll also be stepping down from any involvement 
> with Flatiron and completely shutting down hook.io
>
> In all honesty, I don't think there is much of a loss here for anyone.
>
> The Flatiron framework is pretty much pointless and I'd advise against 
> using it. I started to add some really good reflection features, but since 
> my access has now been removed from Flatiron, I'll no longer be able to 
> advance or maintain any of these features. 
>
> The same advice goes for hook.io. hook.io was a great idea, but it's been 
> systematically made obsolete by Nodejitsu in favor of a closed 
> source priority solution. I'd love to be able to share this with you, but 
> it's closed source, so thats that. I was rebuilding hook.io to use 
> Flatiron, but without the ability to work on Flatiron anymore, it's all 
> moot.
>
> It's really sad to wind all this down, but I don't have a choice in the 
> matter. I've been fired from Nodejitsu and no longer have the resources or 
> git commit access to move any of this stuff forward.
>
> Anyway, thanks for all the good and bad times and goodbye.
>
>

-- 
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: Giving up on node.js / Flatiron / hook.io

[Tim Dickinson]

Get a job!

On Wednesday, September 12, 2012 6:17:48 AM UTC-4, Filipe wrote:
>
> Tim, when you already have food on the table, right?

-- 
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] Stream to multi-stream

[Tim Dickinson]

Hey all.

I'm looking for a module that would allow me to have one net socket 
or other stream and layer other streams on top of it.

I was thinking of writing my own module for this but if anyone knows of 
something like this then i would look at it first before i write my own.

-- 
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: Stream to multi-stream

[Tim Dickinson]

>Do you mean pipe on stream to several streams?

No what I mean is to have one stream and and then have other stream pipe to 
it. So mulit point to mulit point on one stream.

-- 
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: Stream to multi-stream

[Tim Dickinson]

Oh yes its called "multiplex-demultiplex"
Thanks!
On Thursday, September 13, 2012 5:24:44 PM UTC-7, Raynos wrote:
>
> https://github.com/dominictarr/mux-demux
>
> On Thu, Sep 13, 2012 at 1:14 PM, Tim Dickinson 
> 
> > wrote:
>
>> >Do you mean pipe on stream to several streams?
>>
>> No what I mean is to have one stream and and then have other stream pipe 
>> to it. So mulit point to mulit point on one stream.
>>  
>> -- 
>> 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

[nodejs] Re: Crockford : Ynode : "I would fork node.js"

[Tim Dickinson]

I would like to see a fork of node.

On Saturday, September 15, 2012 10:45:30 AM UTC-4, Jorge wrote:
>
> http://www.youtube.com/watch?v=8HzclYKz4yQ#t=22m30s 
>
> "I would fork nodejs. Nodejs is a great thing and I would bet the company 
> on it, but I would not bet the company on Joyent. I see Joyent doing some 
> stuff which is amateurish, maybe a little chidish, so I would fork it, and, 
> I would then give that back to the community, and it would be industrial 
> strength and secure and designed to operate a Yahoo scale and would make it 
> available for everybody for free" 
>
> -- 
> Jorge.

-- 
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: How to aggregate streams? (multiplexer/demultiplexer)

[Tim Dickinson]

LOL I should have searched the group. I asked this question like two days 
latter.

On Monday, September 3, 2012 5:44:24 AM UTC-4, lbdremy wrote:
>
> Hello,
>
> I'm wondering, does someone know a module that is able to aggregate 
> multiple streams into 1. 
> For example you give it 3 readable streams and you get 1 stream emitting 
> all `data ` events from these 3 streams and emitting the `end` event when 
> the 3 streams are ended.
> Same thing for writable streams, where when you write, you actually write 
> to 3 streams.
> And a combinaison of both for writable/readable streams.
>
> Thanks,
>
>

-- 
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: Update Amazon Server to 0.8.x

[Tim Dickinson]

You will have to compile from the git repo or from a tar file.

On Thursday, October 11, 2012 8:44:27 AM UTC-4, Tim Stewart wrote:
>
> I have NodeJS running on an Amazon EC2 server with Amazon Linux AMI. But 
> how do I update from 0.6.18 to 0.8.x? I have tried
>
> sudo yum update nodejs
>
> sudo yum erase nodejs
> followed by
> sudo yum install nodejs
>
> ... and the instructions at:
> https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager
>
> But the node version sticks at 0.6.18.
>
> Any ideas?
>
> Thanks
> Tim
>

-- 
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] git server built with node

[Tim Dickinson]

This might just be what im looking for. Im going to play around with the 
code to see if I can use it.

Ill let you know.

On Sunday, April 21, 2013 12:49:55 AM UTC-4, Quinton Pike wrote:
>
> Here is the link for those that are interested: 
> https://github.com/qrpike/NodeJS-Git-Server
>
> Trying to keep it as lightweight and minimal as possible to not get in the 
> way too much. But I should be adding onPush and onFetch triggers per repo 
> very soon.
>
> Thanks,
>
> On Saturday, April 20, 2013 10:05:23 AM UTC-4, Jose wrote:
>>
>> Hi Quinton,
>> Took a look at gitserver. Interesting. I'd love to see some comparisons 
>> to gitolite, especially how flexible it is to manage permissions and add 
>> hooks.
>> good job anyway
>> On Apr 18, 2013, at 10:51 PM, Quinton Pike  wrote:
>>
>> I am building a NodeJS multi-tenant git server based on pushover. 
>>
>> If you would like, I can put it on github and we can work on it together.
>>
>> Let me know - Thanks.
>>
>> On Monday, March 18, 2013 8:14:58 PM UTC-4, Tim Dickinson wrote:
>>>
>>> Hey all, I'm looking for a git server or a module to build a git server 
>>> with node.js.
>>>
>>> I have looked at pushover and from what I can tell I could build a git 
>>> server with it.
>>>
>>> Can anyone tell me more?
>>>
>>> Thanks
>>>
>>
>> -- 
>> -- 
>> 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.

Re: [nodejs] Better async loop

[Tim Dickinson]

Thanks for the snippet. I have taken your var result = new Array(length); 
to optimize the array.

Why I use a function for the call back with the result is to play on the 
make call now get result latter. Really I'm using this function to update 
data in my database.


Array.prototype.forLoop = function(worker, callBack) {
var items = this;
var length = items.length;
var results = new Array(length);
var errors = new Array(length);

var index = 0;

function doNext() {
worker.call(items, items[index], function(err, result) {
results[index] = result;
errors[index] = err;
index++;
if(index === length)
callback(errors, results);
else
process.nextTick(doNext);
});
}

process.nextTick(doNext);

};

On Wednesday, April 11, 2012 5:13:52 PM UTC-4, Tim Caswell wrote:
>
> Ok, so you have a large array and want to do some work on it but break up 
> the work across several ticks?  That's fine.  I still don't understand why 
> your workers have a callback if they are sync.  So assuming sync workers 
> you could do something like:
>
> var queue = [1,2,3,4,5];
>
> function processSlowly(items, work, callback) {
>   var length = items.length;
>   var results = new Array(length);
>   var index = 0;
>   function doNext() {
> results[index] = work(items[index]);
> index++;
> if (index === length) return callback(results);
> process.nextTick(doNext);
>   }
>   process.nextTick(doNext);
> }
>
>
> If your workers are async, you don't need nectTick because the callback is 
> already called on a new tick.
>
> function processSerialy(items, work, callback) {
>   var length = items.length;
>   var results = new Array(length);
>   var index = 0;
>   function doNext() {
> work(items[index], function (result) {
>   results[index] = result;
>   index++;
>   if (index === length) return callback(results);
>   doNext();
> });
>   }
>   process.nextTick(doNext);
> }
>
> Also note that I don't have any error checking or handling here.  I don't 
> know if the function should bail out on first error, if it should log the 
> error and continue or some other behavior.
>
> On Wed, Apr 11, 2012 at 3:33 PM, Tim Price  wrote:
>
>> OK good point.
>>
>> The stack would be the wrong word. What im trying to do is push eash loop 
>> around the array to be in a new cycle around node loop.
>>
>> I'm trying to keep node event loop running fast. The "asyncForEach" can 
>> take as long as it need, it would be bulk work. I dont want to through 
>> 1000+ function into one cycle around nodes event loop. Now 1000+ is 
>> an example as 100+ might be a better real work example.
>>
>> With your asyncForEach would be the same as the forEach that is already 
>> part of the language.
>>
>> Maybe you can see why i used the nextTick.
>>
>>
>> On Wednesday, April 11, 2012 4:08:10 PM UTC-4, Tim Caswell wrote:
>>>
>>> My point being that you're showing your worker has a callback.  If there 
>>> is a callback then I assume it's an async function. The callback will 
>>> already be called in a new stack.  There is no need to use nextTick to 
>>> break the stack.  If the worker is a sync function then it should return 
>>> it's value instead of passing it via callback.  Then you can use 
>>> Array.prototype.map as-is to get the resultant array.
>>>
>>> Assuming the worker is async, my parallel example was async and 
>>> parallel. If you want async and serial that can be done too similair to 
>>> your original example.
>>>
>>> Since you said "Your asyncForEach is at the end of the day synchronous 
>>> loop just like any other forloop" I'm confused and somewhere one of your 
>>> assumptions is wrong.
>>>
>>> On Wed, Apr 11, 2012 at 3:02 PM, Tim Caswell  wrote:
>>>
 If you just want to keep the stack from growing a simple while or for 
 loop is much easier.

 var items = [1,2,3,4];

 function forEach(items, worker) {
   for (var i = 0, l = items.length; i < l; i++) {
 worker(items[i], i, items);
   }
 }

 forEach(items, function (value, index, array) {
 });

 or just use the built-in Array.prototype.forEach

 items.forEach(function (value, index, array) {
 });

 I don't understand the goal.  My example was assuming that worker was 
 non-blocking and called the callback in a new tick.  It was parallel and 
 async.


 On Wed, Apr 11, 2012 at 2:49 PM, Tim Price wrote:

> I Wanted to keep the items in serially, as im trying to break the 
> stack. Your asyncForEach is at the end of the day synchronous loop just 
> like any other forloop. 
>
> On Wednesday, April 11, 2012 3:33:18 PM UTC-4, Tim Caswell wrote:
>>
>> That depends on what you want it to do.  This seems to execute each 
>> item serially.  You can do them all parallel and abort on the first 
>> error 
>> like this:
>>
>> function asyncForEach(array, worker, callback) {
>>   var len = array.length;
>>   var results = new Arra

[nodejs] Keeping the websocket connection streaming data even with the iPhone locked

[Tim Dickinson]

Thank god it does not keep running. I would hate some web page to keep running 
after I close the phone. What you need is some kind of native app or webkit 
view app. Look at something like phonegap. 

-- 
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] Stream to JSON

[Tim Dickinson]

Hey all.

How can i better write this snippet of code?

var bufferJson = function(key, requestEvent) {
var buffer = []
var cryptoFn = function(message) {
var decipher = crypto.createDecipher('aes-256-cbc', key)
return decipher.update(message, 'hex', 'utf8') + decipher['final']('utf8')
}
function onData(data) {
if(data.indexOf('\n') > -1) {

var message = buffer.join('');
data = data.split('\n');
message += data.shift();
buffer = [];

try {
console.log(cryptoFn(message))
var json = JSON.parse(cryptoFn(message));
} catch(e) {
return util.error('Could not parse message: ' + e.message);
}

requestEvent(json)
data = data.join('\n');

if(data.length) {
onData(data);
}

} else {
buffer.push(data);
}
}

return onData
}

-- 
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: Stream to JSON

[Tim Dickinson]

Oh sorry and you would use it like so


socket.on('data', bufferJson(key, function(data) {
//do something with json object
}))

On Monday, April 30, 2012 6:23:11 PM UTC-4, Tim Dickinson wrote:
>
> Hey all.
>
> How can i better write this snippet of code?
>
> var bufferJson = function(key, requestEvent) {
> var buffer = []
> var cryptoFn = function(message) {
> var decipher = crypto.createDecipher('aes-256-cbc', key)
> return decipher.update(message, 'hex', 'utf8') + decipher['final']('utf8')
> }
> function onData(data) {
> if(data.indexOf('\n') > -1) {
>
> var message = buffer.join('');
> data = data.split('\n');
> message += data.shift();
> buffer = [];
>
> try {
> console.log(cryptoFn(message))
> var json = JSON.parse(cryptoFn(message));
> } catch(e) {
> return util.error('Could not parse message: ' + e.message);
> }
>
> requestEvent(json)
> data = data.join('\n');
>
> if(data.length) {
> onData(data);
> }
>
> } else {
> buffer.push(data);
> }
> }
>
> return onData
> }
>

-- 
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: Stream to JSON

[Tim Dickinson]

Oh i like that idea. If i did it like you had said then i would maybe pipe 
to a xml praser or pipe even to a logger.

On Monday, April 30, 2012 6:36:22 PM UTC-4, Marco Rogers wrote:
>
> There are several potential issues I'm seeing here. But it looks like you 
> have an incoming stream of json messages that are encrypted and separated 
> by newlines. You want parse the stream, decrypt each message and then pass 
> the message to a data handler that expect to each message one by one. Is 
> that accurate?
>
> This is a great use case for node streams. Read up on them and create a 
> stream (or multiple streams) that encapsulates this behavior. You might end 
> up with a an elegant solution that looks like multiple streams piped 
> together.
>
> decryptedStream.on('data', function(data) {
>   // do something with json object
> });
> socket.pipe(messageSplitter).pipe(decrytptedStream)
>
> Here are some good resources to check out.
>
> http://nodejs.org/api/stream.html
> http://maxogden.com/node-streams
> https://github.com/dominictarr/event-stream
>
> In short, try to separate concerns, splitting the message stream, 
> decrypting, json parsing, etc.
>
> :Marco
>
>
> On Monday, April 30, 2012 3:24:37 PM UTC-7, Tim Dickinson wrote:
>>
>> Oh sorry and you would use it like so
>>
>>
>> socket.on('data', bufferJson(key, function(data) {
>> //do something with json object
>> }))
>>
>> On Monday, April 30, 2012 6:23:11 PM UTC-4, Tim Dickinson wrote:
>>>
>>> Hey all.
>>>
>>> How can i better write this snippet of code?
>>>
>>> var bufferJson = function(key, requestEvent) {
>>> var buffer = []
>>> var cryptoFn = function(message) {
>>> var decipher = crypto.createDecipher('aes-256-cbc', key)
>>> return decipher.update(message, 'hex', 'utf8') + 
>>> decipher['final']('utf8')
>>> }
>>> function onData(data) {
>>> if(data.indexOf('\n') > -1) {
>>>
>>> var message = buffer.join('');
>>> data = data.split('\n');
>>> message += data.shift();
>>> buffer = [];
>>>
>>> try {
>>> console.log(cryptoFn(message))
>>> var json = JSON.parse(cryptoFn(message));
>>> } catch(e) {
>>> return util.error('Could not parse message: ' + e.message);
>>> }
>>>
>>> requestEvent(json)
>>> data = data.join('\n');
>>>
>>> if(data.length) {
>>> onData(data);
>>> }
>>>
>>> } else {
>>> buffer.push(data);
>>> }
>>> }
>>>
>>> return onData
>>> }
>>>
>>

-- 
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: Stream to JSON

[Tim Dickinson]

So I thought about what you had said and I came up with this  
https://gist.github.com/2816361. What tips can you give me if any on making 
the "Stream"'s?

On Monday, April 30, 2012 6:36:22 PM UTC-4, Marco Rogers wrote:
>
> There are several potential issues I'm seeing here. But it looks like you 
> have an incoming stream of json messages that are encrypted and separated 
> by newlines. You want parse the stream, decrypt each message and then pass 
> the message to a data handler that expect to each message one by one. Is 
> that accurate?
>
> This is a great use case for node streams. Read up on them and create a 
> stream (or multiple streams) that encapsulates this behavior. You might end 
> up with a an elegant solution that looks like multiple streams piped 
> together.
>
> decryptedStream.on('data', function(data) {
>   // do something with json object
> });
> socket.pipe(messageSplitter).pipe(decrytptedStream)
>
> Here are some good resources to check out.
>
> http://nodejs.org/api/stream.html
> http://maxogden.com/node-streams
> https://github.com/dominictarr/event-stream
>
> In short, try to separate concerns, splitting the message stream, 
> decrypting, json parsing, etc.
>
> :Marco
>
>
> On Monday, April 30, 2012 3:24:37 PM UTC-7, Tim Dickinson wrote:
>>
>> Oh sorry and you would use it like so
>>
>>
>> socket.on('data', bufferJson(key, function(data) {
>> //do something with json object
>> }))
>>
>> On Monday, April 30, 2012 6:23:11 PM UTC-4, Tim Dickinson wrote:
>>>
>>> Hey all.
>>>
>>> How can i better write this snippet of code?
>>>
>>> var bufferJson = function(key, requestEvent) {
>>> var buffer = []
>>> var cryptoFn = function(message) {
>>> var decipher = crypto.createDecipher('aes-256-cbc', key)
>>> return decipher.update(message, 'hex', 'utf8') + 
>>> decipher['final']('utf8')
>>> }
>>> function onData(data) {
>>> if(data.indexOf('\n') > -1) {
>>>
>>> var message = buffer.join('');
>>> data = data.split('\n');
>>> message += data.shift();
>>> buffer = [];
>>>
>>> try {
>>> console.log(cryptoFn(message))
>>> var json = JSON.parse(cryptoFn(message));
>>> } catch(e) {
>>> return util.error('Could not parse message: ' + e.message);
>>> }
>>>
>>> requestEvent(json)
>>> data = data.join('\n');
>>>
>>> if(data.length) {
>>> onData(data);
>>> }
>>>
>>> } else {
>>> buffer.push(data);
>>> }
>>> }
>>>
>>> return onData
>>> }
>>>
>>

-- 
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: Stream to JSON

[Tim Dickinson]

Anything else you can think of? I don't really understand now the streams 
should end.

On Sunday, May 27, 2012 7:23:10 PM UTC-4, Mikeal Rogers wrote:
>
> these are both read/write streams but you don't appear to be emitting 
> "end" after end() is called. that's an issue.
>
> On May 27, 2012, at May 27, 20124:19 PM, Tim Dickinson wrote:
>
> So I thought about what you had said and I came up with this  
> https://gist.github.com/2816361. What tips can you give me if any on 
> making the "Stream"'s?
>
> On Monday, April 30, 2012 6:36:22 PM UTC-4, Marco Rogers wrote:
>>
>> There are several potential issues I'm seeing here. But it looks like you 
>> have an incoming stream of json messages that are encrypted and separated 
>> by newlines. You want parse the stream, decrypt each message and then pass 
>> the message to a data handler that expect to each message one by one. Is 
>> that accurate?
>>
>> This is a great use case for node streams. Read up on them and create a 
>> stream (or multiple streams) that encapsulates this behavior. You might end 
>> up with a an elegant solution that looks like multiple streams piped 
>> together.
>>
>> decryptedStream.on('data', function(data) {
>>   // do something with json object
>> });
>> socket.pipe(messageSplitter).pipe(decrytptedStream)
>>
>> Here are some good resources to check out.
>>
>> http://nodejs.org/api/stream.html
>> http://maxogden.com/node-streams
>> https://github.com/dominictarr/event-stream
>>
>> In short, try to separate concerns, splitting the message stream, 
>> decrypting, json parsing, etc.
>>
>> :Marco
>>
>>
>> On Monday, April 30, 2012 3:24:37 PM UTC-7, Tim Dickinson wrote:
>>>
>>> Oh sorry and you would use it like so
>>>
>>>
>>> socket.on('data', bufferJson(key, function(data) {
>>> //do something with json object
>>> }))
>>>
>>> On Monday, April 30, 2012 6:23:11 PM UTC-4, Tim Dickinson wrote:
>>>>
>>>> Hey all.
>>>>
>>>> How can i better write this snippet of code?
>>>>
>>>> var bufferJson = function(key, requestEvent) {
>>>> var buffer = []
>>>> var cryptoFn = function(message) {
>>>> var decipher = crypto.createDecipher('aes-256-cbc', key)
>>>> return decipher.update(message, 'hex', 'utf8') + 
>>>> decipher['final']('utf8')
>>>> }
>>>> function onData(data) {
>>>> if(data.indexOf('\n') > -1) {
>>>>
>>>> var message = buffer.join('');
>>>> data = data.split('\n');
>>>> message += data.shift();
>>>> buffer = [];
>>>>
>>>> try {
>>>> console.log(cryptoFn(message))
>>>> var json = JSON.parse(cryptoFn(message));
>>>> } catch(e) {
>>>> return util.error('Could not parse message: ' + e.message);
>>>> }
>>>>
>>>> requestEvent(json)
>>>> data = data.join('\n');
>>>>
>>>> if(data.length) {
>>>> onData(data);
>>>> }
>>>>
>>>> } else {
>>>> buffer.push(data);
>>>> }
>>>> }
>>>>
>>>> return onData
>>>> }
>>>>
>>>
> -- 
> 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] [ANN] Route-Machine - HTTP proxy built to run in a cluster environmen

[Tim Dickinson]

Hey all!

Route Machine is a HTTP router built to run in a cluster environment. Using 
the NATS network to update routes in real-time.

Route Machine has been built for the uses with the Raft framework. The 
events Route Machine emits are watched by the Dea.


https://github.com/MangoRaft/route-machine

-- 
-- 
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.

[nodejs] Re: How to measure proxy-request-time of node-http-proxy?

[Tim Dickinson]

This about your cope.

var proxyServer = http.createServer(function (req, res) {

var start_time = new Date().getTime();

proxy.web(req, res);

res.on('finish', function() {
console.log("The request was proxied in " + (new Date().getTime() - 
start_time) + "ms");
});
});

On Saturday, January 25, 2014 5:40:09 AM UTC-8, Christoph wrote:
>
> Hi,
>
> i want to measure the amount of time, each proxy-request needs, so i tried 
> it this way:
>
>
> 
> var httpProxy = require('http-proxy');
> var http = require('http');
>
> var proxy = new httpProxy.createProxyServer({
> target: {
> host: 'localhost',
> port: 80
> }
> });
>
> var start_time = 0;
> var proxyServer = http.createServer(function (req, res) {
>
> start_time = new Date().getTime();
>
> proxy.web(req, res);
>
> res.on('finish', function() {
> console.log("The request was proxied in " + (new Date().getTime() 
> - start_time) + "ms");
> });
> });
> proxyServer.listen(3000);
>
> 
>
> but this does not work correctly, if there are parallel connections to 
> handle. start_time is over-written on each client-request and not handled 
> per request.
>
> thanks for any advice! :)
>

-- 
-- 
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.

[nodejs] [ANN] metrics-server

[Tim Dickinson]

Would like to introduce metric-server

metrics-server is a basic metrics server and client. The client uses UDP to 
send metric to the server. The server stores all metric into a mongodb 
database.

https://github.com/MangoRaft/metrics-server

-- 
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/0af10e5a-d0c0-4736-ba76-99a95eee0cad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[nodejs] Re: node.js cluster multiprocess logging solution

[Tim Dickinson]

Take a look at https://github.com/MangoRaft/Logger

Its not ready for use yet but could be something you would use.

In the next few days I'll be pushing a new version that is independent to 
raft and could be used by any program.

On Monday, April 28, 2014 5:45:50 AM UTC-5, gen chen wrote:
>
> I am now working on a node.js project based on cluster.  I got stuck on 
> the logging.  After doing some research, I worked out a solution. here is 
> it. i don't know if it is a good idea.  The idea is like this.  only master 
> process can wirte to the log file, if the current process is a worker, then 
> it send a log message to the master and then write to the log file while 
> the master can directly write to the log file. this can avoid multiple 
> process open and write to a same file. 
>
> var util = require('util');
> var fs = require('fs');
> var cluster = require('cluster');
>
> var logger = module.exports;
>
> var levels  = ['debug', 'info', 'warn', 'error', 'fatal'];
> var logLevel = 'debug';
>
> var logfile = null;
> var errorLogfile  = null;
>
>
> if(cluster.isMaster){
>
> logfile = fs.createWriteStream('debug.log', {flags:'a'});
> errorLogfile = fs.createWriteStream('error.log', {flags:'a'});
>
> cluster.on('online', function(worker){
> //collect log message from child and write to logfile.
> worker.on('message', function(msg){
> if(msg.type == 'logging') {
> var level = msg.data.level;
> var logStr = msg.data.msg;
> if(levels.indexOf(level) >= levels.indexOf('error')){
> errorLogfile.write(logStr + '\n');
> }else{
> logfile.write(logStr + '\n');
> }
> }
> });
> });
> }
>
>
> function log(level, args){
>
> if(levels.indexOf(level) < levels.indexOf(logLevel)) return;
>
> var args = Array.prototype.slice.call(args);
>
> args = args.map(function(a){
> if(typeof a !== 'string') 
> return JSON.stringify(a);
> else return a;
> });
> var msg = util.format.apply(null, args);
>
> var out = [];
> out.push(new Date());
> out.push('[' + level.toUpperCase() + ']');
> out.push(msg);
>
> 
> if(cluster.isMaster){
>
> //write directly to the log file
> if(levels.indexOf(level) >= levels.indexOf('error')){
> errorLogfile.write(out.join(' ') + '\n');
> }else{
> logfile.write(out.join(' ') + '\n');
> }
>
> }else{
>
> //send to master
> cluster.worker.process.send({
> type : 'logging', 
> data : {
> level : level,
> msg : out.join(' ')
> }
> });
> }
>
> }
>
>
> logger.debug = function(){log('debug', arguments);}
> logger.info = function(){log('info', arguments);}
> logger.warn = function(){log('warn', arguments);}
> logger.error = function(){log('error', arguments);}
> logger.fatal = function(){log('fatal', arguments);}
>
>
>
>

-- 
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/3bfba8cf-1961-4ed2-9daa-096bd4ee59d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[nodejs] Efficient node.js IPC

[Tim Dickinson]

Hey all.

I would like to know from peeps what could be the best IPC.

I have written this code to test what I might use.
https://github.com/FLYBYME/node_ipc_benchmarks

Background.

I have a UDP server receiving messages at a high rate of speed. The server 
stores the last 1500x1000 messages in memory.
I have a web server that reads the messages and streams them out to clients.

UDP -> Memory -> WebServer -> HTTP

At the moment my server is only one process. I have bottlenecks. Im looking 
to setup a multi-process server.

What I'm thinking is something like:

UDP1,UDP2,UDP3 -> IPC 
-> WebServer1-memory/WebServer2-memory/WebServer3-memory -> HTTP

The UDP server/s receives messages. The UDP send the messages over TCP to 
the web server. The web server sends the messages to multiple clients over 
HTTP.

Im looking to scale this up over many cores.

>From my test I have found that RAW TCP connection seems to be the best 
performer.


Any advice on this would be very cool.


SIDE NOTE:
I have thought about saving messages into a database like redis but I have 
found that redis is really slow compared to TCP/Memory.


Thanks

-- 
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/1459ec6e-89c7-4554-8d8d-4c9c2125da83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[nodejs] [ANN] Logger - distributed logging system

[Tim Dickinson]

Logster is a distributed logging system. have you ever wanted to collect 
logs from multiple sources and view them in one place? Well Logster is the 
answer.

https://github.com/MangoRaft/Logger

-- 
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/67255189-951b-4c27-854e-b27aaa891470%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Tim Dickinson]

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.

On Tuesday, March 10, 2015 at 12:34:22 PM UTC-4, Aria Stewart wrote:
>
>
> On Mar 10, 2015, at 11:17 AM, Tim Dickinson  > wrote:
>
> Logster is a distributed logging system. have you ever wanted to collect 
> logs from multiple sources and view them in one place? Well Logster is the 
> answer.
>
>
>
> Neat!
>
> How do you handle dropped log packets?
>
>

-- 
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/a3520a0e-ef77-4364-ad29-d85a212a2f9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Tim Dickinson]

If anyone knows of a TCP reconnect module please let me know.

On Tuesday, March 10, 2015 at 11:40:27 AM UTC-4, Tim Dickinson wrote:
>
> Logster is a distributed logging system. have you ever wanted to collect 
> logs from multiple sources and view them in one place? Well Logster is the 
> answer.
>
> https://github.com/MangoRaft/Logger
>

-- 
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/b33af61c-2d27-472f-9b42-8e52b0c41e3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Tim Dickinson]

It would be really easy to implement the TCP protocol with logster. If its 
something people would like to see I would be more than happy to implement 
it.

On Tuesday, March 10, 2015 at 10:52:05 PM UTC-4, 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/3fc287ec-9f02-4185-9d0b-a9a6c1bb9228%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Tim Dickinson]

>  Perhaps Tim you allow the log information to be buffered at the source 
to minimisee loss?
There is a buffer that clears on a timer or the buffer length. So it will 
send a batch of logs in one message.

>clearly these logs will never be important.
Never is a strong word. Like I said a TCP or even a HTTP server would not 
be hard to implement. As people seem to be interested in it I will be 
implementing it as an option.

>If it's UDP only today, is there a plan to support "other ways"? 
Yes coming soon. :)


-- 
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/c7e0e20a-f3b6-4445-a274-4034d1221aae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.