[nodejs] Re: i heared a lot about nodejs but i am afraid

[Wil Moore]

> ...but its not for traditional php my sql websites like a ecommerce 
> website.


I wouldn't go that far. It (NodeJS) will be fine for such a site...possibly 
more ideal than the "traditional" tools.

i have to develop a product reviewing website i have option to choose 
> between php/mysql or nodejs mysql .due to new uprising technology i am more 
> inclined towards nodejs 


Given a choice, I wouldn't recommend that you go with PHP. This advice 
isn't based off of the countless "PHP Hate" articles (BTW, most of those 
articles are at least 90% accurate), but rather years of hands-on 
experience with the language/platform.

develop  such site in nodejs without facing any critical errors


JavaScript has a few well-known issues; but they are mostly minor. Many of 
the issues people run into with JavaScript are in the category of "It 
doesn't behave like C++/Java/PHP so it's wrong". When you have one of those 
moments, just remember: 
https://twitter.com/wilmoore/status/254686641795518465

as i dont know  inner details of nodejs does nodejs supports  all features 
> like php/mysql like for example


Your major issues with NodeJS won't be NodeJS itself, but JavaScript. 
You'll want to put in the time to learn it well before doing anything too 
serious otherwise you'll end up with extremely messy code.

If you are well versed in automated testing, this is the platform for you. 
The NodeJS community tends to value automated testing at a much higher 
level than the larger in-general JavaScript community.

You will want to check out Mocha (Test Framework) and Chai (Assertion 
Library)
 

> does it supports image thumbnail generation ? 
> does it support pdf,excel ,csv file handlings
> does it supports encryption /decryption algos lie AES,Rjinidial or RSA.
>

All of the above. When you are curious. visit npmjs.org and perform a 
package search. 
 

> so main concern is does it have all the recipes required to develop a 
> traditional or complex apps as i don't want to stuck at any point.
>

You will find an npm package for just about anything you need.
 

> i have a  vps server with 256Ram is that enough for a site like ecommerce 
> site developed with nodejs.
>

That won't get you too far with MySQL (or any relational database for that 
matter), but it should be fine for development purposes.



-- 
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: Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Mike Pilsbury]

a)

(My only use of crypto is to createCredentials for tls.)

-- 
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 JS hosting service in Europe

[Shripad K]

I'll be hosting one pretty soon (by end of this week). It will be hosted in
Cloudsigma (Zurich). Will ping you when I push the app into production.

On Tue, Oct 9, 2012 at 10:56 AM, Karl  wrote:

> Don't know what Pubnub does but low cost hosters in Europe are OVH
> (France,"kimserve" range) and 1and1 (also "1und1", Germany, wait for
> special offers), I had/have smallish dedicated root servers from them and
> they seem ok for bandwidth and performance.
>
> El lunes, 8 de octubre de 2012 19:39:59 UTC+2, remi_grumeau escribió:
>
>> Hi!
>>
>> I'm new to Node, yet doing a lot of JS client-side (no JQuery, real
>> JS) and i'm looking to develop an app using Node. Main idea is to get
>> interactions from a mobile phone to control something on a distant
>> screen.
>> To do so, i've done a few tests using PubNub service & it's actually
>> pretty easy to use, prices are low so i'm pretty fine with it. The
>> thing is PubNub is in California & my app will be used mostly by
>> western european people.
>> So i'm looking for the same kind of ready-to-use service like PubNub
>> is, but hosted in Europe so it may be even quicker (i assume).
>>
>> Any idea?
>>
>> Thx a lot!
>> Remi
>>
>  --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Re: i heared a lot about nodejs but i am afraid

[Aldis Andrejevs]

> does it supports image thumbnail generation ?
YES
NodejsGD - https://github.com/taggon/node-gd
and you can use ImageMagick as well - I prefer this, GD I use for
image creation like captcha

> does it support pdf,excel ,csv file handlings
YES
on fast search about PDF - http://pdfkit.org/
EXCEL - its easy no matter of platform, i create EXCEL XML file and
its good to go
CSV - on fast search - https://github.com/koles/ya-csv - so it is supported

> does it supports encryption /decryption algos lie AES,Rjinidial or RSA.
YES
check out - http://nodejs.org/api/crypto.html - module

> etc.
it depends but probably YES :)

> i have a  vps server with 256Ram is that enough for a site like ecommerce
it depends







On Mon, Oct 8, 2012 at 6:54 PM, waqasde  wrote:
> @ Wil Moore i am well versed with traditional MVC apps in php .but from new
> skill set point of view which has demand i was interested to do a
> professional app in nodejs but the point is would i able to develop  such
> site in nodejs without facing any critical errors  as i dont know  inner
> details of nodejs does nodejs supports  all features like php/mysql like for
> example
>
> does it supports image thumbnail generation ?
> does it support pdf,excel ,csv file handlings
> does it supports encryption /decryption algos lie AES,Rjinidial or RSA.
> etc.
> so main concern is does it have all the recipes required to develop a
> traditional or complex apps as i don't want to stuck at any point.
>
> i have a  vps server with 256Ram is that enough for a site like ecommerce
> site developed with nodejs.
>
>
>
> On Monday, October 8, 2012 12:09:03 PM UTC+5, Wil Moore wrote:
>>>
>>> please guys advise should i invest in nodejs for such website ?
>>
>>
>> A few questions you might start out asking yourself:
>>
>> How well do you know PHP/MySQL?
>> Have you built non-trivial apps with PHP, Ruby, etc. in the past?
>> Are you familiar with any PHP frameworks?
>> How comfortable are you with JavaScript?
>> Have you written any non-trivial apps with JavaScript? (i.e. client-side,
>> MVC, etc.)
>>
>>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Eric S]

a), though in interest of full disclosure, the impact on my current code 
will be minimal, and for future stuff, I'd rather get the change over with 
rather than have even more things to change at a later date.

On Monday, October 8, 2012 5:08:54 PM UTC-7, Joshua Gross wrote:
>
> I like B) in theory, as a way to manage APIs. Anyone not reading this 
> newsgroup will at least have *some* advanced warning. 
>

Understandable, but with Node not at 1.0 yet, I'd hope that anyone using 
node in a production environment has at least one team member keeping up 
with this list.  Then again, we're talking reality, not some place that 
makes sense.

-- 
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 JS hosting service in Europe

[Karl]

Don't know what Pubnub does but low cost hosters in Europe are OVH 
(France,"kimserve" range) and 1and1 (also "1und1", Germany, wait for 
special offers), I had/have smallish dedicated root servers from them and 
they seem ok for bandwidth and performance.  

El lunes, 8 de octubre de 2012 19:39:59 UTC+2, remi_grumeau escribió:
>
> Hi! 
>
> I'm new to Node, yet doing a lot of JS client-side (no JQuery, real 
> JS) and i'm looking to develop an app using Node. Main idea is to get 
> interactions from a mobile phone to control something on a distant 
> screen. 
> To do so, i've done a few tests using PubNub service & it's actually 
> pretty easy to use, prices are low so i'm pretty fine with it. The 
> thing is PubNub is in California & my app will be used mostly by 
> western european people. 
> So i'm looking for the same kind of ready-to-use service like PubNub 
> is, but hosted in Europe so it may be even quicker (i assume). 
>
> Any idea? 
>
> Thx a lot! 
> Remi 
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Node.jar - Java port by Oracle

[cole gillespie]

Isnt the goal of node to eventually be done with "new features" / "bugs" ?
=)

On Tue, Oct 9, 2012 at 7:15 AM, Rick Waldron  wrote:

>  This strikes me as the sort of shitty compatibility fragmentation that
> browsers suffer from. What happens when "node.jar" falls behind in
> supporting new features? Bug fixes?
>
> -Rick
>
> On Monday, October 8, 2012 at 9:03 PM, Ben Noordhuis wrote:
>
> On Tue, Oct 9, 2012 at 2:21 AM, Stewart Mckinney 
> wrote:
>
> I'm just curious as to why having Node run on top of the Java run time is
> better than say, vanilla C++ compiled Node running naively. Doesn't it run
> on pretty much every popular platform now, anyway?
>
>
> The major ones, yes. But there are some high margin, low volume
> architectures like POWER and S/390 that V8 doesn't support (and hence
> node.js) but the JVM does. Think AIX, mainframes, etc.
>
> There has been some corporate interest in running node on such
> architectures but the time and money to get (and keep) it ported isn't
> worth it. node.jar could be a viable alternative.
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
>
>  --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Node.jar - Java port by Oracle

[Rick Waldron]

This strikes me as the sort of shitty compatibility fragmentation that browsers 
suffer from. What happens when "node.jar" falls behind in supporting new 
features? Bug fixes?

-Rick


On Monday, October 8, 2012 at 9:03 PM, Ben Noordhuis wrote:

> On Tue, Oct 9, 2012 at 2:21 AM, Stewart Mckinney  wrote:
> > I'm just curious as to why having Node run on top of the Java run time is
> > better than say, vanilla C++ compiled Node running naively. Doesn't it run
> > on pretty much every popular platform now, anyway?
> > 
> 
> 
> The major ones, yes. But there are some high margin, low volume
> architectures like POWER and S/390 that V8 doesn't support (and hence
> node.js) but the JVM does. Think AIX, mainframes, etc.
> 
> There has been some corporate interest in running node on such
> architectures but the time and money to get (and keep) it ported isn't
> worth it. node.jar could be a viable alternative.
> 
> -- 
> Job Board: http://jobs.nodejs.org/
> Posting guidelines: 
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
> 
> 


-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] i heared a lot about nodejs but i am afraid

[Ryan Schmidt]

On Oct 8, 2012, at 10:54, waqasde  wrote:

> does it supports image thumbnail generation ? 
> does it support pdf,excel ,csv file handlings
> does it supports encryption /decryption algos lie AES,Rjinidial or RSA.
> etc. 
> so main concern is does it have all the recipes required to develop a 
> traditional or complex apps as i don't want to stuck at any point.

nodejs is a JavaScript runtime. Yes, you can do all those things in JavaScript. 
Whether there are existing modules that do those specific tasks I don't know. 
You can search on npm and find out:

https://npmjs.org

If no modules exist for specific tasks you need, you'll have to write the code 
yourself.


> i have a  vps server with 256Ram is that enough for a site like ecommerce 
> site developed with nodejs.   

I suppose that depends on how popular the site will be, how many concurrent 
requests it will need to process.

-- 
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: "Evil OS X"... the perfect client to a node server!

[Rick Waldron]

Funny thing, I said much the same as you have here and got a gnarly chastising. 
  

-Rick


On Monday, October 8, 2012 at 11:37 PM, Joshua Gross wrote:

