Re: [nodejs] process.env.hasOwnProperty
On 24/06/2012, at 04:09, Ben Noordhuis wrote:
On Sun, Jun 24, 2012 at 3:52 AM, Isaac Schlueter i...@izs.me wrote:
If we are going to present something that is not an Object interface,
then that's another conversation. (I'd be open to
process.getEnvKeys() - ArrayString, process.getEnv(key) - String,
and process.putEnv(key, var, clobber=true) - Boolean.)
God, that's horrible. My eyes, they're bleeding!
LOL.
@izs: please forget that!
Most people already know how to do it: ({}).hasOwnProperty.call(process.env,
property);
To those who don't: this is yet another lovely JS WTF!
--
Jorge.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] process.env.hasOwnProperty
On 24/06/2012, at 02:41, Mikeal Rogers wrote: If your goal is to be right about JavaScript I'll be the first to say you're right :) My point is that you can't teach this to everyone in the world writing JavaScript and what we need to do is just make this not an issue in node's core objects. So now we agree: don't teach anybody if you don't want to, nor put methods in the prototype when you shouldn't :-P -- Jorge. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] node-gyp build issues
Hi,
I have a native module (http://github.com/qzaidi/magickwand) that
builds just fine with node-waf. Now that node 0.8 is due to be
released, and also because node-waf isn't building correctly on
SmartOS, I am trying to switch to node-gyp. However, while it builds,
the resulting magickwand.node file is unusable. I am pretty sure this
is some issue with the binding.gyp file I am using, but not quite able
to figure it out.
When I load the module in node, I get undefined symbols error, and
that is because ldd output for node-gyp built module fails to show the
correct dependencies.
ldd magickwand.node (Built with node-waf)
linux-gate.so.1 = (0xb7877000)
libMagickWand.so.3 = /usr/lib/libMagickWand.so.3 (0xb7753000)
libstdc++.so.6 = /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb7668000)
libgcc_s.so.1 = /lib/i386-linux-gnu/libgcc_s.so.1 (0xb764a000)
libc.so.6 = /lib/i386-linux-gnu/tls/i686/nosegneg/libc.so.6
(0xb74cd000)
and others
ldd magickwand.node (Built with node-gyp) linux-gate.so.1 = (0xb7844000)
libc.so.6 = /lib/i386-linux-gnu/tls/i686/nosegneg/libc.so.6
(0xb76b7000)
/lib/ld-linux.so.2 (0xb7845000)
Here's the binding.gyp I am using.
{
targets: [
{
target_name: libmagickwand,
sources: [ src/magickwand.cpp ],
'libraries': [ '!@(Magick-config --libs)' ],
conditions: [
['OS==mac', {
'xcode_settings': {
'OTHER_CFLAGS': [
'!@(Magick-config --cflags)'
],
}
}, {
'cflags': [
'!@(Magick-config --cflags)'
]
}]
]
}
]
}
What do I fix here to get node-gyp use the correct linker flags? Any
clues will be much appreciated.
Thanks
Qasim
--
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 and developing on multiple machines
Excellent. This setup is pretty much exactly what I'm looking for. Thanks John! Also thanks to input from the rest of you guys. Cheers /Magnus Den söndagen den 24:e juni 2012 kl. 05:07:54 UTC+2 skrev John Fitzgerald: In more detail here's I do it; the application/project I'm working on is always hosted on a cloud CentOS machine(s), that have the git/svn checkout locally, and will run the app there. I have some install scripts that setup everything the way I like it. When my client is Windows, I'll use Putty and development via console Vim OR samba mount the repository directory on remote CentOS, then use Sublime Text / Vim. The latter works really well when using a local vmware image for CentOS too. When my client is Linux, I'll use ssh and console Vim OR sshfs/fuse to mount the repository directory on remote CentOS, then Sublime/Vim again. The reason it works well for me, is: a) I often have non-node stuff necessary for my work like postgresql, redis, cli apps, nginx, postfix, binary content etc.. I can't install those all from scratch on every machine I want to work from. b) I want the immediate feedback of save/refresh, so I don't like waiting for rsync or a push/pull. c) Some modules won't work cross platform and I don't care about supporting Windows as a server (I think MS support of Node is great though). d) This same setup works equally well for python/ruby/php apps as I can't use node exclusively. e) My development is under the same conditions as my production environment, so deploying is generally easy. Biggest downside is your editor may die if it doesn't cache file listings and you have a slower link/big repository. Also, I was using ssh/putty with multitail to monitor log files while I work, but I just started trying out http://logio.org/ as a replacement - fantastic so far. On Sat, Jun 23, 2012 at 3:17 AM, Ralphtheninja (Magnus Skog) lars.magnus.s...@gmail.com wrote: Ok, so you either do 1 or 2 on linux, or do 1 or 3 on windows? Or do you combine them? Den lördagen den 23:e juni 2012 kl. 00:22:53 UTC+2 skrev John Fitzgerald: I do the same as Mark, a few cloud servers that I remote into for development. I'm often jumping between a mix of several Win7/Centos/Ubuntu machines - to do remote development I use the following scenarios: 1. On either, ssh with console vim. 2. On linux, I'll do a fuse ssh filesystem mount and then use vim/sublime text. 3. On windows, I do an ssh tunnel samba mount to local drive, then vim/sublime text. Whatever I'm working on is either tunneled to a local port to access via browser, or behind http auth. On Fri, Jun 22, 2012 at 3:07 PM, Mark Hahn m...@hahnca.com wrote: For what it's worth, I have my only development environment on one server and I just remote into it from all the others. I literally see the same exact environment everywhere. On Fri, Jun 22, 2012 at 3:00 PM, Elijah Insua tmp...@gmail.com wrote: dropbox On Fri, Jun 22, 2012 at 2:52 PM, Ralphtheninja (Magnus Skog) lars.magnus.s...@gmail.com wrote: Hi, It's very common that I use several machines while developing and those machines might also be in different locations. I have two machines at home and two machines at my moms etc. There might be more machines in the future. My problem is this. No matter where I am, I just want to sit down and code and not care about what modules I have installed and where. If I'm visiting my mom some day I might find this uber cool module and install it globally with npm on that machine. When I get back home I'd like to sync my global modules on my other machines, instead of having to remember that I installed module X on machine Y. Do you have any recommendations? Thanks /Magnus -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/** node/wiki/Mailing-List-**Posting-Guidelineshttps://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.comnodejs%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/**group/nodejs?hl=en?hl=enhttp://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-Guidelineshttps://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.comnodejs%2bunsubscr...@googlegroups.com For more options, visit this group at
Re: [nodejs] Re: forever and cpu usage
On Sun, Jun 24, 2012 at 12:41 AM, Angelo Chen angelochen...@gmail.comwrote: not sure if it got restarted, but the log file name remain the same. If you are not rotating the log it should stay the same. Use pshttp://unixhelp.ed.ac.uk/CGI/man-cgi?psto find out the process PID and check if is the same some later. Radhamés Brito *Techpark http://www.techpark.com.do/* 829 994 1212 Email:rbr...@techpark.com.do rbr...@techpark.com.do -- 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-gyp build issues
Hi,
I just send you a pull request solving the linker errors (basically a
change to use MagickWand-config).
One small issue remains, and that is the resolving of the path to the
magickwand.node which now resides in ./build/Release/
magickwand.node. I believe there might be a common practice for
dealing with this, but I don't know it exactly.
Best regards,
Jeroen Janssen
On Jun 24, 1:37 pm, Qasim Zaidi qa...@zaidi.me wrote:
Hi,
I have a native module (http://github.com/qzaidi/magickwand) that
builds just fine with node-waf. Now that node 0.8 is due to be
released, and also because node-waf isn't building correctly on
SmartOS, I am trying to switch to node-gyp. However, while it builds,
the resulting magickwand.node file is unusable. I am pretty sure this
is some issue with the binding.gyp file I am using, but not quite able
to figure it out.
When I load the module in node, I get undefined symbols error, and
that is because ldd output for node-gyp built module fails to show the
correct dependencies.
ldd magickwand.node (Built with node-waf)
linux-gate.so.1 = (0xb7877000)
libMagickWand.so.3 = /usr/lib/libMagickWand.so.3 (0xb7753000)
libstdc++.so.6 = /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb7668000)
libgcc_s.so.1 = /lib/i386-linux-gnu/libgcc_s.so.1 (0xb764a000)
libc.so.6 = /lib/i386-linux-gnu/tls/i686/nosegneg/libc.so.6
(0xb74cd000)
and others
ldd magickwand.node (Built with node-gyp) linux-gate.so.1 =
(0xb7844000)
libc.so.6 = /lib/i386-linux-gnu/tls/i686/nosegneg/libc.so.6
(0xb76b7000)
/lib/ld-linux.so.2 (0xb7845000)
Here's the binding.gyp I am using.
{
targets: [
{
target_name: libmagickwand,
sources: [ src/magickwand.cpp ],
'libraries': [ '!@(Magick-config --libs)' ],
conditions: [
['OS==mac', {
'xcode_settings': {
'OTHER_CFLAGS': [
'!@(Magick-config --cflags)'
],
}
}, {
'cflags': [
'!@(Magick-config --cflags)'
]
}]
]
}
]
}
What do I fix here to get node-gyp use the correct linker flags? Any
clues will be much appreciated.
Thanks
Qasim
--
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-gyp build issues
Thanks Jeroen for resolving this quickly. I was wrongly suspecting
node-gyp, while I was supposed to use Wand-config --libs (instead of
Magick-config or MagickWand-config).
Regards
Qasim
On Sun, Jun 24, 2012 at 5:07 PM, Qasim Zaidi qa...@zaidi.me wrote:
Hi,
I have a native module (http://github.com/qzaidi/magickwand) that
builds just fine with node-waf. Now that node 0.8 is due to be
released, and also because node-waf isn't building correctly on
SmartOS, I am trying to switch to node-gyp. However, while it builds,
the resulting magickwand.node file is unusable. I am pretty sure this
is some issue with the binding.gyp file I am using, but not quite able
to figure it out.
When I load the module in node, I get undefined symbols error, and
that is because ldd output for node-gyp built module fails to show the
correct dependencies.
ldd magickwand.node (Built with node-waf)
linux-gate.so.1 = (0xb7877000)
libMagickWand.so.3 = /usr/lib/libMagickWand.so.3 (0xb7753000)
libstdc++.so.6 = /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb7668000)
libgcc_s.so.1 = /lib/i386-linux-gnu/libgcc_s.so.1 (0xb764a000)
libc.so.6 = /lib/i386-linux-gnu/tls/i686/nosegneg/libc.so.6
(0xb74cd000)
and others
ldd magickwand.node (Built with node-gyp) linux-gate.so.1 =
(0xb7844000)
libc.so.6 = /lib/i386-linux-gnu/tls/i686/nosegneg/libc.so.6
(0xb76b7000)
/lib/ld-linux.so.2 (0xb7845000)
Here's the binding.gyp I am using.
{
targets: [
{
target_name: libmagickwand,
sources: [ src/magickwand.cpp ],
'libraries': [ '!@(Magick-config --libs)' ],
conditions: [
['OS==mac', {
'xcode_settings': {
'OTHER_CFLAGS': [
'!@(Magick-config --cflags)'
],
}
}, {
'cflags': [
'!@(Magick-config --cflags)'
]
}]
]
}
]
}
What do I fix here to get node-gyp use the correct linker flags? Any
clues will be much appreciated.
Thanks
Qasim
--
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: Should i use node?
I personally think the Node community is one of the best I've experienced for cultural adovcacy: it's just not necessarily evident as a newbie. The community is diverse and Node itself is young. It also intentionally has a very a small core, which leaves a lot open for interpretation. Node does embrace the unix philosophy by it's choice of APIs, which is a set of guidelines in itself. Beyond that, the Node community principles, (which I now can't find a link to), and frequent advocacy from big contributors on their blogs do a great job of extolling the culture (such as Joyent, the Browserling guys and Nodejitsu - to mention a few). Event driven platforms and servers have been successul in other platforms, but the platforms themselves do not explicitly encourage that style of programming and the choice of JavaScript for nodejs (and it's lack of encumberment to a pre-existing set of synchronous libraries) has forced a complete re-imagination of many of the basic utilities we come to expect from our development frameworks. Raoul On Sunday, June 24, 2012 4:22:15 AM UTC+1, Radhames Brito wrote: On Sat, Jun 23, 2012 at 8:03 PM, Mikeal Rogers mikeal.rog...@gmail.comwrote: Couldn't disagree with you more. Open environments thrive on small discreet and federated components and not on central authority. It's closed systems that require more frameworks and widgets and big SDKs in order to survive and compete against other closed systems. The internet is open, but there are open standards which allow things to work together and help improve overal quality. Competition is excellent when you approach to a problem with a different solution or with higher quality, but if you are doing the exact thing as someone else why not just join the effort? I dont endorse closed systems at all, i hate them, I'm not talking about imposing design restriction but quality restrictions, for example requiring certain level of documentation or testing before making a library available via npm, the authors could still host the library at places like github, and npm could publish a description of the project where the author could explain why that project is different and you could try it or contribute. -- 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: Should i use node?
It is very possible that Node never will mature. Having a zillion choices may be here to stay. Hopefully it will get easier to find the ones you need. Of course the quality of the best modules will improve over time. And some will dominate when they hit the sweet spot of what most developers want. There will always be people that bitch about the fragmentation and want to be told what to use. -- 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] Should i use node?
I wrote something about this few weeks ago http://joseoncode.com/2012/05/31/node-dot-js-and-the-beauty-of-working-on-a-platform-that-embrace-opensource/ 2012/6/23, Radhames Brito rbri...@techpark.com.do: On Sat, Jun 23, 2012 at 1:12 PM, Mark Hahn m...@hahnca.com wrote: I dont see node.js growing much You must be blind. Node is exploding with no end in site. Yes I agree Node is exploding, but there needs to be standards, I know everyone is running to it but efforts should be unified. -- Radhamés Brito *Techpark http://www.techpark.com.do/* 829 994 1212 Email:rbr...@techpark.com.do rbr...@techpark.com.do -- 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 -- Enviado desde mi dispositivo móvil -- 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] NodObjC and iOS or Mac App Store distribution
Out of curiosity, when running a UIWebView on iOS, is it running full WebKit with JIT enabled, etc, or is there something dumbed down about it? Ted On Jun 23, 2012, at 10:35 PM, Tim Caswell wrote: The difference between V8 and most other scripting languages is that V8 does not have an interpreter. It is JIT only. That means it works by 1. writing machine code to memory, 2. executing the code. JIT is very fast and most of the modern scripting engines do it (V8, JSC, SpiderMonkey, LuaJit, ...). All of these engines (except for V8) also have an interpreter mode where the machine code is fixed at compile time and it walks over your script code interpreting it. State is kept using various data structures like one big state machine simulating a CPU that knows how to run JavaScript natively. This is slower, but doesn't require using the same region of memory as both writable and executable. On Sat, Jun 23, 2012 at 9:09 PM, Ryan Schmidt google-2...@ryandesign.com wrote: On Jun 23, 2012, at 17:13, Jorge wrote: On 23/06/2012, at 19:03, Ryan Schmidt wrote: On Jun 23, 2012, at 02:37, Jorge wrote: I don't know the answer to your question, but my guess is that many of the things that node does won't run/can't be done in a sandbox. I believe the experiments with node on iOS so far have always been in jailbroken devices. But I may be wrong. Certainly, being able to run in a sandbox will be necessary, since Apple will not approve apps anymore that don't. I haven't tried it yet, but why do you think node won't run in a sandbox? iOS wont't let user code jump into a block of writable (from your app's point of view) memory -for security reasons- That seems reasonable. and it seems that v8's JIT compiler requires that: http://code.google.com/p/v8/issues/detail?id=1312 Thank you for the link, but I think the discussion goes over my head. It talks about mapping executable memory pages, which are concepts I'm pleased as a JavaScript developer not to have to know anything about. On the surface, I don't understand why the block of memory containing my program code should need to be writable. I'm not wanting to change my program code as it's running. I'm just wanting to run it. Or are you saying that by virtue of being an interpreted language it must be writable? Also, that issue was started over a year ago, and has not been touched in six months. There is a patch attached to implement some improvement, and there's no indication whether it was committed. Maybe something has already changed? Or if not, maybe it's time to remind the v8 devs about it? The Nitro JIT in JavaScriptCore in mobile Safari requires that too, but the security measure has been conveniently lifted for that particular app :-P The second article I linked to in my original post mentioned Apple relaxing its restrictions on interpreted languages, in recognition of the fact that many games use scripting languages like lua. Does lua also run code in writable memory? If so, how are they bypassing Apple's requirement? And if not, is there something we can learn from how lua is doing that that could be applied to improve node / v8? Also it seems that quite a bunch of the usual posix APIs simply aren't there... until you jailbreak it and install the things yourself. I'm not interested in jailbreaking devices; I'm interesting in creating apps users on everyday iOS and OS X devices can install. I'm not familiar with how sandboxing works in OS X or iOS. I haven't found out yet how I could build a sample sandboxed application to play around with it either. What specific POSIX APIs that node needs will be unavailable? Apple wants you to develop your apps using their cocoa APIs not anything else. Soon we are going to suffer similar constraints (sandboxes etc) in Mountain Lion too. And finally a day will come when nothing but Apple's approved apps (that is: from the mac app store) will run in a Mac... for your security. I can't speculate on what direction Apple might go with future versions of OS X, but concerns like these are precisely why I started this thread. In light of the current and potential future security restrictions, how can we use node and NodObjC to develop an OS X or iOS app? It's no use to spend time developing an app if it can't be distributed to end users. On Jun 23, 2012, at 19:43, Tim Caswell wrote: I don't think there is a way to get nodejs using V8 running in an app-store friendly format. Again, why? Is it the same concerns Jorge expressed above? But I would love to get libuv and some scripting engine running there. I may try my luvit project first (luajit + libuv) or luvmonkey (spidermonkey + libuv). Another combination would be JSC + libuv. I'm interested in getting node and NodObjC usable for making OS X and iOS apps. The promise of using
Re: [nodejs] Re: Should i use node?
In my mind, maturing doesn't mean all the choices go away. It just means there are some obvious choices that most people agree are the way to go. This takes time and work. And it means those obvious choices are the first thing newbs run into when they are considering solutions. This can be helped by better organization around community support of recommended modules. Hopefully this story gets better in the near future. :Marco On Sun, Jun 24, 2012 at 10:40 AM, Mark Hahn m...@hahnca.com wrote: It is very possible that Node never will mature. Having a zillion choices may be here to stay. Hopefully it will get easier to find the ones you need. Of course the quality of the best modules will improve over time. And some will dominate when they hit the sweet spot of what most developers want. There will always be people that bitch about the fragmentation and want to be told what to use. -- 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 -- Marco Rogers marco.rog...@gmail.com | https://twitter.com/polotek Life is ten percent what happens to you and ninety percent how you respond to it. - Lou Holtz -- 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] Should i use node?
This can be helped by better organization around community support of recommended modules. Hopefully this story gets better in the near future. Recommended by who? Based on what? I had the chance to assist to a talk that Isaac gave on JsConfAr, about this.. I cant find his talk online right now but this post looks similar: http://blog.izs.me/post/23048895912/tacoconf-anarchism -- 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] Should i use node?
I wont use something because the upvoters. I have 2 months working in node
for serious when i need something i search with npm (slow), or google -
github. Then i look at the github page to see if it does what i want, and
if is not clear i look at the examples folder then at the test folder. If
it does what i want i will use. If it doesnt and i think it should I can
fork it and enhance, or look for some other module.
El domingo, 24 de junio de 2012, Mark Hahn escribió:
Recommended by who? Based on what?
How about one vote per github account?
--
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.comjavascript:_e({}, 'cvml', 'nodejs@googlegroups.com');
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com javascript:_e({}, 'cvml',
'nodejs%2bunsubscr...@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] Should i use node?
On Sun, Jun 24, 2012 at 5:04 PM, José F. Romaniello jfromanie...@gmail.comwrote: I wont use something because the upvoters. I have 2 months working in node for serious when i need something i search with npm (slow), or google - github. Then i look at the github page to see if it does what i want, and if is not clear i look at the examples folder then at the test folder. If it does what i want i will use. If it doesnt and i think it should I can fork it and enhance, or look for some other module. Well your results could be documented (all of our results) in a central place, along the voting Mark mentioned. Elements like recent commits, forks, contributors and download count would be very helpful too, also documentation and testing rating and if the project has a web page or not. -- Radhamés Brito *Techpark http://www.techpark.com.do/* 829 994 1212 Email:rbr...@techpark.com.do rbr...@techpark.com.do -- 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] Should i use node?
Well your results could be documented (all of our results) in a central place It would be just one more piece of data to use when evaluating a module. You could make of it whatever you want. Of course it would cause competition and maybe hurt feelings, but that is life. -- 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] Should i use node?
@izs talk http://blip.tv/jsconfar/isaac_z_schlueter-6193181 More JsConfAr videos http://blip.tv/jsconfar On Sun, Jun 24, 2012 at 5:13 PM, José F. Romaniello jfromanie...@gmail.comwrote: This can be helped by better organization around community support of recommended modules. Hopefully this story gets better in the near future. Recommended by who? Based on what? I had the chance to assist to a talk that Isaac gave on JsConfAr, about this.. I cant find his talk online right now but this post looks similar: http://blog.izs.me/post/23048895912/tacoconf-anarchism -- 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] Should i use node?
Recommended by a majority of your community peers that you respect. And yes that is a vague and fuzzy definition. It should be because there's no prescription here. We're just talking about a rough priority list that tries to reflect the prevailing trends. Or at least that's what I've been pushing. It may end up looking differently. Sent from my iPhone On Jun 24, 2012, at 1:15 PM, Mark Hahn m...@hahnca.com wrote: Recommended by who? Based on what? How about one vote per github account? -- 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] /dev/stdin in node v0.7
I'm having problems with /dev/stdin in node 0.7 - I can't open it as a
file and I can't use it as an input source for spawned childs. Anyone
knows about this, is it a bug or intended behavior?
For example the following is fine with node v0.6 but fails in node
v0.7:
fs.readFile(/dev/stdin, console.log);
The result being:
1. If run as standalone program, after Ctrl+D:
{ [Error: UNKNOWN, read] errno: -1, code: 'UNKNOWN' }
or
2. If spawned with child_process.spawn:
{ [Error: UNKNOWN, open '/dev/stdin'] errno: -1, code: 'UNKNOWN',
path: '/dev/stdin' }
I'm trying to use /dev/stdin as an input file with openssl certificate
generation - instead of writing private keys etc. to the disk, I
forward these by /dev/stdin, for example to create a CSR:
openssl req -new -sha1 -key /dev/stdin -subj /CN=localhost
Works fine with v0.6 but fails in v0.7
--
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] /dev/stdin in node v0.7
On Sun, Jun 24, 2012 at 10:14 PM, andris andris.rein...@gmail.com wrote:
I'm having problems with /dev/stdin in node 0.7 - I can't open it as a
file and I can't use it as an input source for spawned childs. Anyone
knows about this, is it a bug or intended behavior?
For example the following is fine with node v0.6 but fails in node
v0.7:
fs.readFile(/dev/stdin, console.log);
The result being:
1. If run as standalone program, after Ctrl+D:
{ [Error: UNKNOWN, read] errno: -1, code: 'UNKNOWN' }
or
2. If spawned with child_process.spawn:
{ [Error: UNKNOWN, open '/dev/stdin'] errno: -1, code: 'UNKNOWN',
path: '/dev/stdin' }
I'm trying to use /dev/stdin as an input file with openssl certificate
generation - instead of writing private keys etc. to the disk, I
forward these by /dev/stdin, for example to create a CSR:
openssl req -new -sha1 -key /dev/stdin -subj /CN=localhost
Works fine with v0.6 but fails in v0.7
https://github.com/joyent/node/commit/1d3d02c - already fixed
--
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] NodObjC and iOS or Mac App Store distribution
Wow interesting thread you guys! Unfortunately all of the experiments I've done with node and iOS has been with jailbroken devices. Indeed, V8 is the major problem with this, and it seems like there's no way around it, for the reasons Tim already explained. From what I understand, libuv works on iOS, cause I've seen pull requests for libuv in the past that addressed iOS problems. So to answer the original question: No, there haven't been any NodObjC apps accepted into the App Store. You could probably do Cydia if you wanted to go down that road, but most people don't. Feel free to poke those guys in the V8 issue thread, but I don't expect much there, when Apple wouldn't let it be put to use anyways. On Sun, Jun 24, 2012 at 10:48 AM, Ted Young t...@radicaldesigns.org wrote: Out of curiosity, when running a UIWebView on iOS, is it running full WebKit with JIT enabled, etc, or is there something dumbed down about it? Ted On Jun 23, 2012, at 10:35 PM, Tim Caswell wrote: The difference between V8 and most other scripting languages is that V8 does not have an interpreter. It is JIT only. That means it works by 1. writing machine code to memory, 2. executing the code. JIT is very fast and most of the modern scripting engines do it (V8, JSC, SpiderMonkey, LuaJit, ...). All of these engines (except for V8) also have an interpreter mode where the machine code is fixed at compile time and it walks over your script code interpreting it. State is kept using various data structures like one big state machine simulating a CPU that knows how to run JavaScript natively. This is slower, but doesn't require using the same region of memory as both writable and executable. On Sat, Jun 23, 2012 at 9:09 PM, Ryan Schmidt google-2...@ryandesign.comwrote: On Jun 23, 2012, at 17:13, Jorge wrote: On 23/06/2012, at 19:03, Ryan Schmidt wrote: On Jun 23, 2012, at 02:37, Jorge wrote: I don't know the answer to your question, but my guess is that many of the things that node does won't run/can't be done in a sandbox. I believe the experiments with node on iOS so far have always been in jailbroken devices. But I may be wrong. Certainly, being able to run in a sandbox will be necessary, since Apple will not approve apps anymore that don't. I haven't tried it yet, but why do you think node won't run in a sandbox? iOS wont't let user code jump into a block of writable (from your app's point of view) memory -for security reasons- That seems reasonable. and it seems that v8's JIT compiler requires that: http://code.google.com/p/v8/issues/detail?id=1312 Thank you for the link, but I think the discussion goes over my head. It talks about mapping executable memory pages, which are concepts I'm pleased as a JavaScript developer not to have to know anything about. On the surface, I don't understand why the block of memory containing my program code should need to be writable. I'm not wanting to change my program code as it's running. I'm just wanting to run it. Or are you saying that by virtue of being an interpreted language it must be writable? Also, that issue was started over a year ago, and has not been touched in six months. There is a patch attached to implement some improvement, and there's no indication whether it was committed. Maybe something has already changed? Or if not, maybe it's time to remind the v8 devs about it? The Nitro JIT in JavaScriptCore in mobile Safari requires that too, but the security measure has been conveniently lifted for that particular app :-P The second article I linked to in my original post mentioned Apple relaxing its restrictions on interpreted languages, in recognition of the fact that many games use scripting languages like lua. Does lua also run code in writable memory? If so, how are they bypassing Apple's requirement? And if not, is there something we can learn from how lua is doing that that could be applied to improve node / v8? Also it seems that quite a bunch of the usual posix APIs simply aren't there... until you jailbreak it and install the things yourself. I'm not interested in jailbreaking devices; I'm interesting in creating apps users on everyday iOS and OS X devices can install. I'm not familiar with how sandboxing works in OS X or iOS. I haven't found out yet how I could build a sample sandboxed application to play around with it either. What specific POSIX APIs that node needs will be unavailable? Apple wants you to develop your apps using their cocoa APIs not anything else. Soon we are going to suffer similar constraints (sandboxes etc) in Mountain Lion too. And finally a day will come when nothing but Apple's approved apps (that is: from the mac app store) will run in a Mac... for your security. I can't speculate on what direction Apple might go with future versions of OS X, but concerns like these are precisely why I started this thread. In light of the current and
Re: [nodejs] process.env.hasOwnProperty
On Sunday, June 24, 2012 3:17:23 AM UTC+2, Mikeal Rogers wrote: You and Bert are technically correct but what you're correct about doesn't matter. Should node cause an exception on accessing this prototype which many people expect to be there? The answer is obviously no only because it's much easier to make it not a problem that anyone ever sees than it is to explain this to everyone who gets this error. If you reply with another email explaining to me how JavaScript works I'm seriously going to flip out. -Mikeal Let me elaborate on my reservations a little more: * Calling .hasOwnProperty() (or any other prototype method) on an object that's used as a hash table and where the keys are defined outside of the program's control is an anti pattern. People shouldn't do it. The question is really whether node wants to get in the way of the user when he tries to do it anyway. That's debatable - I could live with fixing the prototype. But really, if I were to redo node, I would make all of these guys - process.env, http headers, querystring args - prototype-less object. * process.env does not in any way behave like a normal object. For example all values are coerced to string, and setting a value to (empty string) might actually delete the key. Also, on Windows, keys are case insensitive; changing that is going to break much more than it fixes. There's probably more weirdness that I am not even aware of, which is all caused by the fact that the environment *is* not a JS object. The proper way to do it would probably be to remove `process.env` and expose the functions `process.setenv()` and `process.getenv()`, but the way it works now is too damn convenient to remove. People should just accept the fact that process.env behaves a little different sometimes, and if you really need JS object semantics, make a copy of it. - Bert -- 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] ReferenceError: window is not defined
Hello, I'm a complete node.js newbie and trying to run a program, but get this error: #node ./app.js /home/afarber/src/Pocket-Island/build/app.js:1 window.wooga.cas ^ ReferenceError: window is not defined at Object.anonymous (/home/afarber/src/Pocket-Island/build/app.js:1:63) at Module._compile (module.js:446:26) at Object..js (module.js:464:10) at Module.load (module.js:353:31) at Function._load (module.js:311:12) at Array.0 (module.js:484:10) at EventEmitter._tickCallback (node.js:190:38) I'm probably missing something obvious, does anybody please have a hint for me? I've provided more details at http://stackoverflow.com/questions/11181562/referenceerror-window-is-not-defined Thank you Alex -- 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] ReferenceError: window is not defined
On Mon, Jun 25, 2012 at 12:12 AM, Alexander Farber alexander.far...@gmail.com wrote: Hello, I'm a complete node.js newbie and trying to run a program, but get this error: #node ./app.js /home/afarber/src/Pocket-Island/build/app.js:1 window.wooga.cas ^ ReferenceError: window is not defined at Object.anonymous (/home/afarber/src/Pocket-Island/build/app.js:1:63) at Module._compile (module.js:446:26) at Object..js (module.js:464:10) at Module.load (module.js:353:31) at Function._load (module.js:311:12) at Array.0 (module.js:484:10) at EventEmitter._tickCallback (node.js:190:38) I'm probably missing something obvious, does anybody please have a hint for me? I've provided more details at http://stackoverflow.com/questions/11181562/referenceerror-window-is-not-defined That's because there is no window object. You're not in the browser anymore, Toto. Even if there were a window object, your example would need to be rewritten as `window.wooga window.wooga.cas` to guard against the possibility that the windows object doesn't have a .wooga property. Now, I don't want to sound like an ass but the above is Javascript 101 and the mailing list is not really the place for that. -- 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] planetnodejs down?
http://planetnodejs.com/ seems to have been down for a bit. Not sure who was running it, but I was enjoying it. Ted -- 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-gyp build issues
On 24 June 2012 20:49, Jeroen Janssen jeroen.jans...@gmail.com wrote:
Hi,
I just send you a pull request solving the linker errors (basically a
change to use MagickWand-config).
One small issue remains, and that is the resolving of the path to the
magickwand.node which now resides in ./build/Release/
magickwand.node. I believe there might be a common practice for
dealing with this, but I don't know it exactly.
Best regards,
Jeroen Janssen
On Jun 24, 1:37 pm, Qasim Zaidi qa...@zaidi.me wrote:
Hi,
I have a native module (http://github.com/qzaidi/magickwand) that
builds just fine with node-waf. Now that node 0.8 is due to be
released, and also because node-waf isn't building correctly on
SmartOS, I am trying to switch to node-gyp. However, while it builds,
the resulting magickwand.node file is unusable. I am pretty sure this
is some issue with the binding.gyp file I am using, but not quite able
to figure it out.
When I load the module in node, I get undefined symbols error, and
that is because ldd output for node-gyp built module fails to show the
correct dependencies.
ldd magickwand.node (Built with node-waf)
linux-gate.so.1 = (0xb7877000)
libMagickWand.so.3 = /usr/lib/libMagickWand.so.3 (0xb7753000)
libstdc++.so.6 = /usr/lib/i386-linux-gnu/libstdc++.so.6
(0xb7668000)
libgcc_s.so.1 = /lib/i386-linux-gnu/libgcc_s.so.1 (0xb764a000)
libc.so.6 = /lib/i386-linux-gnu/tls/i686/nosegneg/libc.so.6
(0xb74cd000)
and others
ldd magickwand.node (Built with node-gyp) linux-gate.so.1 =
(0xb7844000)
libc.so.6 = /lib/i386-linux-gnu/tls/i686/nosegneg/libc.so.6
(0xb76b7000)
/lib/ld-linux.so.2 (0xb7845000)
Here's the binding.gyp I am using.
{
targets: [
{
target_name: libmagickwand,
sources: [ src/magickwand.cpp ],
'libraries': [ '!@(Magick-config --libs)' ],
conditions: [
['OS==mac', {
'xcode_settings': {
'OTHER_CFLAGS': [
'!@(Magick-config --cflags)'
],
}
}, {
'cflags': [
'!@(Magick-config --cflags)'
]
}]
]
}
]
}
What do I fix here to get node-gyp use the correct linker flags? Any
clues will be much appreciated.
Thanks
Qasim
--
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
hi, jeroen:
I am the author of geoip module, and I am too stupid to figure the gyp out.
Could help me with the same thing you do for zaidi?
--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] planetnodejs down?
appears to be up now. it's my app, it runs on nodejitsu. On Jun 24, 2012, at June 24, 20127:18 PM, Ted Young wrote: http://planetnodejs.com/ seems to have been down for a bit. Not sure who was running it, but I was enjoying it. Ted -- 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: /dev/stdin in node v0.7
wow, thanks, it's a relief!
On Jun 25, 12:53 am, Ben Noordhuis i...@bnoordhuis.nl wrote:
On Sun, Jun 24, 2012 at 10:14 PM, andris andris.rein...@gmail.com wrote:
I'm having problems with /dev/stdin in node 0.7 - I can't open it as a
file and I can't use it as an input source for spawned childs. Anyone
knows about this, is it a bug or intended behavior?
For example the following is fine with node v0.6 but fails in node
v0.7:
fs.readFile(/dev/stdin, console.log);
The result being:
1. If run as standalone program, after Ctrl+D:
{ [Error: UNKNOWN, read] errno: -1, code: 'UNKNOWN' }
or
2. If spawned with child_process.spawn:
{ [Error: UNKNOWN, open '/dev/stdin'] errno: -1, code: 'UNKNOWN',
path: '/dev/stdin' }
I'm trying to use /dev/stdin as an input file with openssl certificate
generation - instead of writing private keys etc. to the disk, I
forward these by /dev/stdin, for example to create a CSR:
openssl req -new -sha1 -key /dev/stdin -subj /CN=localhost
Works fine with v0.6 but fails in v0.7
https://github.com/joyent/node/commit/1d3d02c- already fixed
--
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: Sticky sessions using the new cluster API?
Does the node clustering module provide hooks to achieve this (sticky sessions) or will I have to re-implement a bunch of things from scratch or copy-paste code? On Friday, June 22, 2012 8:08:30 AM UTC-7, Bradley Meck wrote: There are a couple ways to do this. 1. Use a session store that is transactional and shared (redis etc.) and store where a session should be forwarded to. 2. Use a hashing method that will consistently point to the same location/worker for the same session (session could be ip/user/etc.), if the wrong worker gets the connection, forward it to the original worker. 3. Use a master/slave setup using fork rather than cluster. Master gets all the connections incoming on a machine and processes them before forwarding them to the proper worker. Each method has its advantages. The alternative to this is to change an API to be state-less, which can be hard if connections are using multiple protocols. On Monday, June 18, 2012 11:34:42 PM UTC-5, dhruvbird wrote: Is it possible to have sticky sessions using the new cluster API? Some custom logic such as a cookie based solution? Something similar to nginx sticky module? -- 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
