it depends on how your terminal is configured. on mac osX for example you
can choose wich character encoding should be used.
Am Freitag, 25. Oktober 2013 04:02:44 UTC+2 schrieb yougen zhuang:
I write some Chinese character into the stdin, isn't it valid utf8?
2013/10/24 mscdex
Hey Bruno, checkout out some of the systems that we have
herehttps://github.com/opsmezzo/composer-systems.
This might be closer to what you are looking for. We use the cli tool
quillhttps://github.com/opsmezzo/quill (with
composer https://github.com/opsmezzo/composer as the api endpoint) to
Checkout nodemiral. I have not yet released yet.
https://github.com/arunoda/nodemiral
Build for a cloud automation service. Works pretty well.
On Friday, October 25, 2013, Jarrett Cruger wrote:
Hey Bruno, checkout out some of the systems that we have
This may be of your interest, IANA approved the mime type of a json api:
application/vnd.api+jsonhttp://www.iana.org/assignments/media-types/application/vnd.api+json
http://jsonapi.org/
*application/json is still valid, but if your server has a json api that
can be consumed by clients I
Anyone see what's slowing down this performance test?
http://pastebin.com/Wy32u2T8
--
--
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
Also keep in mind that the native string type in JavaScript is UCS-16 which
means that any code points higher than 16 bits have to be encoded using
surrogate pairs. (Note that the native encoding is quite different from the
UTF-8 encoding commonly used when serializing strings to binary data)
A
I think the fact that the right hand side of a dep specification can
be either a repo (user/repo in github, url), or a version spec
satisfied from a (single) registry, but not both, is a problem. I'd
particularly like a tool that allows git repos to be used as package
sources, with some convention
Hi Bruno,
Simalar to the Chef resource lib, I build
[mecano](https://github.com/wdavidw/node-mecano).
I use it dayly to deploy hadoop cluster.
d.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received
Somebody knows solution?
пятница, 25 октября 2013 г., 1:41:47 UTC+3 пользователь Олег П написал:
Hello!
I use Node.js with Redis.
I want read channel Redis and send messages to client.
This is fragment SERVER code:
const *redis* = require('redis');
const *client* =
I've been using redis pub/sub fine.
Go through the tutorials again. PS: const should not be used like that, use
var.
Publish / Subscribe
Here is a simple example of the API for publish / subscribe. This program
opens two client connections, subscribes to a channel on one of them, and
publishes
Const is the new var in the ES6 world, you should use it everywhere except
for mutable references.
On Oct 25, 2013 9:31 PM, Bruno Fuster brunofus...@gmail.com wrote:
I've been using redis pub/sub fine.
Go through the tutorials again. PS: const should not be used like that,
use var.
Publish /
On Fri, Oct 25, 2013 at 5:34 PM, Brian Di Palma off...@gmail.com wrote:
Const is the new var in the ES6 world, you should use it everywhere except
for mutable references.
What about block scoped primitive values? const is not the new var—that
implies s/var/const/, which is not true.
Rick
--
On Friday, October 25, 2013 12:38:59 PM UTC-4, Sam Roberts wrote:
I think the fact that the right hand side of a dep specification can
be either a repo (user/repo in github, url), or a version spec
satisfied from a (single) registry, but not both, is a problem.
What's wrong with specifying
On Friday, October 25, 2013 4:18:14 PM UTC-7, mscdex wrote:
On Friday, October 25, 2013 12:38:59 PM UTC-4, Sam Roberts wrote:
I think the fact that the right hand side of a dep specification can
be either a repo (user/repo in github, url), or a version spec
satisfied from a (single)
In node, the higher level apis are created by the users (by combining
existing modules into a larger project).
And if anyone ever say that async io has to go, then I'm going to shoot
that person personally!
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
Hello there!
I have released the new version of the siteboot node web development
framework to the public domain on github and on npm. New version 0.2.0-beta
is OUT. Many great improvements - I can't even start listing all the extra
features since the last version because they are just
On Thursday, October 24, 2013 10:08:23 PM UTC-7, Alex Kocharin wrote:
25.10.2013, 07:48, Stuart P. Bentley stu...@testtrack4.comjavascript:
:
The way I see it, the dependencies hash in package.json right now is
pulling double-duty. In some cases (where the value of a dependencies
On Friday, October 25, 2013 9:38:59 AM UTC-7, Sam Roberts wrote:
I think the fact that the right hand side of a dep specification can
be either a repo (user/repo in github, url), or a version spec
satisfied from a (single) registry, but not both, is a problem. I'd
particularly like a
On Thu, Oct 24, 2013 at 8:48 PM, Stuart P. Bentley
stu...@testtrack4.com wrote:
The way I see it, the dependencies hash in package.json right now is
pulling double-duty. In some cases (where the value of a dependencies field
is a semver), it's there to describe generally what module versions
On Saturday, October 26, 2013 4:26:43 AM UTC+4, Stuart P. Bentley wrote:
On Thursday, October 24, 2013 10:08:23 PM UTC-7, Alex Kocharin wrote:
This mixed-purpose approach has a few shortcomings: for one, packages
outside the canonical registry can't specify version ranges.
Why? I
shrinkwrap doesn't really work well in practice, it almost never makes
sense to not pin versions directly. Even bug fixes introduce
non-deterministic behaviour in an application so if you're not uber
rigorous at the QA level in stage it's pretty likely to screw you over
On Thursday, 24 October
21 matches
Mail list logo