> Dennis, this is a developer forum. If you want to peddle your software and 
> aren't willing to show something besides videos, you're in the wrong place.  
>  
> Also I'm not going to watch a 15 minute video. You're not selling yourself 
> very well, I kindly advise you to move on so this stops clogging my inbox :)
>  
> -- Joshua Gross
> Christian / SpanDeX / BA Candidate of Computer Science, UW-Madison 2013
> 414-377-1041 / http://www.joshisgross.com
>  
>  
> On Oct 8, 2012, at 7:12 PM, Dennis Kane  (mailto:dkan...@gmail.com)> wrote:
>  
> > Why do you want the code so bad?  It's not like there's any kind of fancy 
> > algorithms at work.  There are many many open source windowing packages out 
> > there.  It's not exactly rocket science, this.  It's all been done many 
> > times before.  The only difference is that this one is *my* baby!  Besides, 
> > you are welcome to all the code of my desktop prototype on my site at 
> > luvluvluv.info... it's just sitting there on the server for the taking.
> >  
> > I am mainly using this thing as blackmail to get people to be interested in 
> > being my friend.  I want to do some real world community building, and 
> > something like this will go a long way to get a cooperative business up and 
> > running.
> >  
> > Furthermore... you do realize that asking another programmer to "just show 
> > me your code" is exactly the same as asking a girl to "just show me your 
> > breasts", right?  I mean, I have nothing against it in principle, but, my 
> > god... I hardly know ye!!!
> >  
> > My lastest work includes that rubber-band selection feature as well as 
> > dropping icons directly onto folder icons (with that "open folder" hover 
> > trick).  I have also included some basic image file support.
> >  
> > Latest video here: http://www.youtube.com/watch?v=jL5r0b7WWvU
> > On Friday, October 5, 2012 5:56:26 PM UTC-4, sotonin wrote:
> > > Code post it else Zzzz
> > >  
> > > On Fri, Oct 5, 2012 at 4:37 PM, Dennis Kane  wrote:
> > > > See the newest features here--> 
> > > > http://www.youtube.com/watch?v=pF_2DwueGLM
> > > >  
> > > > The current version of the program now includes drag and drop 
> > > > functionality of text files from the native desktop straight into the 
> > > > browser desktop or (any of the subfolders). The difference between my 
> > > > drag and drop and all the HTML5 demos that you see on the web is that 
> > > > the dropped files immediately become icons that are integrated into the 
> > > > program.  
> > > >  
> > > > I will soon start working on getting multimedia icons/files working, so 
> > > > you'll be able to drop those directly in too.  Then I will probably do 
> > > > a very basic kind of image editing demo that will allow you to change 
> > > > individual pixels or some such nonsense.  But I don't want to get 
> > > > bogged down in the details of any particular application, because I 
> > > > always want to stay focused on the big picture of creating a totally 
> > > > powerful and intuitive way to organize our online lives.  
> > > >  
> > > > Anyway, I know I am quite a controversial figure here, but there should 
> > > > be no controversy that this thing is just about ready for prime time.  
> > > > I really do need to start getting interested people on board who would 
> > > > like to help me push the web forward.  The basic mission statement for 
> > > > the venture will basically be that the "old web" (HTML4/version 1.0) is 
> > > > dead and gone.  If anyone calls in search of help on their Flintstone 
> > > > era  documents with all of their  and  tags laying 
> > > > about, we'll just point them in an entirely new direction.  If they 
> > > > still insist on doing things the old way, we'll just hang up on them…  
> > > > This thing is all about the future!  
> > > >  
> > > > We can easily develop libraries of high-level interface widgets that 
> > > > people just need to attach event listeners to.  There will be no angle 
> > > > brackets in sight! 
> > > > !  
> > > >  
> > > > Come one, come all, for the thrill of your lives :)
> > > >  
> > > >  
> > > > On Tuesday, September 25, 2012 7:36:37 PM UTC-4, Dennis Kane wrote:
> > > > > I was thinking of just responding  to this old thread 
> > > > > (https://groups.google.com/forum/?fromgroups=#!topic/nodejs/bEhSbsm24Y4),
> > > > >  in which I talk about the browser based Desktop that I've been 
> > > > > working on, but the new thing I've been doing for the past week is so 
> > > > > superior that I thought it deserved a completely new thead.  By the 
> > > > > way, I know this forum is all about server side Javascript, but there 
> > > > > is not really any serious place one can go on the web that talks 
> > > > > about the client side.  Besides, with socket.io (http://socket.io) & 
> > > > > websockets... I 

[nodejs] Re: Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Simon]

a) Go for it. API-breaking changes are somewhat expected in Node and the 
quality and consistency of Node's API is one of it's strongest points. Keep 
the quality high even if you make a few breaking changes pre-1.0. The 
sooner the better.


On Tuesday, October 9, 2012 6:24:36 AM UTC+7, Isaac Schlueter wrote:
>
> Currently, the crypto module defaults to using 'binary' encoded 
> strings everywhere as the default input and output encoding. 
>
> This is problematic for a few reasons: 
>
> 1. It's slower than necessary. 
> 2. It doesn't match the rest of Node. 
>
> The reason for this is that crypto predates Buffers, and no one ever 
> bothered to go through and change it.  (The same reason it's got some 
> odd hodgepodge of update/digest methods vs the Stream interface you 
> see everywhere else in node.) 
>
> The reason it persists in 0.8 (and perhaps in 0.10) is that we 
> (perhaps overly optimistically) labelled that API "stable", and don't 
> want to break anyone's programs.  It's going to change eventually to 
> match the rest of node.  The only question is whether the change will 
> come in 0.10 or 0.12.  A stream interface to all the crypto classes is 
> coming in 0.10; using 'binary' strings by default is thus even more 
> obviously a departure from the rest of node. 
>
> Note that, if you only use crypto for hashes, and set the 'hex' 
> encoding, then it won't affect you.  If you only ever pass the output 
> of one crypto function to the input of another (sign/verify, for 
> example) then it also won't affect you; you'll just pass buffers 
> around instead of binary strings. 
>
> Please select one, and reply with your choice and perhaps any other 
> feedback you have on this issue.  Thanks. 
>
> a) Go for it.  This won't affect me, and if by chance it does, I don't 
> mind putting 'binary' args here and there. 
> b) Please wait.  Mark the API as unstable in 0.10, but don't change it 
> until 0.12. 
> c) I have no opinion, because I don't use the crypto API directly. 
>
>
> (Disclaimer: Node is not a democracy.  The "winning" vote might still 
> be out-voted by reasonable considerations of the core dev team.  This 
> is informative only ;) 
>

-- 
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: Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Andrey]

a) Go for it. This will probably affect me, but I'll be happy to change 
code for better

On Tuesday, 9 October 2012 10:24:36 UTC+11, Isaac Schlueter wrote:
>
> Currently, the crypto module defaults to using 'binary' encoded 
> strings everywhere as the default input and output encoding. 
>
> This is problematic for a few reasons: 
>
> 1. It's slower than necessary. 
> 2. It doesn't match the rest of Node. 
>
> The reason for this is that crypto predates Buffers, and no one ever 
> bothered to go through and change it.  (The same reason it's got some 
> odd hodgepodge of update/digest methods vs the Stream interface you 
> see everywhere else in node.) 
>
> The reason it persists in 0.8 (and perhaps in 0.10) is that we 
> (perhaps overly optimistically) labelled that API "stable", and don't 
> want to break anyone's programs.  It's going to change eventually to 
> match the rest of node.  The only question is whether the change will 
> come in 0.10 or 0.12.  A stream interface to all the crypto classes is 
> coming in 0.10; using 'binary' strings by default is thus even more 
> obviously a departure from the rest of node. 
>
> Note that, if you only use crypto for hashes, and set the 'hex' 
> encoding, then it won't affect you.  If you only ever pass the output 
> of one crypto function to the input of another (sign/verify, for 
> example) then it also won't affect you; you'll just pass buffers 
> around instead of binary strings. 
>
> Please select one, and reply with your choice and perhaps any other 
> feedback you have on this issue.  Thanks. 
>
> a) Go for it.  This won't affect me, and if by chance it does, I don't 
> mind putting 'binary' args here and there. 
> b) Please wait.  Mark the API as unstable in 0.10, but don't change it 
> until 0.12. 
> c) I have no opinion, because I don't use the crypto API directly. 
>
>
> (Disclaimer: Node is not a democracy.  The "winning" vote might still 
> be out-voted by reasonable considerations of the core dev team.  This 
> is informative only ;) 
>

-- 
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: "Evil OS X"... the perfect client to a node server!

[Joshua Gross]

Dennis, this is a developer forum. If you want to peddle your software and 
aren't willing to show something besides videos, you're in the wrong place. 

Also I'm not going to watch a 15 minute video. You're not selling yourself very 
well, I kindly advise you to move on so this stops clogging my inbox :)

-- Joshua Gross
Christian / SpanDeX / BA Candidate of Computer Science, UW-Madison 2013
414-377-1041 / http://www.joshisgross.com

On Oct 8, 2012, at 7:12 PM, Dennis Kane  wrote:

> Why do you want the code so bad?  It's not like there's any kind of fancy 
> algorithms at work.  There are many many open source windowing packages out 
> there.  It's not exactly rocket science, this.  It's all been done many times 
> before.  The only difference is that this one is *my* baby!  Besides, you are 
> welcome to all the code of my desktop prototype on my site at 
> luvluvluv.info... it's just sitting there on the server for the taking.
> 
> I am mainly using this thing as blackmail to get people to be interested in 
> being my friend.  I want to do some real world community building, and 
> something like this will go a long way to get a cooperative business up and 
> running.
> 
> Furthermore... you do realize that asking another programmer to "just show me 
> your code" is exactly the same as asking a girl to "just show me your 
> breasts", right?  I mean, I have nothing against it in principle, but, my 
> god... I hardly know ye!!!
> 
> My lastest work includes that rubber-band selection feature as well as 
> dropping icons directly onto folder icons (with that "open folder" hover 
> trick).  I have also included some basic image file support.
> 
> Latest video here: http://www.youtube.com/watch?v=jL5r0b7WWvU
> 
> On Friday, October 5, 2012 5:56:26 PM UTC-4, sotonin wrote:
> Code post it else Zzzz
> 
> On Fri, Oct 5, 2012 at 4:37 PM, Dennis Kane  wrote:
> See the newest features here--> http://www.youtube.com/watch?v=pF_2DwueGLM
> 
> The current version of the program now includes drag and drop functionality 
> of text files from the native desktop straight into the browser desktop or 
> (any of the subfolders). The difference between my drag and drop and all the 
> HTML5 demos that you see on the web is that the dropped files immediately 
> become icons that are integrated into the program.
> 
> I will soon start working on getting multimedia icons/files working, so 
> you'll be able to drop those directly in too.  Then I will probably do a very 
> basic kind of image editing demo that will allow you to change individual 
> pixels or some such nonsense.  But I don't want to get bogged down in the 
> details of any particular application, because I always want to stay focused 
> on the big picture of creating a totally powerful and intuitive way to 
> organize our online lives.
> 
> Anyway, I know I am quite a controversial figure here, but there should be no 
> controversy that this thing is just about ready for prime time.  I really do 
> need to start getting interested people on board who would like to help me 
> push the web forward.  The basic mission statement for the venture will 
> basically be that the "old web" (HTML4/version 1.0) is dead and gone.  If 
> anyone calls in search of help on their Flintstone era  documents with 
> all of their  and  tags laying about, we'll just point them in 
> an entirely new direction.  If they still insist on doing things the old way, 
> we'll just hang up on them…  This thing is all about the future!
> 
> We can easily develop libraries of high-level interface widgets that people 
> just need to attach event listeners to.  There will be no angle brackets in 
> sight! !
> 
> Come one, come all, for the thrill of your lives :)
> 
> 
> On Tuesday, September 25, 2012 7:36:37 PM UTC-4, Dennis Kane wrote:
> I was thinking of just responding  to this old thread, in which I talk about 
> the browser based Desktop that I've been working on, but the new thing I've 
> been doing for the past week is so superior that I thought it deserved a 
> completely new thead.  By the way, I know this forum is all about server side 
> Javascript, but there is not really any serious place one can go on the web 
> that talks about the client side.  Besides, with socket.io & websockets... I 
> don't really make much of a distinction between client and server anymore.  I 
> just know that there's no reason to do a document.getElementById() call in 
> node :)
> 
> This new thing is a totally shocking clone of OS X.  I knew I was going to 
> have to start over from the ground up, because my previous code base was so 
> sh*tty, haha!  I have really been concentrating on getting a nice, tight 
> little API that developers will positively drool over.  I don't want to make 
> this thing publicly available for many reasons... but you can check out a 
> youtube vid (http://www.youtube.com/watch?v=Tq_W19QokXk) that shows it in 
> action, and I still have my same old crappy prototype online 

[nodejs] Re: Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Bradley Meck]

a. who is actually messing with crypto after the fact. I would like to know 
the reasons to do so.

