[nodejs] Re: Wanted: federated-event/message-emitting platform?
looks like a peer-to-peer network to me. here are some libs:
https://github.com/Raynos/peer-connection-network
or you can develop it as a grid (read p2p network with predefined peers)
using https://github.com/substack/dnode
Am Montag, 18. Februar 2013 18:33:47 UTC+1 schrieb MikeB_2012:
Hi all. I'm an experienced data mining/machine learning algorithm
developer redirecting from programming/prototyping in Matlab (past decade)
to programming in js/node.js. I'm looking for guidance as to what node
packages I should be considering to achieve a certain functionality.
The functionality I'm looking for is approximately as follows:
a) an assortment of sensors puts data on a network. Each sensor has a
dedicated process that pre-processes sensor data. The processed data is
then transmitted to other processes;
b) there are several virtual 'layers' or 'groups'. Each layer has a
specific purpose or goal that is attained through the asynchronous
processing of the processed sensor data by one or more processes;
c) should any process fail/crash, the remaining processes are
unaffected;
d) similarly, processes can be added to the system as required without
affecting other processes; and
e) processes take input from other processes. For example, some
processes obviously will use the output of sensor pre-processing
processes. But some processes will simply be taking the output of other
processes.
So you can picture this network of processes (a 'mesh' ?) with some
subsets of the mesh working towards common goals. The idea is vaguely
comparable to neural networks but with large amounts of feedback say, a
liquid state NN vice multi-layer feed forward NN, complex processes vice
simple transfer functions at the mesh nodes, and asynchrony.
Within the mesh, processes are born and die, but the whole operation
remains largely unaffected in the sense that other processes will only
lose/gain information but they won't fail (cease trying to process). The
latter is important because a nuance is that a given process will decide
for itself what information it will use, what other processes it will
'listen' to and will have to adapt when changes occur. So processes must
be aware of each other.
Anyways, I can fake portions of all this using Matlab (in un-real-time)
but node.js seems to offer the potential to actually implement the idea in
real-time, kind of, maybe. (I'm still learning so some of you may know
better.) I was optimistic with one node package, hook.io, but it has
shut down. I'm happy to fork it but would need lots of help and guidance.
Several others were suggested including: kue, rabbitmq, zero-mq, nssocket,
dnode, amino, and federation. But whereas I'd found a clear explanation
of hook.io (with illustrations to confirm it seemed like what I
wanted)http://ejeklint.github.com/2011/09/23/hook.io-for-dummies-part-1-overview/most
other packages need knowledge (eg. - reddis) that I don't yet have
('federation'
being the exception https://github.com/jacobgroundwater/federation).
So that's what I'm trying to do and it looks like js/node.js can help me
do it. Is that a correct conclusion? If so, are there any packages or
approaches that you might suggest? As always, any constructive guidance or
advice would be appreciated.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
nodejs group.
To unsubscribe from this group and stop receiving emails from it, send an email
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Need an offline npm-style repository - what's a good approach?
You can set up a npm repository of your own pretty easily [1]. It doesn't have to replicate the public npm repository. I don't know how hard it would be to patch it so it does if package not locally availbale then fetch from the net but it could be another approach [1] http://clock.co.uk/tech-blogs/how-to-create-a-private-npmjs-repository On Tuesday, 19 February 2013 05:09:34 UTC+1, andy wrote: This would be ideal in our scenario. It's what Artifactory does for us in Java land (if a module doesn't exist in our local repo, it grabs it from maven central) and would be awesome to see in npm. If someone does an Enterprise NPM Repo Kickstarter I'll certainly kick in a few bucks to support it. :) andy On Mon, Feb 18, 2013 at 1:10 PM, nwhite change...@gmail.com javascript: wrote: I wish it was trivial to have a sparse npm server. One where I could publish my private modules to and replicate only the packages I'm interested in. Then have all npm package requests that are not found automatically forwarded to the official server. On Mon, Feb 18, 2013 at 12:14 PM, andy e virtu...@gmail.comjavascript: wrote: OK, great, thanks for the info. I'll chat it over and maybe give a shot at replicating the couch instance. Thanks for the help! Andy On Mon, Feb 18, 2013 at 12:08 PM, Bradley Meck bradle...@gmail.comjavascript: wrote: Right now without compaction you are looking at 45~ GB of data it looks like on the current npm public registry, and it can be replicated without needing any permission. On Monday, February 18, 2013 1:01:33 PM UTC-6, andy wrote: Cool, thanks for the suggestion(s). Two quick questions: 1) Can anyone replicate w/ the npm couch repo? I take it that's a yes but maybe you need permission (then again maybe people are smart enough to not want to have to do this, unlike us...) 2) How big? 10GB? 100GB? 1TB+? Thanks, Andy On Mon, Feb 18, 2013 at 11:50 AM, Luke Arduini luke.a...@gmail.comwrote: Touching on what Tim said, if you create a document for replication in /_replicator (not /_replicate) on couch you can turn couch off/on and have replication resume whenever. I do it all the time for my private npm and it works well, example: https://gist.github.com/st-**luke/4165831https://gist.github.com/st-luke/4165831 On Mon, Feb 18, 2013 at 1:46 PM, Tim Caswell t...@creationix.comwrote: If you want a mirror of the public npm repo, one option is to replicate the couch database. It's pretty big, but once replicated would give you a full mirror. I'm pretty sure you can do delta updates later on by putting the couch database back online and syncing again. On Mon, Feb 18, 2013 at 12:42 PM, Luke Arduini luke.a...@gmail.comwrote: You could set up git on a server on your lan and just specify dependencies in your projects' package.json files pointing to the git address. Seems like it would be the easiest way to go for private modules not on the internet. On Mon, Feb 18, 2013 at 1:23 PM, andy e virtu...@gmail.com wrote: Apologies in advance because I've only glanced at this problem, but we work in a unique environment where we have no Internet connectivity. So, with our Java apps, we run an instance of Artifactory on our LAN and load it by running an instance that is connected, which we then export and bring into the 'offline' instance. That gives us a sort of mirror of Java dependencies for maven and what not when we're developing. Is there anything like Artifactory for npm? Do I need to roll my own somehow (i.e. would a simple WebDAV server work or is it more complex)? I've glanced at Mike's node-reggie idea so maybe that is a place to start (https://github.com/mbrevoort/**node-reggiehttps://github.com/mbrevoort/node-reggie ). We don't need anything fancy - just a way to add npm modules to a project without having to check them in or pass around a giant .zip copy with all possible repos...etc. (Right now I just have a node_modules_for_work folder where I load up a ton of modules, then I zip that up and bring it in.) I'm happy to go off and do some reading/digging, so links to similar ideas/attempts are appreciated. Thanks, Andy -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/** node/wiki/Mailing-List-**Posting-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 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=enhttp://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop
[nodejs] Re: Multi-threaded Node.js
I'll add to greelgorke answer that shared state between parallel workers is more and more considered an antipattern these days. Erlang uses messages passing, Go has channels (kinda like streams) and node has a several message based communication pattern (streams, WebWorker API, dnode, etc.). Node.js doesn't force you to use these patterns, but it certainly promotes them. On Monday, 18 February 2013 10:07:18 UTC+1, greelgorke wrote: threads-a-gogo for small but cpu-heavy tasks. child_process.fork for permanently running worker-like services (or use tools like mongroup) cluster for horizontal scaling on a single machine to use all CPU-cores Node is designed mainly for I/O intensive Use Cases, in fact it was born out of the idea to build up a web server, which can handle many concurrent connections and can scale horizontal w/o pain. easy integration of websockets support is on top of it. this is it, what node is for. as much as i like the idea to do almost all in node, i admit, there are tasks, that are not good to solve in node. They are rare, but they are there. And node have no thready for a reason: the complexity. classic threads are able to share state. this is the root of evil in multithreading :) other solutions on thread basis are better i.E. erlang has threads with message passing only, other platforms uses other technics for thread communication. Node provides no multithreading to the developer, but it uses threads under the hood, so it is still efficient, at least as efficient as your longest computation. true parallelism !== threading. threads is one possible solution to implement parallel tasks. Node provides you with child_process and cluster to process-based solutions, web-services are another one, that distribute your app over network. and you have the ability to pass the task to completely other platform/tool/app if it suites it. a simple example here is to provide image scaling in your node app via passing the scaling work itself to imagemagick, which is a better tool for this kind of tasks. before i start to use threads in node i'd first look if i can delegate the task to some other tool or service. node is good at communication and streaming, and as such it also good as a dispatcher or commander in a cluster of services. Am Montag, 18. Februar 2013 01:15:48 UTC+1 schrieb RF: Hi, I'm CS student who is new to Node, and I have two questions: 1. Is there currently an existing mechanism (e.g. module, core functionality) that allows Node applications to spawn multiple threads (to take advantage of multiple cores for true parallelism) ? 2. If not, would this be a desirable feature? My understanding is that Node applications use a single thread to handle everything by queuing events on an event loop to be processed sequentially. I also understand that this is the core feature that allows Node to grant efficiency gains for specific types of applications, and is the (main?) source of Node's popularity. Given this fact then (and assuming that it's correct), it would seem counter-intuitive to enable multi-threaded functionality in Node when there are other languages/frameworks available potentially more suited to multi-threaded behavior. However, an example use case that I'm thinking of is a situation whereby an existing Node application needs to be adapted or extended with some functionality that would benefit from true parallelism. So, maybe 3 or 4 threads could be created that would handle 3 or 4 tasks more efficiently than Node's existing sequential behavior, while still taking advantage of Node's established execution model in other areas of the application. I was thinking along the lines of creating a Node module that exposes an interface for creating threads and supplying them with the necessary function (and also some mechanisms for dealing with shared data concurrency and consensus issues). I have searched unsuccessfully through available resources in an attempt to answer the above questions, so I'm hoping that someone can help me out. Regards, -Rob -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Module assistance request
I know, that's why one of the things I've done is delete the zlib streams. 0.10 won't have streaming bzlib support though. On Monday, 18 February 2013 21:16:41 UTC, Raynos wrote: node 0.10 will having streaming zlib. On Mon, Feb 18, 2013 at 2:12 AM, OrangeDog ja...@howeswho.co.ukjavascript: wrote: If someone could give me a hand replacing the wscript on https://github.com/OrangeDog/node-gzbz2/tree/streams2 with a proper gyp build, I would be very grateful. There still don't seem to be any simple tutorials or examples for 0.6+ modules around. I look forward to your pull requests :) -- -- 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.comjavascript: To unsubscribe from this group, send email to nodejs+un...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] jsonobject not replaces \n character with new line .
hi following is the process i do. i create jsonobject in javascript then in java i use that json object and putted that string data in DB. db doent' store \n but it directly stores it in new lines. while reteriving time i gets string with \n but now when i convert java obj to jsonobject \n is not replace with new lines and i render that json object on UI. and ui also not showing \n . -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Help! NPM pack includes folder, but NPM install does not?
I built a small package to try uploading to the npm registry. When I
install it back, however, it's missing the lib folder.
This is the (summarized) `package.json`:
{
# author, name, description, version, repository
files: [bin, src, lib, Makefile],
main: ./lib/foo.js,
bin: {
foo: ./bin/foo
},
# dependencies, engines
}
When I issue npm pack, the resulting tar file *contains* the lib folder as
expected.
However, when after publishing I run`npm install -g, the package installed
to `/usr/lib/node_modules is *missing* the lib folder. All other files are
there.
What am I missing?
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
nodejs group.
To unsubscribe from this group and stop receiving emails from it, send an email
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Return value from callback
Hi guys!
I'm working in a Geddy.JS application and I have one problem with one
function.
In my view(in EJS) I have the next:
*%= h.comments(debate); %*
*
*
My problem: When we go to the comments function, we have:
*
*
*
exports.comments = function (debate) {
debate.getComments(function(err,comments){
console.log(comments.length);
return comments.length;
});
};
My app doesn't print anything, but CONSOLE.LOG prints all perfect.
How can I return the value and print it into the view?
Thanks to all
*
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
nodejs group.
To unsubscribe from this group and stop receiving emails from it, send an email
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Help! NPM pack includes folder, but NPM install does not?
You are missing the lib folder.
Le 19 févr. 2013 12:11, Santiago Lezica slezic...@gmail.com a écrit :
I built a small package to try uploading to the npm registry. When I
install it back, however, it's missing the lib folder.
This is the (summarized) `package.json`:
{
# author, name, description, version, repository
files: [bin, src, lib, Makefile],
main: ./lib/foo.js,
bin: {
foo: ./bin/foo
},
# dependencies, engines
}
When I issue npm pack, the resulting tar file *contains* the lib folder
as expected.
However, when after publishing I run`npm install -g, the package
installed to `/usr/lib/node_modules is *missing* the lib folder. All
other files are there.
What am I missing?
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
nodejs group.
To unsubscribe from this group and stop receiving emails from it, send an
email to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
nodejs group.
To unsubscribe from this group and stop receiving emails from it, send an email
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Best way to reload?
On Mon, Feb 18, 2013 at 7:05 PM, Federico Kereki fker...@gmail.com wrote: I'm guessing that you could have a process running periodically, which would monitor loaded modules for updates and, if needed, require(...) them again after having done a delete require.cache[...]. This is actually very different than what PHP does. In PHP, you have nothing shared across requests (unless you're sharing through an external service). In node, if you re-require() a module, you're going to kill any state that was being tracked inside that module. You'll also need to write your code in a different style than you normally would because you wouldn't want to hold on to module references. You'd also need to make sure that your old and new code can work together. With PHP, you're getting a clean slate on every request. You *can* setup your node server to work this way, but you probably won't. My only hard-and-fast requirement is that no connection is lost because of the restart -- connected users shouldn't notice any change at all, though I could stand a certain delay. You'll need to write logic for a graceful shutdown so that you can send a signal to your process and have it stop accepting new requests, but not exit until it has finished serving all the requests that it has already received. If you don't want to miss any connections, you'll probably want to have a few processes running on different ports and have a balancer in front. You can stagger the restarts to avoid down time. What's the best way? It's likely going to depend on your server/network architecture. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Dynamic Web app in Node JS without Jade and Stylus
Hi, I would like to do the following, 1) Have regular .html .css .js files just like a normal web app 2) Interact with Node Js only through Ajax calls 3) But All files mentioned in 1) are also hosted on the same Node Http server. So when I say http://localhost:3000/index.html, Node Js server should give me index.html along with all css js files included in it. Then my Javascript Ajax code should drive the functionality with Node program getting called by ajax request. Can anyone please please suggest me the best way to do this ? I don't want to use Jade or Stylus. I want to develop as if I am using tomcat or wamp server use power of Node where ever needed only. I am aware of express js framework but don't know how it will be useful for above scenario. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: [PATCH] NEW API: fs.seek()
fs.read() with a position argument doesn't set the current file position (neither does pread). So you can't use the position argument to seek inside a file -- unless you *always* pass the position argument, and manually keep incrementing it. It would be nice (read, unsurprising) to just add fs.seek() to the API. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: Return value from callback
as far as i now ejs (as most of other template engines) does not support
asynchronous helper. you have to fetch the comments first and then pass
them to your template rendering
in your controller:
function(req, res, params){
var debate = //resolve the debate
*
debate.getComments(function(err,comments){
*
*
console.log(comments.length);
self.respond({comments: comments, debate: debate})
});
*
}
in view
*%= comments.length; %*
Am Montag, 18. Februar 2013 20:16:51 UTC+1 schrieb Eric Ponce:
Hi guys!
I'm working in a Geddy.JS application and I have one problem with one
function.
In my view(in EJS) I have the next:
*%= h.comments(debate); %*
*
*
My problem: When we go to the comments function, we have:
*
*
*
exports.comments = function (debate) {
debate.getComments(function(err,comments){
console.log(comments.length);
return comments.length;
});
};
My app doesn't print anything, but CONSOLE.LOG prints all perfect.
How can I return the value and print it into the view?
Thanks to all
*
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
nodejs group.
To unsubscribe from this group and stop receiving emails from it, send an email
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: jsonobject not replaces \n character with new line .
\n is a new line here are to few infos to help. the db may encode the new lines wrong, the ui may render it wrong, the conversion of java to json may go wrong etc. Am Dienstag, 19. Februar 2013 07:46:24 UTC+1 schrieb mkg: hi following is the process i do. i create jsonobject in javascript then in java i use that json object and putted that string data in DB. db doent' store \n but it directly stores it in new lines. while reteriving time i gets string with \n but now when i convert java obj to jsonobject \n is not replace with new lines and i render that json object on UI. and ui also not showing \n . -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: jsonobject not replaces \n character with new line .
btw. it's not a node.js question, right? :D Am Dienstag, 19. Februar 2013 15:49:48 UTC+1 schrieb greelgorke: \n is a new line here are to few infos to help. the db may encode the new lines wrong, the ui may render it wrong, the conversion of java to json may go wrong etc. Am Dienstag, 19. Februar 2013 07:46:24 UTC+1 schrieb mkg: hi following is the process i do. i create jsonobject in javascript then in java i use that json object and putted that string data in DB. db doent' store \n but it directly stores it in new lines. while reteriving time i gets string with \n but now when i convert java obj to jsonobject \n is not replace with new lines and i render that json object on UI. and ui also not showing \n . -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: Best way to reload?
look at this https://github.com/LearnBoost/up it in fact spinns new worker processes and let the old ones live for defined amount of time, so they have the chance to end their work gracefully before they die. and you have a cluster and simple keep-alive monitoring for free. Am Dienstag, 19. Februar 2013 01:05:55 UTC+1 schrieb Federico Kereki: Hi! What's the best way to reload a node.js website? I mean, working with Apache/PHP if you just upload a new PHP file, all newcomers will use that file, without needing to restart/reload Apache. However, if you simply kill a node.js process and restart it, currently connected users will be in trouble, processes may be aborted in the middle, updates could be lost, etc. I'm guessing that you could have a process running periodically, which would monitor loaded modules for updates and, if needed, require(...) them again after having done a delete require.cache[...]. I've also found recommendations for node-supervisor and nodemon, and I'm sure there must be some more out there. My only hard-and-fast requirement is that no connection is lost because of the restart -- connected users shouldn't notice any change at all, though I could stand a certain delay. What's the best way? Thanks, and best regards, Federico Kereki -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Re: [PATCH] NEW API: fs.seek()
See the fs-ext module on npm. Note: It needs updated to use gyp - I haven't had time to do it. Patches welcome. On Wed, Feb 13, 2013 at 5:33 PM, C. Scott Ananian csc...@laptop.org wrote: fs.read() with a position argument doesn't set the current file position (neither does pread). So you can't use the position argument to seek inside a file -- unless you *always* pass the position argument, and manually keep incrementing it. It would be nice (read, unsurprising) to just add fs.seek() to the API. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Help! NPM pack includes folder, but NPM install does not?
Works for me: https://gist.github.com/4986672
On Tue, Feb 19, 2013 at 3:41 AM, Berger Kennedy FOTSO
fober...@gmail.com wrote:
You are missing the lib folder.
Le 19 févr. 2013 12:11, Santiago Lezica slezic...@gmail.com a écrit :
I built a small package to try uploading to the npm registry. When I
install it back, however, it's missing the lib folder.
This is the (summarized) `package.json`:
{
# author, name, description, version, repository
files: [bin, src, lib, Makefile],
main: ./lib/foo.js,
bin: {
foo: ./bin/foo
},
# dependencies, engines
}
When I issue npm pack, the resulting tar file contains the lib folder as
expected.
However, when after publishing I run`npm install -g, the package installed
to `/usr/lib/node_modules is missing the lib folder. All other files are
there.
What am I missing?
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
nodejs group.
To unsubscribe from this group and stop receiving emails from it, send an
email to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
nodejs group.
To unsubscribe from this group and stop receiving emails from it, send an
email to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
nodejs group.
To unsubscribe from this group and stop receiving emails from it, send an email
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Module assistance request
Zlib streams are in 0.6, dude. On Mon, Feb 18, 2013 at 1:16 PM, Jake Verbaten rayn...@gmail.com wrote: node 0.10 will having streaming zlib. On Mon, Feb 18, 2013 at 2:12 AM, OrangeDog ja...@howeswho.co.uk wrote: If someone could give me a hand replacing the wscript on https://github.com/OrangeDog/node-gzbz2/tree/streams2 with a proper gyp build, I would be very grateful. There still don't seem to be any simple tutorials or examples for 0.6+ modules around. I look forward to your pull requests :) -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Wanted: federated-event/message-emitting platform?
Sounds like you have a series of agents that need to be social with each other? Have you considered using something derived from the original web collection/stream of content, Atom? In particular, a bunch of OStatus/ActivityStrea.ms nodes can pass data down a chain of processing agents, appending data into the next guys queue and the next guy picking it up, doing whatever intermediary processing it needs, and passing it along. Changing the runtime behavior is a matter of altering an ingesting process/agent's behavior, redirecting it to another endpoint or reconfiguring it. I'd definitely look at repruposing social networking software such as pump.io to get your machines making a social network of work or data items: machines, the most social of beasts I know! I'd be most interested in hearing any mismatches, where people feel this high level implementation idea doesn't suit this high level problem description. There's a lot of very low level transport-grade technologies listed, but a resourceful outlook, and a standards stack built to talk about collections of things, is what I would naturally turn to if one needs to socialize a data flow across systems: you'll get much further much faster than hacking some coordination schema yourself, or borrowing a raw message transport. It'd be a delight if dr-ses (Distributed Resilient Secure EcmaScript) were further along, as a low level language construct for weaving together systems, but it's not, so use web standards to create and data-flow across collections. -rektide -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Need an offline npm-style repository - what's a good approach?
Wow, that link is awesome. Thank you. Andy Sent from my iPhone On Feb 19, 2013, at 1:56 AM, Floby florent.j...@gmail.com wrote: You can set up a npm repository of your own pretty easily [1]. It doesn't have to replicate the public npm repository. I don't know how hard it would be to patch it so it does if package not locally availbale then fetch from the net but it could be another approach [1] http://clock.co.uk/tech-blogs/how-to-create-a-private-npmjs-repository On Tuesday, 19 February 2013 05:09:34 UTC+1, andy wrote: This would be ideal in our scenario. It's what Artifactory does for us in Java land (if a module doesn't exist in our local repo, it grabs it from maven central) and would be awesome to see in npm. If someone does an Enterprise NPM Repo Kickstarter I'll certainly kick in a few bucks to support it. :) andy On Mon, Feb 18, 2013 at 1:10 PM, nwhite change...@gmail.com wrote: I wish it was trivial to have a sparse npm server. One where I could publish my private modules to and replicate only the packages I'm interested in. Then have all npm package requests that are not found automatically forwarded to the official server. On Mon, Feb 18, 2013 at 12:14 PM, andy e virtu...@gmail.com wrote: OK, great, thanks for the info. I'll chat it over and maybe give a shot at replicating the couch instance. Thanks for the help! Andy On Mon, Feb 18, 2013 at 12:08 PM, Bradley Meck bradle...@gmail.com wrote: Right now without compaction you are looking at 45~ GB of data it looks like on the current npm public registry, and it can be replicated without needing any permission. On Monday, February 18, 2013 1:01:33 PM UTC-6, andy wrote: Cool, thanks for the suggestion(s). Two quick questions: 1) Can anyone replicate w/ the npm couch repo? I take it that's a yes but maybe you need permission (then again maybe people are smart enough to not want to have to do this, unlike us...) 2) How big? 10GB? 100GB? 1TB+? Thanks, Andy On Mon, Feb 18, 2013 at 11:50 AM, Luke Arduini luke.a...@gmail.com wrote: Touching on what Tim said, if you create a document for replication in /_replicator (not /_replicate) on couch you can turn couch off/on and have replication resume whenever. I do it all the time for my private npm and it works well, example: https://gist.github.com/st-luke/4165831 On Mon, Feb 18, 2013 at 1:46 PM, Tim Caswell t...@creationix.com wrote: If you want a mirror of the public npm repo, one option is to replicate the couch database. It's pretty big, but once replicated would give you a full mirror. I'm pretty sure you can do delta updates later on by putting the couch database back online and syncing again. On Mon, Feb 18, 2013 at 12:42 PM, Luke Arduini luke.a...@gmail.com wrote: You could set up git on a server on your lan and just specify dependencies in your projects' package.json files pointing to the git address. Seems like it would be the easiest way to go for private modules not on the internet. On Mon, Feb 18, 2013 at 1:23 PM, andy e virtu...@gmail.com wrote: Apologies in advance because I've only glanced at this problem, but we work in a unique environment where we have no Internet connectivity. So, with our Java apps, we run an instance of Artifactory on our LAN and load it by running an instance that is connected, which we then export and bring into the 'offline' instance. That gives us a sort of mirror of Java dependencies for maven and what not when we're developing. Is there anything like Artifactory for npm? Do I need to roll my own somehow (i.e. would a simple WebDAV server work or is it more complex)? I've glanced at Mike's node-reggie idea so maybe that is a place to start (https://github.com/mbrevoort/node-reggie). We don't need anything fancy - just a way to add npm modules to a project without having to check them in or pass around a giant .zip copy with all possible repos...etc. (Right now I just have a node_modules_for_work folder where I load up a ton of modules, then I zip that up and bring it in.) I'm happy to go off and do some reading/digging, so links to similar ideas/attempts are appreciated. Thanks, Andy -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nod...@googlegroups.com To unsubscribe from this group, send email to nodejs+un...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com. For more options, visit
Re: [nodejs] Module assistance request
He's was binding to zlib, which he said he's dropped now. But he's also binding to bzlib, which node does *not* bind to. James, I'll try to send you a basic binding.gyp for your project in a little bit. On Tue, Feb 19, 2013 at 7:06 AM, Isaac Schlueter i...@izs.me wrote: Zlib streams are in 0.6, dude. On Mon, Feb 18, 2013 at 1:16 PM, Jake Verbaten rayn...@gmail.com wrote: node 0.10 will having streaming zlib. On Mon, Feb 18, 2013 at 2:12 AM, OrangeDog ja...@howeswho.co.uk wrote: If someone could give me a hand replacing the wscript on https://github.com/OrangeDog/node-gzbz2/tree/streams2 with a proper gyp build, I would be very grateful. There still don't seem to be any simple tutorials or examples for 0.6+ modules around. I look forward to your pull requests :) -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Module assistance request
I've actually had a great experience so far with the pure js bzip library. https://github.com/skeggse/node-bzip -Mikeal On Feb 19, 2013, at February 19, 20139:50 AM, Nathan Rajlich nat...@tootallnate.net wrote: He's was binding to zlib, which he said he's dropped now. But he's also binding to bzlib, which node does *not* bind to. James, I'll try to send you a basic binding.gyp for your project in a little bit. On Tue, Feb 19, 2013 at 7:06 AM, Isaac Schlueter i...@izs.me wrote: Zlib streams are in 0.6, dude. On Mon, Feb 18, 2013 at 1:16 PM, Jake Verbaten rayn...@gmail.com wrote: node 0.10 will having streaming zlib. On Mon, Feb 18, 2013 at 2:12 AM, OrangeDog ja...@howeswho.co.uk wrote: If someone could give me a hand replacing the wscript on https://github.com/OrangeDog/node-gzbz2/tree/streams2 with a proper gyp build, I would be very grateful. There still don't seem to be any simple tutorials or examples for 0.6+ modules around. I look forward to your pull requests :) -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: Dynamic Web app in Node JS without Jade and Stylus
Great, someone who doesn't want to use express! I myself find this framework too specific as well. However, there are true advantages in using existing projects instead of re-inventing the wheel. Since the node http server is a bit rough around the edges though, some sort of http framework is recommended. Here's my pick: - Use connect (on which express is based) for the basic functionality ( http://www.senchalabs.org/connect/ ) as the webserver framework. - Use bodyparser middleware for POST request bodies. - Write your own middleware for API access. - Use static middleware for static file serving from a directory - You can copypaste this gist: https://gist.github.com/klovadis/4988305 Connect basically allows you to execute so called middleware functions on a http request in a linear order. Whenever a request comes in, each function does something (i.e. modify the request object to add cookie information) if applicable and continues to the next middleware, or responds to the request and skips the remaining middleware functions. So the order in which the middleware functions are added matters - you want to have decorating functions at the beginning and a catch all function at the end. The documentation of the exact workings of connect - to state things nicely - has room for improvement though. Express is based on connect and the way it works with middleware functions, but adds a lot of functionality for which you otherwise need to write your own middleware (i.e. a router or rendering jade templates out of the box). That is why lots of people do use express (*and tend to recommend it as the one and only solution whenever the word webserver is present*). In fact many other webserver frameworks do exist and are worth having a look at, but since I do know connect quite well by now I therefore recommend using it (without express on top of it). So in a nutshell: Place all your static files in a subfolder and let the static middleware serve them. Add api logic in a middleware function. No additional functionality is present. But do read up on the coolness of jade and stylus some time, there is a reason why people use those. All the best, Geerten On Tuesday, February 19, 2013 3:35:53 PM UTC+1, kanitkar...@gmail.com wrote: Hi, I would like to do the following, 1) Have regular .html .css .js files just like a normal web app 2) Interact with Node Js only through Ajax calls 3) But All files mentioned in 1) are also hosted on the same Node Http server. So when I say http://localhost:3000/index.html, Node Js server should give me index.html along with all css js files included in it. Then my Javascript Ajax code should drive the functionality with Node program getting called by ajax request. Can anyone please please suggest me the best way to do this ? I don't want to use Jade or Stylus. I want to develop as if I am using tomcat or wamp server use power of Node where ever needed only. I am aware of express js framework but don't know how it will be useful for above scenario. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Re: Best way to reload?
In general, with node.js you'll find that breaking up your back-end into many processes, works best. Have a single HTTP process and a separate websocket process that then emit IPC requests either directly or via a messaging bus like 0mq will help address issues like this. Specifically, in a well architectured highly decoupled application, development tends to be silo'd to specific concerns at any given time. So fixes to a specific service (process) would then require restarting only that specific service, and thus at worst any IPC requests made during the restart to that specific service would be dropped and could optionally be resubmitted. Additionally, using a message queue like 0mq offers cheap message buffering that will ensure (within reason) message delivery after restart so no requests get dropped. This also breaks up your application nicely as it leads to a better separation of state; Your main application logic doesn't store it. We use my teammate's, Michael Schoonmaker, 0mq library Shuttle: https://github.com/Schoonology/shuttle Development tends to go like this: 1. I'm making changes to the foo API namespace. 2. I spend most of my time updating things related to the foo namespace. 3. I constantly restart and retest internal IPC calls to the foo service 4. When I feel confident the functionality is complete, I integration test the new foo functionality as part of the whole system. Another nice perk of breaking your application into many decoupled focus processes, is it helps with horizontal scaling. Cheers, Adam Crabtree On Tue, Feb 19, 2013 at 10:46 AM, Mark Hahn m...@hahnca.com wrote: I use a websocket instead of page loads and the user can't tell when the server reboots. Socket.io automatically reconnects. On Tue, Feb 19, 2013 at 7:01 AM, greelgorke greelgo...@gmail.com wrote: look at this https://github.com/LearnBoost/up it in fact spinns new worker processes and let the old ones live for defined amount of time, so they have the chance to end their work gracefully before they die. and you have a cluster and simple keep-alive monitoring for free. Am Dienstag, 19. Februar 2013 01:05:55 UTC+1 schrieb Federico Kereki: Hi! What's the best way to reload a node.js website? I mean, working with Apache/PHP if you just upload a new PHP file, all newcomers will use that file, without needing to restart/reload Apache. However, if you simply kill a node.js process and restart it, currently connected users will be in trouble, processes may be aborted in the middle, updates could be lost, etc. I'm guessing that you could have a process running periodically, which would monitor loaded modules for updates and, if needed, require(...) them again after having done a delete require.cache[...]. I've also found recommendations for node-supervisor and nodemon, and I'm sure there must be some more out there. My only hard-and-fast requirement is that no connection is lost because of the restart -- connected users shouldn't notice any change at all, though I could stand a certain delay. What's the best way? Thanks, and best regards, Federico Kereki -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Better a little with righteousness than much gain with injustice. Proverbs 16:8 -- -- 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] Error: write EPIPE
Hi, We are getting EPIPE errors. Reproducing the error is a matter of uploading multiple files at the same time while keep on using the site, and eventually it will throw. Here is the stack trace: stack:[ Error: write EPIPE, at errnoException (net.js:770:11), at Object.afterWrite (net.js:594:19) ], Node version: 0.8.16 What is the right way to handle/avoid this potential error? Any documentation I could look into? On a somewhat related note, what's the status of domains? Thanks, Gustavo Machado machad...@gmail.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 --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Good news: nginx now supports websockets
Finally :) http://nginx.com/news/nginx-websockets.html -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Error: write EPIPE
On Tue, Feb 19, 2013 at 12:47 PM, Gustavo Machado machad...@gmail.com wrote: Hi, We are getting EPIPE errors. Reproducing the error is a matter of uploading multiple files at the same time while keep on using the site, and eventually it will throw. Here is the stack trace: stack:[ Error: write EPIPE, at errnoException (net.js:770:11), at Object.afterWrite (net.js:594:19) ], Node version: 0.8.16 What is the right way to handle/avoid this potential error? Any documentation I could look into? EPIPE means you're writing to a pipe or socket when the other end has terminated the connection. It's a run-time error; there is nothing you can do but close your end as well. On a somewhat related note, what's the status of domains? Alive and well? Thanks, Gustavo Machado machad...@gmail.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 --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Version 0.9.10 (Unstable)
2013.02.19, Version 0.9.10 (Unstable) * V8: Upgrade to 3.15.11.15 * npm: Upgrade to 1.2.12 * fs: Change default WriteStream config, increase perf (isaacs) * process: streamlining tick callback logic (Trevor Norris) * stream_wrap, udp_wrap: add read-only fd property (Ben Noordhuis) * buffer: accept negative indices in Buffer#slice() (Ben Noordhuis) * tls: Cycle data when underlying socket drains (isaacs) * stream: read(0) should not always trigger _read(n,cb) (isaacs) * stream: Empty strings/buffers do not signal EOF any longer (isaacs) * crypto: improve cipher/decipher error messages (Ben Noordhuis) * net: Respect the 'readable' flag on sockets (isaacs) * net: don't suppress ECONNRESET (Ben Noordhuis) * typed arrays: copy Buffer in typed array constructor (Ben Noordhuis) * typed arrays: make DataView throw on non-ArrayBuffer (Ben Noordhuis) * windows: MSI installer enhancements (Scott Blomquist, Jim Schubert) Source Code: http://nodejs.org/dist/v0.9.10/node-v0.9.10.tar.gz Macintosh Installer (Universal): http://nodejs.org/dist/v0.9.10/node-v0.9.10.pkg Windows Installer: http://nodejs.org/dist/v0.9.10/node-v0.9.10-x86.msi Windows x64 Installer: http://nodejs.org/dist/v0.9.10/x64/node-v0.9.10-x64.msi Windows x64 Files: http://nodejs.org/dist/v0.9.10/x64/ Linux 32-bit Binary: http://nodejs.org/dist/v0.9.10/node-v0.9.10-linux-x86.tar.gz Linux 64-bit Binary: http://nodejs.org/dist/v0.9.10/node-v0.9.10-linux-x64.tar.gz Solaris 32-bit Binary: http://nodejs.org/dist/v0.9.10/node-v0.9.10-sunos-x86.tar.gz Solaris 64-bit Binary: http://nodejs.org/dist/v0.9.10/node-v0.9.10-sunos-x64.tar.gz Other release files: http://nodejs.org/dist/v0.9.10/ Website: http://nodejs.org/docs/v0.9.10/ Documentation: http://nodejs.org/docs/v0.9.10/api/ Shasums: ``` 813d5f42b156b7d64f00b86e13d26ada3ef352e5 node-v0.9.10-darwin-x64.tar.gz 99dbe66fd0fc176fb3459ffcf62212dcb27bef10 node-v0.9.10-darwin-x86.tar.gz 3a5a465238cbdbdac9786c204fd27be61ce7159a node-v0.9.10-linux-x64.tar.gz 3340ac206ec1a1f827c954efdfa1351dcfe9f419 node-v0.9.10-linux-x86.tar.gz b920b2e57c6df1e080966fdeccbfd1b384b156d4 node-v0.9.10-sunos-x64.tar.gz 9c1744352bb1bc71f48f8aea1aff6aeefe35a394 node-v0.9.10-sunos-x86.tar.gz f1daaafc330cc9993a3a6f7ca8b9cc870b49e75c node-v0.9.10-x86.msi 2b6c70f57c1513e8f5151785b1ac263565983918 node-v0.9.10.pkg 265542c15cf939b7c71a545758d835ed44d791d3 node-v0.9.10.tar.gz 653f24d53f411217d57ed18d73921ff4721f00dd node.exe 7d62da67a7b33628d7d90c9d5037cf564dfc5ce4 node.exp cfebbcd81db602b2f051328a9924e19ca2cb6235 node.lib a31694cb9e03d13a616f3cc634852d8dc98e69b8 node.pdb 5f94c1cc9301a8b85082fee7549aa376aedd8ec5 x64/node-v0.9.10-x64.msi 7716c01ce60f7c65100cc405726badf8476afebd x64/node.exe 121d4a721968ba4631d29de07e5d6c326d259b4b x64/node.exp 17f651000f6b0c840efe539ae5257cb894481c49 x64/node.lib d04242a5ec3a3104931ec8de6a846a8f7746b1fd x64/node.pdb ``` -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Socket.io throught new Nginx version 1.3
The current developer version of Nginx now supports Websockets. ( http://nginx.com/news/nginx-websockets.html) Does any one have tried this yet and could give some insight if it is now possible to proxy socket.io connections through Nginx? -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Socket.io throught new Nginx version 1.3
I just get: debug - client authorized info - handshake authorized b9XMag_ay5Jti2KQ8VxB debug - setting request GET /socket.io/1/websocket/b9XMag_ay5Jti2KQ8VxB debug - set heartbeat interval for client b9XMag_ay5Jti2KQ8VxB warn - websocket connection invalid info - transport end (undefined) I can't find any information in how to implement websockets with nginx. I have nginx 1.3.13 from chris lea PPA 2013/2/19 Philipp Klose m...@thehippo.de The current developer version of Nginx now supports Websockets. ( http://nginx.com/news/nginx-websockets.html) Does any one have tried this yet and could give some insight if it is now possible to proxy socket.ioconnections through Nginx? -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: Dynamic Web app in Node JS without Jade and Stylus
Thanks a lot Gregor Geerten for your replies !!! I have following scenarios or situations 1. In my projects, HTML designers create mockups in plane HTML CSS with dummy data where dynamically generated data will be placed and HTML templates can be used by JavaScript developer later. Heavy use of CSS and complex nested Html gets created with supporting jQuery or Javascript code of jQuery plugins used sometimes. So a bit difficult to imagine doing same in Jade. 2. I don't know about Jade, but I am fond of HandleBars, so I want to know how to use it in Node JS project ? 3. The scenario is like this - If I have an existing project with this technology stack - HTML + CSS + JS + jQuery + PHP(only for database calls and not for .php pages, php is connected to .html pages only through Ajax). And now I just want port this Dynamic Web App to NodeJS by replacing business logic written in PHP with Node JS and also have Node JS as http web server. So no more PHP or WAMP in picture now. How can I achieve this without Jade Stylus ? Any pointers/ links to github repos or jsFiddles are welcome. 4. What is an excellent ebook that I can buy which teaches how to do end to end development of HTML + CSS + jQuery + HandleBars + Backbone/ KnockoutJS + NodeJS kind of web apps without Jade 5. Can any one of you experienced people elaborate on what are key advantages of using Jade over HandleBars ? I just don't want to learn new thing for the sake of it without a good reason :) 6. How to achieve same thing mentioned in link( http://thecodinghumanist.com/blog/archives/2011/5/6/serving-static-files-from-node-jshttps://mex07a.emailsrvr.com/owa/redir.aspx?C=0XUOyGttuk-E178ujGwQ4PWeAPyW4s9Ic5T8XNiO6uB0y_vWS3p3hQueay6fxh98syLG2dS89qU.URL=http%3a%2f%2fthecodinghumanist.com%2fblog%2farchives%2f2011%2f5%2f6%2fserving-static-files-from-node-js) in a better abstract way ? On Tuesday, February 19, 2013 11:49:13 PM UTC+5:30, Geerten van Meel wrote: Great, someone who doesn't want to use express! I myself find this framework too specific as well. However, there are true advantages in using existing projects instead of re-inventing the wheel. Since the node http server is a bit rough around the edges though, some sort of http framework is recommended. Here's my pick: - Use connect (on which express is based) for the basic functionality ( http://www.senchalabs.org/connect/ ) as the webserver framework. - Use bodyparser middleware for POST request bodies. - Write your own middleware for API access. - Use static middleware for static file serving from a directory - You can copypaste this gist: https://gist.github.com/klovadis/4988305 Connect basically allows you to execute so called middleware functions on a http request in a linear order. Whenever a request comes in, each function does something (i.e. modify the request object to add cookie information) if applicable and continues to the next middleware, or responds to the request and skips the remaining middleware functions. So the order in which the middleware functions are added matters - you want to have decorating functions at the beginning and a catch all function at the end. The documentation of the exact workings of connect - to state things nicely - has room for improvement though. Express is based on connect and the way it works with middleware functions, but adds a lot of functionality for which you otherwise need to write your own middleware (i.e. a router or rendering jade templates out of the box). That is why lots of people do use express (*and tend to recommend it as the one and only solution whenever the word webserver is present*). In fact many other webserver frameworks do exist and are worth having a look at, but since I do know connect quite well by now I therefore recommend using it (without express on top of it). So in a nutshell: Place all your static files in a subfolder and let the static middleware serve them. Add api logic in a middleware function. No additional functionality is present. But do read up on the coolness of jade and stylus some time, there is a reason why people use those. All the best, Geerten On Tuesday, February 19, 2013 3:35:53 PM UTC+1, kanitkar...@gmail.comwrote: Hi, I would like to do the following, 1) Have regular .html .css .js files just like a normal web app 2) Interact with Node Js only through Ajax calls 3) But All files mentioned in 1) are also hosted on the same Node Http server. So when I say http://localhost:3000/index.html, Node Js server should give me index.html along with all css js files included in it. Then my Javascript Ajax code should drive the functionality with Node program getting called by ajax request. Can anyone please please suggest me the best way to do this ? I don't want to use Jade or Stylus. I want to develop
Re: [nodejs] Socket.io throught new Nginx version 1.3
I've found this: http://thechangelog.com/nginx-gains-support-for-websockets/
Just this lines:
location /chat/ {
proxy_pass http://backend;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection upgrade;
}
2013/2/19 Andre Contreras inu.c...@gmail.com
I just get:
debug - client authorized
info - handshake authorized b9XMag_ay5Jti2KQ8VxB
debug - setting request GET /socket.io/1/websocket/b9XMag_ay5Jti2KQ8VxB
debug - set heartbeat interval for client b9XMag_ay5Jti2KQ8VxB
warn - websocket connection invalid
info - transport end (undefined)
I can't find any information in how to implement websockets with nginx. I
have nginx 1.3.13 from chris lea PPA
2013/2/19 Philipp Klose m...@thehippo.de
The current developer version of Nginx now supports Websockets. (
http://nginx.com/news/nginx-websockets.html) Does any one have tried
this yet and could give some insight if it is now possible to proxy
socket.io connections through Nginx?
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
nodejs group.
To unsubscribe from this group and stop receiving emails from it, send an
email to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
nodejs group.
To unsubscribe from this group and stop receiving emails from it, send an email
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: Good news: nginx now supports websockets
Thanks for sharing. That's excellent! On Wednesday, February 20, 2013 4:12:58 AM UTC+7, Vitaly Puzrin wrote: Finally :) http://nginx.com/news/nginx-websockets.html -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] [ANN] Boston Node.js in the wild February Meetup
The Boston based Node.js in the wild Meetup group will be holding its next meeting on Wed Feb 20, 2013 at 7pm in the Brightcove offices. This meetup will have a panel discussion where participants will provide information about their company, how they're using or planning to use Node.js. We'll also look at the current state of Node.js from an adoption and maturity point of view. List of people/companies on the panel: David Greenstein from Kibits Alex Nazerian from Kutout Jesse Streb from on Kaymbu Angel Municio from PlannedUp TBD from Brightcove There will be free drinks and pizza at the event. For more information and to signup: http://www.meetup.com/Node-js-in-the-wild -- Daniel R. dani...@neophi.com [http://danielr.neophi.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 --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: Need an offline npm-style repository - what's a good approach?
When your build your NPM registry, you can replicate single package with sync_package, but replicate all packages(It's pretty big). https://github.com/TBEDP/sync_package 在 2013年2月19日星期二UTC+8上午2时23分05秒，andy写道： Apologies in advance because I've only glanced at this problem, but we work in a unique environment where we have no Internet connectivity. So, with our Java apps, we run an instance of Artifactory on our LAN and load it by running an instance that is connected, which we then export and bring into the 'offline' instance. That gives us a sort of mirror of Java dependencies for maven and what not when we're developing. Is there anything like Artifactory for npm? Do I need to roll my own somehow (i.e. would a simple WebDAV server work or is it more complex)? I've glanced at Mike's node-reggie idea so maybe that is a place to start ( https://github.com/mbrevoort/node-reggie). We don't need anything fancy - just a way to add npm modules to a project without having to check them in or pass around a giant .zip copy with all possible repos...etc. (Right now I just have a node_modules_for_work folder where I load up a ton of modules, then I zip that up and bring it in.) I'm happy to go off and do some reading/digging, so links to similar ideas/attempts are appreciated. Thanks, Andy -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: Version 0.9.10 (Unstable)
How about release roadmap? Any 1.0.0 news? 在 2013年2月20日星期三UTC+8上午6时02分55秒，Isaac Schlueter写道： 2013.02.19, Version 0.9.10 (Unstable) * V8: Upgrade to 3.15.11.15 * npm: Upgrade to 1.2.12 * fs: Change default WriteStream config, increase perf (isaacs) * process: streamlining tick callback logic (Trevor Norris) * stream_wrap, udp_wrap: add read-only fd property (Ben Noordhuis) * buffer: accept negative indices in Buffer#slice() (Ben Noordhuis) * tls: Cycle data when underlying socket drains (isaacs) * stream: read(0) should not always trigger _read(n,cb) (isaacs) * stream: Empty strings/buffers do not signal EOF any longer (isaacs) * crypto: improve cipher/decipher error messages (Ben Noordhuis) * net: Respect the 'readable' flag on sockets (isaacs) * net: don't suppress ECONNRESET (Ben Noordhuis) * typed arrays: copy Buffer in typed array constructor (Ben Noordhuis) * typed arrays: make DataView throw on non-ArrayBuffer (Ben Noordhuis) * windows: MSI installer enhancements (Scott Blomquist, Jim Schubert) Source Code: http://nodejs.org/dist/v0.9.10/node-v0.9.10.tar.gz Macintosh Installer (Universal): http://nodejs.org/dist/v0.9.10/node-v0.9.10.pkg Windows Installer: http://nodejs.org/dist/v0.9.10/node-v0.9.10-x86.msi Windows x64 Installer: http://nodejs.org/dist/v0.9.10/x64/node-v0.9.10-x64.msi Windows x64 Files: http://nodejs.org/dist/v0.9.10/x64/ Linux 32-bit Binary: http://nodejs.org/dist/v0.9.10/node-v0.9.10-linux-x86.tar.gz Linux 64-bit Binary: http://nodejs.org/dist/v0.9.10/node-v0.9.10-linux-x64.tar.gz Solaris 32-bit Binary: http://nodejs.org/dist/v0.9.10/node-v0.9.10-sunos-x86.tar.gz Solaris 64-bit Binary: http://nodejs.org/dist/v0.9.10/node-v0.9.10-sunos-x64.tar.gz Other release files: http://nodejs.org/dist/v0.9.10/ Website: http://nodejs.org/docs/v0.9.10/ Documentation: http://nodejs.org/docs/v0.9.10/api/ Shasums: ``` 813d5f42b156b7d64f00b86e13d26ada3ef352e5 node-v0.9.10-darwin-x64.tar.gz 99dbe66fd0fc176fb3459ffcf62212dcb27bef10 node-v0.9.10-darwin-x86.tar.gz 3a5a465238cbdbdac9786c204fd27be61ce7159a node-v0.9.10-linux-x64.tar.gz 3340ac206ec1a1f827c954efdfa1351dcfe9f419 node-v0.9.10-linux-x86.tar.gz b920b2e57c6df1e080966fdeccbfd1b384b156d4 node-v0.9.10-sunos-x64.tar.gz 9c1744352bb1bc71f48f8aea1aff6aeefe35a394 node-v0.9.10-sunos-x86.tar.gz f1daaafc330cc9993a3a6f7ca8b9cc870b49e75c node-v0.9.10-x86.msi 2b6c70f57c1513e8f5151785b1ac263565983918 node-v0.9.10.pkg 265542c15cf939b7c71a545758d835ed44d791d3 node-v0.9.10.tar.gz 653f24d53f411217d57ed18d73921ff4721f00dd node.exe 7d62da67a7b33628d7d90c9d5037cf564dfc5ce4 node.exp cfebbcd81db602b2f051328a9924e19ca2cb6235 node.lib a31694cb9e03d13a616f3cc634852d8dc98e69b8 node.pdb 5f94c1cc9301a8b85082fee7549aa376aedd8ec5 x64/node-v0.9.10-x64.msi 7716c01ce60f7c65100cc405726badf8476afebd x64/node.exe 121d4a721968ba4631d29de07e5d6c326d259b4b x64/node.exp 17f651000f6b0c840efe539ae5257cb894481c49 x64/node.lib d04242a5ec3a3104931ec8de6a846a8f7746b1fd x64/node.pdb ``` -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups nodejs group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