On Monday, October 8, 2012 6:24:36 PM UTC-5, Isaac Schlueter wrote:
>
> Currently, the crypto module defaults to using 'binary' encoded 
> strings everywhere as the default input and output encoding. 
>
> This is problematic for a few reasons: 
>
> 1. It's slower than necessary. 
> 2. It doesn't match the rest of Node. 
>
> The reason for this is that crypto predates Buffers, and no one ever 
> bothered to go through and change it.  (The same reason it's got some 
> odd hodgepodge of update/digest methods vs the Stream interface you 
> see everywhere else in node.) 
>
> The reason it persists in 0.8 (and perhaps in 0.10) is that we 
> (perhaps overly optimistically) labelled that API "stable", and don't 
> want to break anyone's programs.  It's going to change eventually to 
> match the rest of node.  The only question is whether the change will 
> come in 0.10 or 0.12.  A stream interface to all the crypto classes is 
> coming in 0.10; using 'binary' strings by default is thus even more 
> obviously a departure from the rest of node. 
>
> Note that, if you only use crypto for hashes, and set the 'hex' 
> encoding, then it won't affect you.  If you only ever pass the output 
> of one crypto function to the input of another (sign/verify, for 
> example) then it also won't affect you; you'll just pass buffers 
> around instead of binary strings. 
>
> Please select one, and reply with your choice and perhaps any other 
> feedback you have on this issue.  Thanks. 
>
> a) Go for it.  This won't affect me, and if by chance it does, I don't 
> mind putting 'binary' args here and there. 
> b) Please wait.  Mark the API as unstable in 0.10, but don't change it 
> until 0.12. 
> c) I have no opinion, because I don't use the crypto API directly. 
>
>
> (Disclaimer: Node is not a democracy.  The "winning" vote might still 
> be out-voted by reasonable considerations of the core dev team.  This 
> is informative only ;) 
>

-- 
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: Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Austin William Wright]

(a) Yes, *please.* Changes in the behavior of binary strings, and the usage 
of binary strings alone, has hurt me in the past.

And even if Node.js *was* version 1.0.0, that's still no excuse to not 
improve the API.

It should go without saying, remember to document and announce the behavior 
change accordingly.

On Monday, October 8, 2012 4:24:36 PM UTC-7, Isaac Schlueter wrote:
>
> Currently, the crypto module defaults to using 'binary' encoded 
> strings everywhere as the default input and output encoding. 
>
> This is problematic for a few reasons: 
>
> 1. It's slower than necessary. 
> 2. It doesn't match the rest of Node. 
>
> The reason for this is that crypto predates Buffers, and no one ever 
> bothered to go through and change it.  (The same reason it's got some 
> odd hodgepodge of update/digest methods vs the Stream interface you 
> see everywhere else in node.) 
>
> The reason it persists in 0.8 (and perhaps in 0.10) is that we 
> (perhaps overly optimistically) labelled that API "stable", and don't 
> want to break anyone's programs.  It's going to change eventually to 
> match the rest of node.  The only question is whether the change will 
> come in 0.10 or 0.12.  A stream interface to all the crypto classes is 
> coming in 0.10; using 'binary' strings by default is thus even more 
> obviously a departure from the rest of node. 
>
> Note that, if you only use crypto for hashes, and set the 'hex' 
> encoding, then it won't affect you.  If you only ever pass the output 
> of one crypto function to the input of another (sign/verify, for 
> example) then it also won't affect you; you'll just pass buffers 
> around instead of binary strings. 
>
> Please select one, and reply with your choice and perhaps any other 
> feedback you have on this issue.  Thanks. 
>
> a) Go for it.  This won't affect me, and if by chance it does, I don't 
> mind putting 'binary' args here and there. 
> b) Please wait.  Mark the API as unstable in 0.10, but don't change it 
> until 0.12. 
> c) I have no opinion, because I don't use the crypto API directly. 
>
>
> (Disclaimer: Node is not a democracy.  The "winning" vote might still 
> be out-voted by reasonable considerations of the core dev team.  This 
> is informative only ;) 
>

-- 
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: "Evil OS X"... the perfect client to a node server!

[Sotonin]

+1 for this

On Mon, Oct 8, 2012 at 9:31 PM, Rick Waldron  wrote:

>  Is it possible to have this address banned?
>
> -Rick
>
> On Monday, October 8, 2012 at 8:12 PM, Dennis Kane wrote:
>
> Why do you want the code so bad?  It's not like there's any kind of fancy
> algorithms at work.  There are many many open source windowing packages out
> there.  It's not exactly rocket science, this.  It's all been done many
> times before.  The only difference is that this one is *my* baby!  Besides,
> you are welcome to all the code of my desktop prototype on my site at
> luvluvluv.info... it's just sitting there on the server for the taking.
>
> I am mainly using this thing as blackmail to get people to be interested
> in being my friend.  I want to do some real world community building, and
> something like this will go a long way to get a cooperative business up and
> running.
>
> Furthermore... you do realize that asking another programmer to "just show
> me your code" is exactly the same as asking a girl to "just show me your
> breasts", right?  I mean, I have nothing against it in principle, but, my
> god... I hardly know ye!!!
>
> My lastest work includes that rubber-band selection feature as well as
> dropping icons directly onto folder icons (with that "open folder" hover
> trick).  I have also included some basic image file support.
>
> Latest video here: http://www.youtube.com/watch?v=jL5r0b7WWvU
>
> On Friday, October 5, 2012 5:56:26 PM UTC-4, sotonin wrote:
>
> Code post it else Zzzz
>
> On Fri, Oct 5, 2012 at 4:37 PM, Dennis Kane  wrote:
>
> See the newest features here--> http://www.youtube.**
> com/watch?v=pF_2DwueGLM 
>
> The current version of the program now includes drag and drop
> functionality of text files from the native desktop straight into the
> browser desktop or (any of the subfolders). The difference between my drag
> and drop and all the HTML5 demos that you see on the web is that the
> dropped files immediately become icons that are integrated into the program.
>
> I will soon start working on getting multimedia icons/files working, so
> you'll be able to drop those directly in too.  Then I will probably do a
> very basic kind of image editing demo that will allow you to change
> individual pixels or some such nonsense.  But I don't want to get bogged
> down in the details of any particular application, because I always want to
> stay focused on the big picture of creating a totally powerful and
> intuitive way to organize our online lives.
>
> Anyway, I know I am quite a controversial figure here, but there should be
> no controversy that this thing is just about ready for prime time.  I
> really do need to start getting interested people on board who would like
> to help me push the web forward.  The basic mission statement for the
> venture will basically be that the "old web" (HTML4/version 1.0) is dead
> and gone.  If anyone calls in search of help on their Flintstone era 
> documents with all of their  and  tags laying about, we'll
> just point them in an entirely new direction.  If they still insist on
> doing things the old way, we'll just hang up on them…  This thing is all
> about the future!
>
> We can easily develop libraries of high-level interface widgets that
> people just need to attach event listeners to.  There will be no angle
> brackets in sight!  is>!
>
> Come one, come all, for the thrill of your lives :)
>
>
> On Tuesday, September 25, 2012 7:36:37 PM UTC-4, Dennis Kane wrote:
>
> I was thinking of just responding  to this old 
> thread,
> in which I talk about the browser based Desktop that I've been working on,
> but the new thing I've been doing for the past week is so superior that I
> thought it deserved a completely new thead.  By the way, I know this forum
> is all about server side Javascript, but there is not really any serious
> place one can go on the web that talks about the client side.  Besides,
> with socket.io & websockets... I don't really make much of a distinction
> between client and server anymore.  I just know that there's no reason to
> do a document.getElementById() call in node :)
>
> This new thing is a totally shocking clone of OS X.  I knew I was going to
> have to start over from the ground up, because my previous code base was so
> sh*tty, haha!  I have really been concentrating on getting a nice, tight
> little API that developers will positively drool over.  I don't want to
> make this thing publicly available for many reasons... but you can check
> out a youtube vid 
> (http://www.youtube.com/watch?v=Tq_W19QokXk)
>  that
> shows it in action, and I still have my same old crappy prototype online at
> http://luvluvluv.info.  Well, hopefully this is proof that I am able to
> do some cool stuff, and hopefully summa yous will want to start being my
> friend now, LOL!

Re: [nodejs] Re: "Evil OS X"... the perfect client to a node server!

[Rick Waldron]

Is it possible to have this address banned?  

-Rick


On Monday, October 8, 2012 at 8:12 PM, Dennis Kane wrote:

> Why do you want the code so bad?  It's not like there's any kind of fancy 
> algorithms at work.  There are many many open source windowing packages out 
> there.  It's not exactly rocket science, this.  It's all been done many times 
> before.  The only difference is that this one is *my* baby!  Besides, you are 
> welcome to all the code of my desktop prototype on my site at 
> luvluvluv.info... it's just sitting there on the server for the taking.
>  
> I am mainly using this thing as blackmail to get people to be interested in 
> being my friend.  I want to do some real world community building, and 
> something like this will go a long way to get a cooperative business up and 
> running.
>  
> Furthermore... you do realize that asking another programmer to "just show me 
> your code" is exactly the same as asking a girl to "just show me your 
> breasts", right?  I mean, I have nothing against it in principle, but, my 
> god... I hardly know ye!!!
>  
> My lastest work includes that rubber-band selection feature as well as 
> dropping icons directly onto folder icons (with that "open folder" hover 
> trick).  I have also included some basic image file support.
>  
> Latest video here: http://www.youtube.com/watch?v=jL5r0b7WWvU
> On Friday, October 5, 2012 5:56:26 PM UTC-4, sotonin wrote:
> > Code post it else Zzzz
> >  
> > On Fri, Oct 5, 2012 at 4:37 PM, Dennis Kane  wrote:
> > > See the newest features here--> http://www.youtube.com/watch?v=pF_2DwueGLM
> > >  
> > > The current version of the program now includes drag and drop 
> > > functionality of text files from the native desktop straight into the 
> > > browser desktop or (any of the subfolders). The difference between my 
> > > drag and drop and all the HTML5 demos that you see on the web is that the 
> > > dropped files immediately become icons that are integrated into the 
> > > program.  
> > >  
> > > I will soon start working on getting multimedia icons/files working, so 
> > > you'll be able to drop those directly in too.  Then I will probably do a 
> > > very basic kind of image editing demo that will allow you to change 
> > > individual pixels or some such nonsense.  But I don't want to get bogged 
> > > down in the details of any particular application, because I always want 
> > > to stay focused on the big picture of creating a totally powerful and 
> > > intuitive way to organize our online lives.  
> > >  
> > > Anyway, I know I am quite a controversial figure here, but there should 
> > > be no controversy that this thing is just about ready for prime time.  I 
> > > really do need to start getting interested people on board who would like 
> > > to help me push the web forward.  The basic mission statement for the 
> > > venture will basically be that the "old web" (HTML4/version 1.0) is dead 
> > > and gone.  If anyone calls in search of help on their Flintstone era 
> > >  documents with all of their  and  tags laying about, 
> > > we'll just point them in an entirely new direction.  If they still insist 
> > > on doing things the old way, we'll just hang up on them…  This thing is 
> > > all about the future!  
> > >  
> > > We can easily develop libraries of high-level interface widgets that 
> > > people just need to attach event listeners to.  There will be no angle 
> > > brackets in sight! 
> > > !  
> > >  
> > > Come one, come all, for the thrill of your lives :)
> > >  
> > >  
> > > On Tuesday, September 25, 2012 7:36:37 PM UTC-4, Dennis Kane wrote:
> > > > I was thinking of just responding  to this old thread 
> > > > (https://groups.google.com/forum/?fromgroups=#!topic/nodejs/bEhSbsm24Y4),
> > > >  in which I talk about the browser based Desktop that I've been working 
> > > > on, but the new thing I've been doing for the past week is so superior 
> > > > that I thought it deserved a completely new thead.  By the way, I know 
> > > > this forum is all about server side Javascript, but there is not really 
> > > > any serious place one can go on the web that talks about the client 
> > > > side.  Besides, with socket.io (http://socket.io) & websockets... I 
> > > > don't really make much of a distinction between client and server 
> > > > anymore.  I just know that there's no reason to do a 
> > > > document.getElementById() call in node :)
> > > >  
> > > > This new thing is a totally shocking clone of OS X.  I knew I was going 
> > > > to have to start over from the ground up, because my previous code base 
> > > > was so sh*tty, haha!  I have really been concentrating on getting a 
> > > > nice, tight little API that developers will positively drool over.  I 
> > > > don't want to make this thing publicly available for many reasons... 
> > > > but you can check out a youtube vid 
> > > > (http://www.youtube.com/watch?v=Tq_W19QokXk) that shows it in action, 
> > > > and I still have my same 

Re: [nodejs] Re: Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[codepilot Account]

I agree. We aren't to version 1.0 yet, so anything should be fair game.
On Oct 8, 2012 7:19 PM, "mscdex"  wrote:

> a) times 1
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "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: Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[mscdex]

a) times 1

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Node.jar - Java port by Oracle

[Ben Noordhuis]

On Tue, Oct 9, 2012 at 2:21 AM, Stewart Mckinney  wrote:
> I'm just curious as to why having Node run on top of the Java run time is
> better than say, vanilla C++ compiled Node running naively. Doesn't it run
> on pretty much every popular platform now, anyway?

The major ones, yes. But there are some high margin, low volume
architectures like POWER and S/390 that V8 doesn't support (and hence
node.js) but the JVM does. Think AIX, mainframes, etc.

There has been some corporate interest in running node on such
architectures but the time and money to get (and keep) it ported isn't
worth it. node.jar could be a viable alternative.

-- 
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: Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Lois]

a) do the right thing as soon as possible. It affects me, but this is such 
a minor issue to resolve.

On Monday, October 8, 2012 4:24:36 PM UTC-7, Isaac Schlueter wrote:
>
> Currently, the crypto module defaults to using 'binary' encoded 
> strings everywhere as the default input and output encoding. 
>
> This is problematic for a few reasons: 
>
> 1. It's slower than necessary. 
> 2. It doesn't match the rest of Node. 
>
> The reason for this is that crypto predates Buffers, and no one ever 
> bothered to go through and change it.  (The same reason it's got some 
> odd hodgepodge of update/digest methods vs the Stream interface you 
> see everywhere else in node.) 
>
> The reason it persists in 0.8 (and perhaps in 0.10) is that we 
> (perhaps overly optimistically) labelled that API "stable", and don't 
> want to break anyone's programs.  It's going to change eventually to 
> match the rest of node.  The only question is whether the change will 
> come in 0.10 or 0.12.  A stream interface to all the crypto classes is 
> coming in 0.10; using 'binary' strings by default is thus even more 
> obviously a departure from the rest of node. 
>
> Note that, if you only use crypto for hashes, and set the 'hex' 
> encoding, then it won't affect you.  If you only ever pass the output 
> of one crypto function to the input of another (sign/verify, for 
> example) then it also won't affect you; you'll just pass buffers 
> around instead of binary strings. 
>
> Please select one, and reply with your choice and perhaps any other 
> feedback you have on this issue.  Thanks. 
>
> a) Go for it.  This won't affect me, and if by chance it does, I don't 
> mind putting 'binary' args here and there. 
> b) Please wait.  Mark the API as unstable in 0.10, but don't change it 
> until 0.12. 
> c) I have no opinion, because I don't use the crypto API directly. 
>
>
> (Disclaimer: Node is not a democracy.  The "winning" vote might still 
> be out-voted by reasonable considerations of the core dev team.  This 
> is informative only ;) 
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Node.jar - Java port by Oracle

[Stewart Mckinney]

*natively. Christ.

On Mon, Oct 8, 2012 at 8:21 PM, Stewart Mckinney wrote:

> I'm just curious as to why having Node run on top of the Java run time is
> better than say, vanilla C++ compiled Node running naively. Doesn't it run
> on pretty much every popular platform now, anyway?
>
> If you are going to build out new services in Node.js, why not simply
> create auxiliary architecture to support it? Service layers don't need to
> be physically integrated, although I can see the argument from an
> "gee this is gonna be easier to convince my IT department to do"
> perspective.
>
> To me it just seems like an interesting exercise, not anything truly
> practical, although I don't mind being educated in the matter.
>
>
> On Mon, Oct 8, 2012 at 6:10 PM, Patrick Mueller  wrote:
>
>> On 10/4/12 1:16 PM, Jonathan Buchanan wrote:
>>
>>> I'm at JavaOne, for my sins, and I've been attending all the sessions
>>> related to Oracle's new JavaScript implementation in Java, called Nashorn.
>>>
>>> What initially caught my eye was that they're also porting the Node.js
>>> APIs, module system etc. in a project called Node.jar.
>>>
>> For folks interested in "node on Java", there's a project out there
>> called SprintStack which - as near as I can tell - also aims to provide
>> "node" on Java.
>>
>> http://sprintstack.com/
>>
>> I have no experience with it, just happened to notice it a while back.
>>
>>
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List-**
>> Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscribe@**googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/**group/nodejs?hl=en?hl=en
>>
>
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Node.jar - Java port by Oracle

[Stewart Mckinney]

I'm just curious as to why having Node run on top of the Java run time is
better than say, vanilla C++ compiled Node running naively. Doesn't it run
on pretty much every popular platform now, anyway?

If you are going to build out new services in Node.js, why not simply
create auxiliary architecture to support it? Service layers don't need to
be physically integrated, although I can see the argument from an
"gee this is gonna be easier to convince my IT department to do"
perspective.

To me it just seems like an interesting exercise, not anything truly
practical, although I don't mind being educated in the matter.

On Mon, Oct 8, 2012 at 6:10 PM, Patrick Mueller  wrote:

> On 10/4/12 1:16 PM, Jonathan Buchanan wrote:
>
>> I'm at JavaOne, for my sins, and I've been attending all the sessions
>> related to Oracle's new JavaScript implementation in Java, called Nashorn.
>>
>> What initially caught my eye was that they're also porting the Node.js
>> APIs, module system etc. in a project called Node.jar.
>>
> For folks interested in "node on Java", there's a project out there called
> SprintStack which - as near as I can tell - also aims to provide "node" on
> Java.
>
> http://sprintstack.com/
>
> I have no experience with it, just happened to notice it a while back.
>
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List-**
> Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscribe@**googlegroups.com
> For more options, visit this group at
> http://groups.google.com/**group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Re: "Evil OS X"... the perfect client to a node server!

[Dennis Kane]

Why do you want the code so bad?  It's not like there's any kind of fancy 
algorithms at work.  There are many many open source windowing packages out 
there.  It's not exactly rocket science, this.  It's all been done many 
times before.  The only difference is that this one is *my* baby!  Besides, 
you are welcome to all the code of my desktop prototype on my site at 
luvluvluv.info... it's just sitting there on the server for the taking.

I am mainly using this thing as blackmail to get people to be interested in 
being my friend.  I want to do some real world community building, and 
something like this will go a long way to get a cooperative business up and 
running.

Furthermore... you do realize that asking another programmer to "just show 
me your code" is exactly the same as asking a girl to "just show me your 
breasts", right?  I mean, I have nothing against it in principle, but, my 
god... I hardly know ye!!!

My lastest work includes that rubber-band selection feature as well as 
dropping icons directly onto folder icons (with that "open folder" hover 
trick).  I have also included some basic image file support.

Latest video here: http://www.youtube.com/watch?v=jL5r0b7WWvU

On Friday, October 5, 2012 5:56:26 PM UTC-4, sotonin wrote:
>
> Code post it else Zzzz
>
> On Fri, Oct 5, 2012 at 4:37 PM, Dennis Kane 
> > wrote:
>
>> See the newest features here--> 
>> http://www.youtube.com/watch?v=pF_2DwueGLM
>>
>> The current version of the program now includes drag and drop 
>> functionality of text files from the native desktop straight into the 
>> browser desktop or (any of the subfolders). The difference between my drag 
>> and drop and all the HTML5 demos that you see on the web is that the 
>> dropped files immediately become icons that are integrated into the program.
>>
>> I will soon start working on getting multimedia icons/files working, so 
>> you'll be able to drop those directly in too.  Then I will probably do a 
>> very basic kind of image editing demo that will allow you to change 
>> individual pixels or some such nonsense.  But I don't want to get bogged 
>> down in the details of any particular application, because I always want to 
>> stay focused on the big picture of creating a totally powerful and 
>> intuitive way to organize our online lives.
>>
>> Anyway, I know I am quite a controversial figure here, but there should 
>> be no controversy that this thing is just about ready for prime time.  I 
>> really do need to start getting interested people on board who would like 
>> to help me push the web forward.  The basic mission statement for the 
>> venture will basically be that the "old web" (HTML4/version 1.0) is dead 
>> and gone.  If anyone calls in search of help on their Flintstone era  
>> documents with all of their  and  tags laying about, we'll 
>> just point them in an entirely new direction.  If they still insist on 
>> doing things the old way, we'll just hang up on them…  This thing is all 
>> about the future!
>>
>> We can easily develop libraries of high-level interface widgets that 
>> people just need to attach event listeners to.  There will be no angle 
>> brackets in sight! !
>>
>> Come one, come all, for the thrill of your lives :)
>>
>>
>> On Tuesday, September 25, 2012 7:36:37 PM UTC-4, Dennis Kane wrote:
>>
>>> I was thinking of just responding  to this old 
>>> thread,
>>>  
>>> in which I talk about the browser based Desktop that I've been working on, 
>>> but the new thing I've been doing for the past week is so superior that I 
>>> thought it deserved a completely new thead.  By the way, I know this forum 
>>> is all about server side Javascript, but there is not really any serious 
>>> place one can go on the web that talks about the client side.  Besides, 
>>> with socket.io & websockets... I don't really make much of a 
>>> distinction between client and server anymore.  I just know that there's no 
>>> reason to do a document.getElementById() call in node :)
>>>
>>> This new thing is a totally shocking clone of OS X.  I knew I was going 
>>> to have to start over from the ground up, because my previous code base was 
>>> so sh*tty, haha!  I have really been concentrating on getting a nice, tight 
>>> little API that developers will positively drool over.  I don't want to 
>>> make this thing publicly available for many reasons... but you can check 
>>> out a youtube vid 
>>> (http://www.youtube.com/watch?**v=Tq_W19QokXk)
>>>  that 
>>> shows it in action, and I still have my same old crappy prototype online at 
>>> http://luvluvluv.info.  Well, hopefully this is proof that I am able to 
>>> do some cool stuff, and hopefully summa yous will want to start being my 
>>> friend now, LOL!!!
>>>
>>> And get this... the current, uncompressed js file size is only 54kb!
>>>
>>  -- 
>> Job Board: http://jobs.nodejs.org/
>> Posting 

Re: [nodejs] Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Joshua Gross]

I like B) in theory, as a way to manage APIs. Anyone not reading this newsgroup 
will at least have *some* advanced warning. 

-- Joshua Gross
Christian / SpanDeX.io / BA Candidate of Computer Science, UW-Madison 2013
414-377-1041 / http://www.joshisgross.com

On Oct 8, 2012, at 6:24 PM, Isaac Schlueter  wrote:

> Currently, the crypto module defaults to using 'binary' encoded
> strings everywhere as the default input and output encoding.
> 
> This is problematic for a few reasons:
> 
> 1. It's slower than necessary.
> 2. It doesn't match the rest of Node.
> 
> The reason for this is that crypto predates Buffers, and no one ever
> bothered to go through and change it.  (The same reason it's got some
> odd hodgepodge of update/digest methods vs the Stream interface you
> see everywhere else in node.)
> 
> The reason it persists in 0.8 (and perhaps in 0.10) is that we
> (perhaps overly optimistically) labelled that API "stable", and don't
> want to break anyone's programs.  It's going to change eventually to
> match the rest of node.  The only question is whether the change will
> come in 0.10 or 0.12.  A stream interface to all the crypto classes is
> coming in 0.10; using 'binary' strings by default is thus even more
> obviously a departure from the rest of node.
> 
> Note that, if you only use crypto for hashes, and set the 'hex'
> encoding, then it won't affect you.  If you only ever pass the output
> of one crypto function to the input of another (sign/verify, for
> example) then it also won't affect you; you'll just pass buffers
> around instead of binary strings.
> 
> Please select one, and reply with your choice and perhaps any other
> feedback you have on this issue.  Thanks.
> 
> a) Go for it.  This won't affect me, and if by chance it does, I don't
> mind putting 'binary' args here and there.
> b) Please wait.  Mark the API as unstable in 0.10, but don't change it
> until 0.12.
> c) I have no opinion, because I don't use the crypto API directly.
> 
> 
> (Disclaimer: Node is not a democracy.  The "winning" vote might still
> be out-voted by reasonable considerations of the core dev team.  This
> is informative only ;)
> 
> -- 
> Job Board: http://jobs.nodejs.org/
> Posting guidelines: 
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Andrew Stone]

Go For it.

On Mon, Oct 8, 2012 at 7:41 PM, Michael Schoonmaker <
michael.r.schoonma...@gmail.com> wrote:

> My vote is a', "Please for the love of all that is holy go for it." The
> incongruence is annoying, and I have to context-switch every time I work
> with our crypto code.
>
>
> On Mon, Oct 8, 2012 at 4:33 PM, Joshua Holbrook 
> wrote:
>
>> I say go for it. :)
>>
>> --Josh
>>
>> On Mon, Oct 8, 2012 at 4:24 PM, Isaac Schlueter  wrote:
>> > Currently, the crypto module defaults to using 'binary' encoded
>> > strings everywhere as the default input and output encoding.
>> >
>> > This is problematic for a few reasons:
>> >
>> > 1. It's slower than necessary.
>> > 2. It doesn't match the rest of Node.
>> >
>> > The reason for this is that crypto predates Buffers, and no one ever
>> > bothered to go through and change it.  (The same reason it's got some
>> > odd hodgepodge of update/digest methods vs the Stream interface you
>> > see everywhere else in node.)
>> >
>> > The reason it persists in 0.8 (and perhaps in 0.10) is that we
>> > (perhaps overly optimistically) labelled that API "stable", and don't
>> > want to break anyone's programs.  It's going to change eventually to
>> > match the rest of node.  The only question is whether the change will
>> > come in 0.10 or 0.12.  A stream interface to all the crypto classes is
>> > coming in 0.10; using 'binary' strings by default is thus even more
>> > obviously a departure from the rest of node.
>> >
>> > Note that, if you only use crypto for hashes, and set the 'hex'
>> > encoding, then it won't affect you.  If you only ever pass the output
>> > of one crypto function to the input of another (sign/verify, for
>> > example) then it also won't affect you; you'll just pass buffers
>> > around instead of binary strings.
>> >
>> > Please select one, and reply with your choice and perhaps any other
>> > feedback you have on this issue.  Thanks.
>> >
>> > a) Go for it.  This won't affect me, and if by chance it does, I don't
>> > mind putting 'binary' args here and there.
>> > b) Please wait.  Mark the API as unstable in 0.10, but don't change it
>> > until 0.12.
>> > c) I have no opinion, because I don't use the crypto API directly.
>> >
>> >
>> > (Disclaimer: Node is not a democracy.  The "winning" vote might still
>> > be out-voted by reasonable considerations of the core dev team.  This
>> > is informative only ;)
>> >
>> > --
>> > 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
>>
>>
>>
>> --
>> Joshua Holbrook
>> Head of Support
>> Nodejitsu Inc.
>> j...@nodejitsu.com
>>
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>
>  --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[codepilot Account]

a)

On Mon, Oct 8, 2012 at 4:41 PM, Michael Schoonmaker <
michael.r.schoonma...@gmail.com> wrote:

> My vote is a', "Please for the love of all that is holy go for it." The
> incongruence is annoying, and I have to context-switch every time I work
> with our crypto code.
>
>
> On Mon, Oct 8, 2012 at 4:33 PM, Joshua Holbrook 
> wrote:
>
>> I say go for it. :)
>>
>> --Josh
>>
>> On Mon, Oct 8, 2012 at 4:24 PM, Isaac Schlueter  wrote:
>> > Currently, the crypto module defaults to using 'binary' encoded
>> > strings everywhere as the default input and output encoding.
>> >
>> > This is problematic for a few reasons:
>> >
>> > 1. It's slower than necessary.
>> > 2. It doesn't match the rest of Node.
>> >
>> > The reason for this is that crypto predates Buffers, and no one ever
>> > bothered to go through and change it.  (The same reason it's got some
>> > odd hodgepodge of update/digest methods vs the Stream interface you
>> > see everywhere else in node.)
>> >
>> > The reason it persists in 0.8 (and perhaps in 0.10) is that we
>> > (perhaps overly optimistically) labelled that API "stable", and don't
>> > want to break anyone's programs.  It's going to change eventually to
>> > match the rest of node.  The only question is whether the change will
>> > come in 0.10 or 0.12.  A stream interface to all the crypto classes is
>> > coming in 0.10; using 'binary' strings by default is thus even more
>> > obviously a departure from the rest of node.
>> >
>> > Note that, if you only use crypto for hashes, and set the 'hex'
>> > encoding, then it won't affect you.  If you only ever pass the output
>> > of one crypto function to the input of another (sign/verify, for
>> > example) then it also won't affect you; you'll just pass buffers
>> > around instead of binary strings.
>> >
>> > Please select one, and reply with your choice and perhaps any other
>> > feedback you have on this issue.  Thanks.
>> >
>> > a) Go for it.  This won't affect me, and if by chance it does, I don't
>> > mind putting 'binary' args here and there.
>> > b) Please wait.  Mark the API as unstable in 0.10, but don't change it
>> > until 0.12.
>> > c) I have no opinion, because I don't use the crypto API directly.
>> >
>> >
>> > (Disclaimer: Node is not a democracy.  The "winning" vote might still
>> > be out-voted by reasonable considerations of the core dev team.  This
>> > is informative only ;)
>> >
>> > --
>> > 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
>>
>>
>>
>> --
>> Joshua Holbrook
>> Head of Support
>> Nodejitsu Inc.
>> j...@nodejitsu.com
>>
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>
>  --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Michael Schoonmaker]

My vote is a', "Please for the love of all that is holy go for it." The
incongruence is annoying, and I have to context-switch every time I work
with our crypto code.

On Mon, Oct 8, 2012 at 4:33 PM, Joshua Holbrook wrote:

> I say go for it. :)
>
> --Josh
>
> On Mon, Oct 8, 2012 at 4:24 PM, Isaac Schlueter  wrote:
> > Currently, the crypto module defaults to using 'binary' encoded
> > strings everywhere as the default input and output encoding.
> >
> > This is problematic for a few reasons:
> >
> > 1. It's slower than necessary.
> > 2. It doesn't match the rest of Node.
> >
> > The reason for this is that crypto predates Buffers, and no one ever
> > bothered to go through and change it.  (The same reason it's got some
> > odd hodgepodge of update/digest methods vs the Stream interface you
> > see everywhere else in node.)
> >
> > The reason it persists in 0.8 (and perhaps in 0.10) is that we
> > (perhaps overly optimistically) labelled that API "stable", and don't
> > want to break anyone's programs.  It's going to change eventually to
> > match the rest of node.  The only question is whether the change will
> > come in 0.10 or 0.12.  A stream interface to all the crypto classes is
> > coming in 0.10; using 'binary' strings by default is thus even more
> > obviously a departure from the rest of node.
> >
> > Note that, if you only use crypto for hashes, and set the 'hex'
> > encoding, then it won't affect you.  If you only ever pass the output
> > of one crypto function to the input of another (sign/verify, for
> > example) then it also won't affect you; you'll just pass buffers
> > around instead of binary strings.
> >
> > Please select one, and reply with your choice and perhaps any other
> > feedback you have on this issue.  Thanks.
> >
> > a) Go for it.  This won't affect me, and if by chance it does, I don't
> > mind putting 'binary' args here and there.
> > b) Please wait.  Mark the API as unstable in 0.10, but don't change it
> > until 0.12.
> > c) I have no opinion, because I don't use the crypto API directly.
> >
> >
> > (Disclaimer: Node is not a democracy.  The "winning" vote might still
> > be out-voted by reasonable considerations of the core dev team.  This
> > is informative only ;)
> >
> > --
> > 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
>
>
>
> --
> Joshua Holbrook
> Head of Support
> Nodejitsu Inc.
> j...@nodejitsu.com
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Christian Tellnes]

a) Go for it

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Joshua Holbrook]

I say go for it. :)

--Josh

On Mon, Oct 8, 2012 at 4:24 PM, Isaac Schlueter  wrote:
> Currently, the crypto module defaults to using 'binary' encoded
> strings everywhere as the default input and output encoding.
>
> This is problematic for a few reasons:
>
> 1. It's slower than necessary.
> 2. It doesn't match the rest of Node.
>
> The reason for this is that crypto predates Buffers, and no one ever
> bothered to go through and change it.  (The same reason it's got some
> odd hodgepodge of update/digest methods vs the Stream interface you
> see everywhere else in node.)
>
> The reason it persists in 0.8 (and perhaps in 0.10) is that we
> (perhaps overly optimistically) labelled that API "stable", and don't
> want to break anyone's programs.  It's going to change eventually to
> match the rest of node.  The only question is whether the change will
> come in 0.10 or 0.12.  A stream interface to all the crypto classes is
> coming in 0.10; using 'binary' strings by default is thus even more
> obviously a departure from the rest of node.
>
> Note that, if you only use crypto for hashes, and set the 'hex'
> encoding, then it won't affect you.  If you only ever pass the output
> of one crypto function to the input of another (sign/verify, for
> example) then it also won't affect you; you'll just pass buffers
> around instead of binary strings.
>
> Please select one, and reply with your choice and perhaps any other
> feedback you have on this issue.  Thanks.
>
> a) Go for it.  This won't affect me, and if by chance it does, I don't
> mind putting 'binary' args here and there.
> b) Please wait.  Mark the API as unstable in 0.10, but don't change it
> until 0.12.
> c) I have no opinion, because I don't use the crypto API directly.
>
>
> (Disclaimer: Node is not a democracy.  The "winning" vote might still
> be out-voted by reasonable considerations of the core dev team.  This
> is informative only ;)
>
> --
> 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



-- 
Joshua Holbrook
Head of Support
Nodejitsu Inc.
j...@nodejitsu.com

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Re: SyntaxError: invalid syntax - while installing 0.8.1

[Ben Noordhuis]

On Tue, Oct 9, 2012 at 1:07 AM, Dean Flory  wrote:
> I just received this after installing Python 2.7.3:
>
>> # ./configure
>>   File "./configure", line 347
>> o['default_configuration'] = 'Debug' if options.debug else 'Release'
>>   ^
>> SyntaxError: invalid syntax
>
>
> And I'm guessing it's playing a part in why I can't install the newest
> version of Node.js since I can't get past ./configure (where other
> packages/installs succeeded when ./configure was entered).

You may have installed python 2.7 but you're not using it, otherwise
you wouldn't be getting that error. :-)

Try this:

  $ python2.7 configure
  $ make PYTHON=python2.7

Replace python2.7 with whatever the binary is really called.

-- 
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] Poll for v0.10 feature: Crypto default to 'binary' strings vs defaulting to buffers

[Isaac Schlueter]

Currently, the crypto module defaults to using 'binary' encoded
strings everywhere as the default input and output encoding.

This is problematic for a few reasons:

1. It's slower than necessary.
2. It doesn't match the rest of Node.

The reason for this is that crypto predates Buffers, and no one ever
bothered to go through and change it.  (The same reason it's got some
odd hodgepodge of update/digest methods vs the Stream interface you
see everywhere else in node.)

The reason it persists in 0.8 (and perhaps in 0.10) is that we
(perhaps overly optimistically) labelled that API "stable", and don't
want to break anyone's programs.  It's going to change eventually to
match the rest of node.  The only question is whether the change will
come in 0.10 or 0.12.  A stream interface to all the crypto classes is
coming in 0.10; using 'binary' strings by default is thus even more
obviously a departure from the rest of node.

Note that, if you only use crypto for hashes, and set the 'hex'
encoding, then it won't affect you.  If you only ever pass the output
of one crypto function to the input of another (sign/verify, for
example) then it also won't affect you; you'll just pass buffers
around instead of binary strings.

Please select one, and reply with your choice and perhaps any other
feedback you have on this issue.  Thanks.

a) Go for it.  This won't affect me, and if by chance it does, I don't
mind putting 'binary' args here and there.
b) Please wait.  Mark the API as unstable in 0.10, but don't change it
until 0.12.
c) I have no opinion, because I don't use the crypto API directly.


(Disclaimer: Node is not a democracy.  The "winning" vote might still
be out-voted by reasonable considerations of the core dev team.  This
is informative only ;)

-- 
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: SyntaxError: invalid syntax - while installing 0.8.1

[Dean Flory]

I just received this after installing Python 2.7.3:

# ./configure
>   File "./configure", line 347
> o['default_configuration'] = 'Debug' if options.debug else 'Release'
>   ^
> SyntaxError: invalid syntax


And I'm guessing it's playing a part in why I can't install the newest 
version of Node.js since I can't get past ./configure (where other 
packages/installs succeeded when ./configure was entered).


On Friday, June 29, 2012 9:19:25 PM UTC-4, neojp wrote:
>
> Hey guys,
>
> I'm running Node 0.6.15 on CentOS with Python 2.4.3 and for some reason, 
> I'm getting this weird error while trying to install 0.8.1
> Does anyone have any idea on what can I do about it?
>
> $ cd node-v0.8.1
> $ ./configure
>   File "./configure", line 266
> o['default_configuration'] = 'Debug' if options.debug else 'Release'
>   ^
> SyntaxError: invalid syntax
>
>
> 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] Node.jar - Java port by Oracle

[Patrick Mueller]

On 10/4/12 1:16 PM, Jonathan Buchanan wrote:
I'm at JavaOne, for my sins, and I've been attending all the sessions 
related to Oracle's new JavaScript implementation in Java, called Nashorn.


What initially caught my eye was that they're also porting the Node.js 
APIs, module system etc. in a project called Node.jar.
For folks interested in "node on Java", there's a project out there 
called SprintStack which - as near as I can tell - also aims to provide 
"node" on Java.


http://sprintstack.com/

I have no experience with it, just happened to notice it a while back.

--
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] Potential Problem with Node.js Implementation of OpenSSL with large amounts of data

[Ben Noordhuis]

On Sun, Oct 7, 2012 at 11:34 PM, Justin Meltzer  wrote:
> Aww shucks :/
>
> Out of curiosity, how does the _push method on the Cryptostream prototype
> know where one message ends and the other begins?

It doesn't, it feeds openssl encrypted data until decrypted data pops
out at the other side (or vice versa, of course).

> It seems to me that the while/do loop continues to call _pusher (which calls
> SSL_read under the hood) until either the buffer is all used up or the
> SSL_read function can't read anything (it returns -1). Then it'll emit a
> data event only if it has actually read a non-negative number of bytes.
>
> When I was debugging, it occurred to me that maybe the data was coming in
> slowly in chunks so that after it had read the first one or two chunks from
> SSL_read, the next tick of the while loop fired so quickly that it returned
> -1 before the next chunk of data had reached the C buffer. Then it emitted
> this first part of the data as if it were its own isolated grouping. Is this
> possible?

I'm not sure if I'm following you. Encryption and decryption in the
current implementation are synchronous. That while loop in lib/tls.js
doesn't get split over multiple ticks of the event loop.

For the record, SSL and TLS work like this:

1) they are frame based
2) a frame contains one or more messages
3) a message is either a protocol message or data

Frames and messages can span multiple TCP packets. If you feed openssl
input that contains only partial messages, or protocol messages and no
data, nothing comes out at the other side.

-- 
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 JS hosting service in Europe

[remi_grumeau]

Hi!

I'm new to Node, yet doing a lot of JS client-side (no JQuery, real
JS) and i'm looking to develop an app using Node. Main idea is to get
interactions from a mobile phone to control something on a distant
screen.
To do so, i've done a few tests using PubNub service & it's actually
pretty easy to use, prices are low so i'm pretty fine with it. The
thing is PubNub is in California & my app will be used mostly by
western european people.
So i'm looking for the same kind of ready-to-use service like PubNub
is, but hosted in Europe so it may be even quicker (i assume).

Any idea?

Thx a lot!
Remi

-- 
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: "Evil OS X"... the perfect client to a node server!

[Stephen Handley]

http://www.youtube.com/watch?v=udNHsk57f24

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Any resources to help one brush up...?

[Declan de Wet]

Quite surprised you responded to this, your efforts have been a great help 
in my learning haha! It would really nice to have structured quizzes one 
can complete though. Since my first post here I found an IBM one, but it's 
more of a "Correct this code then answer this true/false question and then 
you're finished with the quiz" type thing. Also, I wouldn't really trust 
IBM quizzes on Node.js after I read a response article to an IBM blog post 
on the subject... I'm sure you'll know of the one I'm speaking of. So, 
here's a goal for you devs with free time... structure your knowledge in a 
quiz! :) It'll be of so much help.

On Monday, October 8, 2012 5:43:18 PM UTC+2, Tim Caswell wrote:
>
> The official nodejs API docs are great.  My experience with most 
> people learning nodejs is that they didn't know javascript as well as 
> they had thought.  Node makes heavy use of callbacks and closures. 
> This means that more often the weird aspects of js scoping creep out. 
>
> There are many nodejs specific resources out there.  There have been 
> some threads about this recently in this list you can search through. 
> I haven't heard of anything like the w3schools format (not speaking of 
> the content quality, just format). 
>
> On Mon, Oct 8, 2012 at 5:03 AM, Declan de Wet 
> > 
> wrote: 
> > Hi, 
> > 
> > I am relatively new to Node.js. I heard and researched about it a long 
> time 
> > ago. I'm more familiar with Ruby and PHP, but Node.js has really caught 
> my 
> > attention lately. I am familiar with Javascript for basic interactivity 
> and 
> > the popular libraries to go with it. I've done some tutorials and so on 
> and 
> > I've been competent enough to find many guides, books, blogs, 
> screencasts 
> > and so on for it (this really is a vibing community, I must say) - but 
> I'm 
> > looking for something a little out-of-the-scope of basic walkthroughs 
> and 
> > documentation... 
> > 
> > I've done some searching but I can't seem to find what I want, and what 
> I 
> > want is an online exam type app I can use to brush up my knowledge of 
> > Node.js and drill it into my head by striving to get correct answers 
> after 
> > reviewing study material. Nothing too complicated like a full on 
> training 
> > course, though. I know of the Codeschool course and various things like 
> this 
> > that just teach regular old JavaScript, so I came here hoping that 
> someone 
> > here would be more likely to know of anything like this (if it exists) 
> for 
> > Node.js. 
> > 
> > So, does such a thing exist yet? If so, where can I find it, and if not, 
> > would you experienced developers care to make one for us determined 
> newbies? 
> > :D 
> > 
> > Thanks in advance, by the way! 
> > 
> > -- 
> > 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

Re: [nodejs] ANN: Prozess, a node.js lib for the kafka distributed messaging queue

[Gregg Caines]

It's the only one AFAIK that can read / write 0.7+ messages.  Ideally
we would've forked a different lib, but didn't find them to be under
very active development, or using normal node idioms.

-- 
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] ANN: Prozess, a node.js lib for the kafka distributed messaging queue

[Arnout Kazemier]

How does your library compare to other node-kafka libraries? I know there a few.

On Monday 8 October 2012 at 18:52, Gregg Caines wrote:

> https://github.com/cainus/Prozess  /  https://npmjs.org/package/prozess
> 
> There are lots of TODOs still on this, but we've got a Kafka lib working in 
> node.js that handles Kafka 0.7 messages.  We're not using it in production 
> yet, but it's on its way and we'll be fleshing out more features as it goes.
> 
> Kafka is a distributed pub/sub style message queue released by linkedin.
> 
> This is useful if you want to do some really heavy-duty message-queuing or 
> pubsub.
> 
> Feedback or contributions are appreciated of course!
> 
> 
> -- 
> 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 
> (mailto:nodejs@googlegroups.com)
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com 
> (mailto:nodejs+unsubscr...@googlegroups.com)
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] node.js caching proxy

[Mark Hahn]

I highly recommend using nginx in front of nodejs servers.  It provides all
the caching and is a lot faster, especially for static files.

On Sun, Oct 7, 2012 at 11:06 PM, Thuan le minh wrote:

> is there solution for node.js caching proxy with bellow scenario
>
> 1-- (if webserver response data)
> client <--> node.js proxy <---> webserver
>   (cached data)
>  2-- if webserver not response data
>  client ---> node.js proxywebserver
>< cache data
>
> thank !
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

RE: [nodejs] Dynamic content scrape with Node.js

[Chad Engler]

This is probably the same person who asked this question on
StackOverflow:

 

http://stackoverflow.com/questions/12630891/scrape-data-generated-by-jav
ascript-on-server-side-from-webpages-aspx

 

Where I have already answered his question, he just didn't like it:

 

http://stackoverflow.com/questions/12630891/scrape-data-generated-by-jav
ascript-on-server-side-from-webpages-aspx#comment17032399_12630891

 

-Chad

 

From: nodejs@googlegroups.com [mailto:nodejs@googlegroups.com] On Behalf
Of Dave Kuhn
Sent: Saturday, October 06, 2012 11:46 PM
To: nodejs@googlegroups.com
Subject: Re: [nodejs] Dynamic content scrape with Node.js

 

Good suggestions so far, though i highly recommend you check out
phantomjs.org. Phantom is a headless version of WebKit which is the
rendering engine behind Chrome & Safari. It's the most comprehensive
solution to handling AJAX content when scraping in my book since it's
technically the same as interacting with a page loaded by your browser. 

 

-- 
Dave Kuhn

Sent with Sparrow  

 

On Saturday, October 6, 2012 at 3:04 PM, rektide wrote:

Only just picked it up last week, but it worked well enough--
node.io. It exposes a

jQuery-esque interface for querying scraped pages. Extremely
high level, "just works"

scraping module, in my book!

 

It also has a fairly sizable task-processing system built in,
which I have not used.

 

Good luck:

https://github.com/chriso/node.io

 

-rektide

 

On Sat, Oct 06, 2012 at 01:34:03PM -0700, Narek Musakhanyan
wrote:

Hey guys . I tried to scrape a data from a website using
PHP cURL lib but

I failed  since cURl allows you to scrape only static
content . But the

content I want to scrape changes via javascript(AJAX)
since cURL cant

hanfle that I couldnt handle scraping via cURL . So I
heard the this type

of things can be done via node . Basically I need to
make my node app

handle this js wait for some time until AJAX is done and
the pass it to

php .So is it possible to do via node.js ? I dont know
node and I have to

start from scratch so I am here you to point out the
right node framework

to use to get the result I explained . 

 

-- 

Job Board: http://jobs.nodejs.org/

Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines

You received this message because you are subscribed to the
Google

Groups "nodejs" group.

To post to this group, send email to nodejs@googlegroups.com

To unsubscribe from this group, send email to

nodejs+unsubscr...@googlegroups.com

For more options, visit this group at

http://groups.google.com/group/nodejs?hl=en?hl=en

 

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[nodejs] ANN: Prozess, a node.js lib for the kafka distributed messaging queue

[Gregg Caines]

https://github.com/cainus/Prozess  /  https://npmjs.org/package/prozess

There are lots of TODOs still on this, but we've got a Kafka lib working in 
node.js that handles Kafka 0.7 messages.  We're not using it in production 
yet, but it's on its way and we'll be fleshing out more features as it goes.

Kafka is a distributed pub/sub style message queue released by linkedin.

This is useful if you want to do some really heavy-duty message-queuing or 
pubsub.

Feedback or contributions are appreciated of course!


-- 
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] Why there's no callback for opening stream?

[Adam Crabtree]

`util.pump` is deprecated in favor of Stream.pipe.

>From the docs,
http://nodejs.org/docs/latest/api/all.html#all_util_pump_readablestream_writablestream_callback
:
util.pump(readableStream, writableStream,
[callback])#

Stability: 0 - Deprecated: Use readableStream.pipe(writableStream)


Additionally, so long as you do the pipe in the same tick as the stream
creation, you'll get the single 'error' event and thus the single call to
callback. As a general rule of thumb, when piping, don't bother with the
origin stream's events unless you have an explicit reason to do so. In this
case it doesn't seem you do, in which case you would only handle the
'error' event once on the destination stream.

Cheers,
Adam Crabtree

On Mon, Oct 8, 2012 at 9:44 AM, Adam Crabtree  wrote:

> Stream.pipe,
>
>
> http://nodejs.org/docs/latest/api/all.html#all_stream_pipe_destination_options
>
> will handle this for you in exactly the way you want:
>
>
> var copy = function(from, to, cb){
>   var stream = fs.createReadStream(from)
> .pipe(fs.createWriteStream(to))
>
>   stream.on('error', cb)
>   stream.on('end', cb)
> }
>
> Take a look at the source for Stream.pipe and you'll see what I'm talking
> about; It wraps the 'error' event callback and emits only once, then does
> its own cleanup (you'll have to call destroy yourself, although I think
> maybe pipe should do this in its cleanup...).
>
> From https://github.com/joyent/node/blob/master/lib/stream.js:
>
>
>   source.on('error', onerror);
>
>   dest.on('error', onerror);
>
>
>   // remove all the event listeners that were added.
>
>   function cleanup() {
>
> source.removeListener('data', ondata);
>
> dest.removeListener('drain', ondrain);
>
>
> source.removeListener('end', onend);
>
> source.removeListener('close', onclose);
>
>
> source.removeListener('error', onerror);
>
> dest.removeListener('error', onerror);
>
>
> source.removeListener('end', cleanup);
>
> source.removeListener('close', cleanup);
>
>
> dest.removeListener('end', cleanup);
>
> dest.removeListener('close', cleanup);
>
>   }
>
>
>
> Cheers,
> Adam Crabtree
>
> On Sun, Oct 7, 2012 at 7:57 PM, Alexey Petrushin <
> alexey.petrus...@gmail.com> wrote:
>
>> > I'm missing how this would help ...
>> With callbacks it may be something like code below:
>>
>> > so you'll still need to attach the two error handlers, and you'll still
>> need
>> > to handle the possibility of multiple notifications.
>> Not sure about it but maybe `stream.destroy()` on first event should
>> handle such cases.
>>
>> var copy = function(from, to, cb){
>>   var fromStream = null
>>   var toStream = null
>>
>>   var finish = function(err){
>> fromStream.destroy()
>> toStream.destroy()
>> cb(err)
>>   }
>>
>>   fromStream = fs.createReadStream(from, function(err){
>> if(err) return cb(err)
>> toStream = fs.createWriteStream(to, function(err){
>>   if(err) return cb(err)
>>
>>   fromStream.on('error', finish)
>>   toStream.on('error', finish)
>>   fromStream.on('end', finish)
>>   fromStream.pipe(toStream)
>> })
>>   })
>> }
>>
>> On Monday, October 8, 2012 6:41:43 AM UTC+4, Martin Cooper wrote:
>>
>>> On Sun, Oct 7, 2012 at 5:54 PM, Alexey Petrushin
>>>  wrote:
>>> > Tried to copy files using streams and pipe and got funny results.
>>> Let's
>>> > consider following code (highlighted version https://gist.github.com/*
>>> *3850106 
>>> > ):
>>> >
>>> > var copy = function(from, to, cb){
>>> >   var fromStream = fs.createReadStream(from)
>>> >   fromStream.on('error', cb)
>>> >   var toStream = fs.createWriteStream(to)
>>> >   toStream.on('error', cb)
>>> >   fromStream.on('end', cb)
>>> > }
>>> >
>>> > copy('non existing file a', 'non existing dir/file b',
>>> function(err){
>>> >   console.log(err)
>>> > })
>>> >
>>> > There are errors in both streams (non existing source file and no
>>> parent
>>> > directory for destination file) - so, both of them will emit
>>> > 'error' event, and the callback will be called twice with both errors.
>>> >
>>> > // Error will be reported twice:
>>> > //
>>> > // { [Error: ENOENT, open 'non existing file a'] errno: 34,
>>> > //code: 'ENOENT', path: 'non existing file a' }
>>> > // { [Error: ENOENT, open 'non existing dir/file b'] errno: 34,
>>> > //code: 'ENOENT', path: 'non existing dir/file b' }
>>> >
>>> > I found the solution by looking at the source of `util.pump` - it does
>>> it by
>>> > wrapping callback into function that calls callback only once - for
>>> the fist
>>> > error and ignoring others.
>>> >
>>> > But maybe it would be nice to have a callback for `createXxxStream` or
>>> > something like 'ready' or 'succe

Re: [nodejs] Why there's no callback for opening stream?

[Adam Crabtree]

Stream.pipe,

http://nodejs.org/docs/latest/api/all.html#all_stream_pipe_destination_options

will handle this for you in exactly the way you want:

var copy = function(from, to, cb){
  var stream = fs.createReadStream(from)
.pipe(fs.createWriteStream(to))

  stream.on('error', cb)
  stream.on('end', cb)
}

Take a look at the source for Stream.pipe and you'll see what I'm talking
about; It wraps the 'error' event callback and emits only once, then does
its own cleanup (you'll have to call destroy yourself, although I think
maybe pipe should do this in its cleanup...).

>From https://github.com/joyent/node/blob/master/lib/stream.js:


  source.on('error', onerror);
  dest.on('error', onerror);

  // remove all the event listeners that were added.
  function cleanup() {
source.removeListener('data', ondata);
dest.removeListener('drain', ondrain);

source.removeListener('end', onend);
source.removeListener('close', onclose);

source.removeListener('error', onerror);
dest.removeListener('error', onerror);

source.removeListener('end', cleanup);
source.removeListener('close', cleanup);

dest.removeListener('end', cleanup);
dest.removeListener('close', cleanup);
  }



Cheers,
Adam Crabtree

On Sun, Oct 7, 2012 at 7:57 PM, Alexey Petrushin  wrote:

> > I'm missing how this would help ...
> With callbacks it may be something like code below:
>
> > so you'll still need to attach the two error handlers, and you'll still
> need
> > to handle the possibility of multiple notifications.
> Not sure about it but maybe `stream.destroy()` on first event should
> handle such cases.
>
> var copy = function(from, to, cb){
>   var fromStream = null
>   var toStream = null
>
>   var finish = function(err){
> fromStream.destroy()
> toStream.destroy()
> cb(err)
>   }
>
>   fromStream = fs.createReadStream(from, function(err){
> if(err) return cb(err)
> toStream = fs.createWriteStream(to, function(err){
>   if(err) return cb(err)
>
>   fromStream.on('error', finish)
>   toStream.on('error', finish)
>   fromStream.on('end', finish)
>   fromStream.pipe(toStream)
> })
>   })
> }
>
> On Monday, October 8, 2012 6:41:43 AM UTC+4, Martin Cooper wrote:
>
>> On Sun, Oct 7, 2012 at 5:54 PM, Alexey Petrushin
>>  wrote:
>> > Tried to copy files using streams and pipe and got funny results. Let's
>> > consider following code (highlighted version https://gist.github.com/**
>> 3850106 
>> > ):
>> >
>> > var copy = function(from, to, cb){
>> >   var fromStream = fs.createReadStream(from)
>> >   fromStream.on('error', cb)
>> >   var toStream = fs.createWriteStream(to)
>> >   toStream.on('error', cb)
>> >   fromStream.on('end', cb)
>> > }
>> >
>> > copy('non existing file a', 'non existing dir/file b',
>> function(err){
>> >   console.log(err)
>> > })
>> >
>> > There are errors in both streams (non existing source file and no
>> parent
>> > directory for destination file) - so, both of them will emit
>> > 'error' event, and the callback will be called twice with both errors.
>> >
>> > // Error will be reported twice:
>> > //
>> > // { [Error: ENOENT, open 'non existing file a'] errno: 34,
>> > //code: 'ENOENT', path: 'non existing file a' }
>> > // { [Error: ENOENT, open 'non existing dir/file b'] errno: 34,
>> > //code: 'ENOENT', path: 'non existing dir/file b' }
>> >
>> > I found the solution by looking at the source of `util.pump` - it does
>> it by
>> > wrapping callback into function that calls callback only once - for the
>> fist
>> > error and ignoring others.
>> >
>> > But maybe it would be nice to have a callback for `createXxxStream` or
>> > something like 'ready' or 'success' events to know that it created
>> > successfully?
>>
>> I'm missing how this would help. If there was such an event, either
>> stream could still emit an error before it (e.g. open error) or after
>> it (e.g. read or write error), so you'll still need to attach the two
>> error handlers, and you'll still need to handle the possibility of
>> multiple notifications. What would be the benefit of having another
>> event to listen for?
>>
>> --
>> Martin Cooper
>>
>>
>> > --
>> > 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
>>
>

Re: [nodejs] Facing a problem with Node-torrent project by Max Stewart on github (https://github.com/superafroman/node-torrent)

[Isaac Schlueter]

Have you tried posting an issue on the github repo?  That'd probably
be the best way to get some help with this library.

https://github.com/superafroman/node-torrent/issues


On Sat, Oct 6, 2012 at 2:09 AM, Prachi Shah  wrote:
> Currently my team is working on a project of Peer to Peer download under
> bit-torrent protocol using node.js technology. While exploring few online
> resources, we came across a project by Max Stewart in github
> (https://github.com/superafroman/node-torrent) which seemed to be much
> useful for us. But we are also facing some problem to use it, the details of
> which I am mentioning below,
>
> CASE 1: Using a ready-made torrent file with node-torrent client  [Seeder
> already available with the tracker]
>
> Pieces validated.
>
> The download begins by connecting to tracker and then to peer.
>
> CASE 2: Using a self made torrent using clients like (utorrent/ vuze) with
> public tracker [now I am seeding using the same clients utorrent/ vuze]
>
> CASE 2.1[Test report with node-torrent]
>
> None of the pieces validated
> The download doesn't begin
>
> CASE 2.2[Test report with vuze/ utorrent]
> Download Begins & completes.
>
> CASE 3: Using a self made torrent using clients like (utorrent/ vuze) with
> personal tracker [now I am seeding using the same clients utorrent/ vuze]
>
> CASE 3.1[Test report with node-torrent]
>
> None of the pieces validated
> The download doesn't begin
>
> CASE 3.2[Test report with vuze/ utorrent]
> The download doesn't begin
>
>
> Considering CASE 2 & 3, kindly assist us in resolving this issue. Any
> specific reason for pieces not getting validated.? Any assistance/ help
> would be of great help in this hour of need.
>
> Looking forward a favorable reply at the earliest. Thank you.
>
> --
> 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: i heared a lot about nodejs but i am afraid

[waqasde]

@ Wil Moore i am well versed with traditional MVC apps in php .but from new 
skill set point of view which has demand i was interested to do a 
professional app in nodejs but the point is would i able to develop  such 
site in nodejs without facing any critical errors  as i dont know  inner 
details of nodejs does nodejs supports  all features like php/mysql like 
for example

does it supports image thumbnail generation ? 
does it support pdf,excel ,csv file handlings
does it supports encryption /decryption algos lie AES,Rjinidial or RSA.
etc. 
so main concern is does it have all the recipes required to develop a 
traditional or complex apps as i don't want to stuck at any point.

i have a  vps server with 256Ram is that enough for a site like ecommerce 
site developed with nodejs.   



On Monday, October 8, 2012 12:09:03 PM UTC+5, Wil Moore wrote:
>
> please guys advise should i invest in nodejs for such website ?
>
>
> A few questions you might start out asking yourself:
>
>
>1. How well do you know PHP/MySQL?
>2. Have you built non-trivial apps with PHP, Ruby, etc. in the past?
>3. Are you familiar with any PHP frameworks?
>4. How comfortable are you with JavaScript?
>5. Have you written any non-trivial apps with JavaScript? (i.e. 
>client-side, MVC, etc.)
>
>
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Any resources to help one brush up...?

[Tim Caswell]

The official nodejs API docs are great.  My experience with most
people learning nodejs is that they didn't know javascript as well as
they had thought.  Node makes heavy use of callbacks and closures.
This means that more often the weird aspects of js scoping creep out.

There are many nodejs specific resources out there.  There have been
some threads about this recently in this list you can search through.
I haven't heard of anything like the w3schools format (not speaking of
the content quality, just format).

On Mon, Oct 8, 2012 at 5:03 AM, Declan de Wet  wrote:
> Hi,
>
> I am relatively new to Node.js. I heard and researched about it a long time
> ago. I'm more familiar with Ruby and PHP, but Node.js has really caught my
> attention lately. I am familiar with Javascript for basic interactivity and
> the popular libraries to go with it. I've done some tutorials and so on and
> I've been competent enough to find many guides, books, blogs, screencasts
> and so on for it (this really is a vibing community, I must say) - but I'm
> looking for something a little out-of-the-scope of basic walkthroughs and
> documentation...
>
> I've done some searching but I can't seem to find what I want, and what I
> want is an online exam type app I can use to brush up my knowledge of
> Node.js and drill it into my head by striving to get correct answers after
> reviewing study material. Nothing too complicated like a full on training
> course, though. I know of the Codeschool course and various things like this
> that just teach regular old JavaScript, so I came here hoping that someone
> here would be more likely to know of anything like this (if it exists) for
> Node.js.
>
> So, does such a thing exist yet? If so, where can I find it, and if not,
> would you experienced developers care to make one for us determined newbies?
> :D
>
> Thanks in advance, by the way!
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Which database to use for a realtime chat game?

[Jake Verbaten]

Consider a combo like crdt + indexedDB + discovery-network for a
distributed game

-- 
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: Can someone help with the AES cipher

[James Coglan]

On 8 October 2012 15:48, James Coglan  wrote:

> I'm trying to implement a crypto system, and want to make sure I'm doing
> something portable, i.e. the ciphertexts I generate can be understood by
> any language with openssl functionality. I have a Ruby program that uses
> AES-256-CBC to encrypt some data, and I want to make sure I can generate
> the same ciphertext using Node.
>
> What mode of operation does crypto.createCipher('aes256') use? I assume
> it's not a bare AES function since it can encrypt arbitrary amounts of
> data, so it must be using a construction like CBC or CTR. Which one does it
> use, and can it be changed by the user?
>

To partially answer my own question: 'aes-256-cbc' is an allowed mode.
There are other modes available according to `openssl enc --help` but not
all of them work in Node.

If you want to set the IV used, you need to use crypto.createCipheriv().
For aes-256-cbc, the key must be 32 bytes, the IV 16. e.g.:

var crypto = require('crypto'),
key= '2ea5074bcc33ccbd1cd99341b837fcb4',
iv = '0123456789abcdef',
aes= crypto.createCipheriv('aes-256-cbc', key, iv);

var cipher = aes.update('The Text', 'utf8', 'hex') + aes.final('hex');
console.log(cipher);

-- 
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] Can someone help with the AES cipher

[Micheil Smith]

Hi James,

Having a quick look in the C side of things, it looks like the names come 
directly from OpenSSL, which has a function EVP_get_cipherbyname; I couldn't 
quite find where "aes256" was defined, however, I did just try doing: 

crypto.createCipher("aes-256-cbc", key)

And it appeared to work. I can see a bunch of names defined in objects.h and 
such in openssl, but don't know how those really work.

– Micheil

On 08/10/2012, at 2:48 PM, James Coglan  wrote:

> Hi all,
> 
> I'm trying to implement a crypto system, and want to make sure I'm doing 
> something portable, i.e. the ciphertexts I generate can be understood by any 
> language with openssl functionality. I have a Ruby program that uses 
> AES-256-CBC to encrypt some data, and I want to make sure I can generate the 
> same ciphertext using Node.
> 
> What mode of operation does crypto.createCipher('aes256') use? I assume it's 
> not a bare AES function since it can encrypt arbitrary amounts of data, so it 
> must be using a construction like CBC or CTR. Which one does it use, and can 
> it be changed by the user?
> 
> -- 
> James Coglan
> http://jcoglan.com
> +44 (0) 7771512510
> 
> -- 
> Job Board: http://jobs.nodejs.org/
> Posting guidelines: 
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Can someone help with the AES cipher

[Ben Noordhuis]

On Mon, Oct 8, 2012 at 3:48 PM, James Coglan  wrote:
> Hi all,
>
> I'm trying to implement a crypto system, and want to make sure I'm doing
> something portable, i.e. the ciphertexts I generate can be understood by any
> language with openssl functionality. I have a Ruby program that uses
> AES-256-CBC to encrypt some data, and I want to make sure I can generate the
> same ciphertext using Node.
>
> What mode of operation does crypto.createCipher('aes256') use? I assume it's
> not a bare AES function since it can encrypt arbitrary amounts of data, so
> it must be using a construction like CBC or CTR. Which one does it use, and
> can it be changed by the user?

It's CBC. Here is how you create an AES-256 cipher with a different mode:

  cipher = crypto.createCipher('aes-256-ecb', key); // *not* 'aes256-ecb'

-- 
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] Can someone help with the AES cipher

[James Coglan]

Hi all,

I'm trying to implement a crypto system, and want to make sure I'm doing
something portable, i.e. the ciphertexts I generate can be understood by
any language with openssl functionality. I have a Ruby program that uses
AES-256-CBC to encrypt some data, and I want to make sure I can generate
the same ciphertext using Node.

What mode of operation does crypto.createCipher('aes256') use? I assume
it's not a bare AES function since it can encrypt arbitrary amounts of
data, so it must be using a construction like CBC or CTR. Which one does it
use, and can it be changed by the user?

-- 
James Coglan
http://jcoglan.com
+44 (0) 7771512510

-- 
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] Which database to use for a realtime chat game?

[Yi Tan]

+1 to Angel Java Lopez's question.

In high traffic real-time games, data persistence no need to be in
"real-time".

The important thing I think is how to efficiently and accurately delivery
message to clients in low lag and low bandwidth consumption

Regards,

ty


2012/10/8 Angel Java Lopez 

> Hi people!
>
> My questions are basic, but I prefer to ask them, to have more context and
> to have a better understanding of your requirement:
>
> - Why you need a database? What are the use cases?
>
> I could imagine a game, based on chat messages, that don't need a
> database; it can distributed the message to the clients, and it can have an
> in-memory state of the game (one server instance per game, sticky assigned
> at begin of the game, maybe using a hash mapping from game id to server id
> to manage the game; I presume the servers can be identified... etc...
> etc...).
>
> Do you need a database to keep the CURRENT game state? To save the game
> history AT END? To keep the score of the players?
>
> Angel "Java" Lopez
> @ajlopez
>
>
> On Sat, Oct 6, 2012 at 10:44 PM, Nickname  wrote:
>
>> I'm creating a chat based game with Node.js and I would like to know
>> which database is best for the job?
>>
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>
>  --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[nodejs] Any resources to help one brush up...?

[Declan de Wet]

Hi,

I am relatively new to Node.js. I heard and researched about it a long time 
ago. I'm more familiar with Ruby and PHP, but Node.js has really caught my 
attention lately. I am familiar with Javascript for basic interactivity and 
the popular libraries to go with it. I've done some tutorials and so on and 
I've been competent enough to find many guides, books, blogs, screencasts 
and so on for it (this really is a vibing community, I must say) - but I'm 
looking for something a little out-of-the-scope of basic walkthroughs and 
documentation...

I've done some searching but I can't seem to find what I want, and what I 
want is an online exam type app I can use to brush up my knowledge of 
Node.js and drill it into my head by striving to get correct answers after 
reviewing study material. Nothing too complicated like a full on training 
course, though. I know of the Codeschool course and various things like 
this that just teach regular old JavaScript, so I came here hoping that 
someone here would be more likely to know of anything like this (if it 
exists) for Node.js.

So, does such a thing exist yet? If so, where can I find it, and if not, 
would you experienced developers care to make one for us determined 
newbies? :D

Thanks in advance, by the way!

-- 
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] Which database to use for a realtime chat game?

[JerryS]

MongoDB is my choice. And if you want to scale into the cloud check out 
firebase.

On Sunday, October 7, 2012 8:05:36 PM UTC-7, Alexey Petrushin wrote:
>
> +1 for redis Redis 
>
> CouchDB also have interesting features (pub/sub and others), but it seems 
> there are rumors about its performance not so good.
>

-- 
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] Which database to use for a realtime chat game?

[Angel Java Lopez]

Hi people!

My questions are basic, but I prefer to ask them, to have more context and
to have a better understanding of your requirement:

- Why you need a database? What are the use cases?

I could imagine a game, based on chat messages, that don't need a database;
it can distributed the message to the clients, and it can have an in-memory
state of the game (one server instance per game, sticky assigned at begin
of the game, maybe using a hash mapping from game id to server id to manage
the game; I presume the servers can be identified... etc... etc...).

Do you need a database to keep the CURRENT game state? To save the game
history AT END? To keep the score of the players?

Angel "Java" Lopez
@ajlopez

On Sat, Oct 6, 2012 at 10:44 PM, Nickname  wrote:

> I'm creating a chat based game with Node.js and I would like to know which
> database is best for the job?
>
> --
> 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: Which database to use for a realtime chat game?

[Julian Gruber]

Also checkout dominictarr's scuttlebutt or crdt for a master-less approach

On Sunday, October 7, 2012 3:44:48 AM UTC+2, Nickname wrote:
>
> I'm creating a chat based game with Node.js and I would like to know which 
> database is best for the job?
>

-- 
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: i heared a lot about nodejs but i am afraid

[Wil Moore]

>
> please guys advise should i invest in nodejs for such website ?


A few questions you might start out asking yourself:


   1. How well do you know PHP/MySQL?
   2. Have you built non-trivial apps with PHP, Ruby, etc. in the past?
   3. Are you familiar with any PHP frameworks?
   4. How comfortable are you with JavaScript?
   5. Have you written any non-trivial apps with JavaScript? (i.e. 
   client-side, MVC, etc.)
   

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