.
From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Ed Summers
[e...@pobox.com]
Sent: 09 May 2012 04:26
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Anyone using node.js?
I've been using NodeJS in a few side projects lately, and have come to
like it quite a bit for certain
On Wed, May 9, 2012 at 3:47 AM, Berry, Rob robert.be...@liverpool.ac.uk wrote:
You almost certainly should not rewrite an entire codebase from scratch
unless there's an extremely good reason to do so. JoelOnSoftware did a good
piece on it -
for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Ed Summers
[e...@pobox.com]
Sent: 09 May 2012 09:24
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Anyone using node.js?
On Wed, May 9, 2012 at 3:47 AM, Berry, Rob robert.be...@liverpool.ac.uk wrote:
You almost certainly should not rewrite an entire
On Wed, May 9, 2012 at 4:50 AM, Berry, Rob robert.be...@liverpool.ac.uk wrote:
Though re Python I would say mixing Django with Twisted is a fairly blatant
error. There are libraries built on Twisted to serve web-pages, and if you're
doing event-driven programming you should really be using
May 2012 10:05
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Anyone using node.js?
On Wed, May 9, 2012 at 4:50 AM, Berry, Rob robert.be...@liverpool.ac.uk wrote:
Though re Python I would say mixing Django with Twisted is a fairly blatant
error. There are libraries built on Twisted to serve
On Wed, May 9, 2012 at 5:17 AM, Berry, Rob robert.be...@liverpool.ac.uk wrote:
No, fair enough, you are right. If that's the paradigm you want it would be a
better bet to go for a language that has it built in from the ground up.
And (just so it isn't lost) you are absolutely right to question
On Tue, May 8, 2012 at 11:26 PM, Ed Summers e...@pobox.com wrote:
For both these apps the socket.io library for NodeJS provided a really
nice abstraction for streaming data from the server to the client
using a variety of mechanisms: web sockets, flash socket, long
polling, JSONP polling,
Gruber
Sent: Tuesday, May 08, 2012 10:35 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Anyone using node.js?
Thanks, it really helps to get a list of projects using it so I can get a
better sense of what's possible.
On Tue, May 8, 2012 at 10:23 AM, Cary Gordon listu...@chillco.com wrote
On Mon, May 7, 2012 at 10:17 PM, Ethan Gruber ewg4x...@gmail.com wrote:
It was recently suggested to me that a project I am working on may adopt
node.js for its architecture (well, be completely re-written for node.js).
I don't know anything about node.js, and have only heard of it in some
I have done some work with node building apps in the areas of mapping
and communication (chat, etc.).
Looking at the list at
https://github.com/joyent/node/wiki/Projects,-Applications,-and-Companies-Using-Node,
the emphasis on real-time stands out.
Node is fast and lightweight, and is well
Thanks. I have been working on a system that allows editing of RDF in web
forms, creating linked data connections in the background, publishing to
eXist and Solr for dissemination, and will eventually integrate operation
with an RDF triplestore/SPARQL, all with Tomcat apps. I'm not sure it is
Node is fairly new - so it would be a little experimental.
But it does have an active community, and there are quite a few useful
packages; including a solr-client (http://search.npmjs.org/#/solr-client).
I would look into it, if only for the purposes of learning a little more
about it and to
Thanks, it really helps to get a list of projects using it so I can get a
better sense of what's possible.
On Tue, May 8, 2012 at 10:23 AM, Cary Gordon listu...@chillco.com wrote:
I have done some work with node building apps in the areas of mapping
and communication (chat, etc.).
Looking at
On Tue, May 8, 2012 at 10:17 AM, Ethan Gruber ewg4x...@gmail.com wrote:
Thanks. I have been working on a system that allows editing of RDF in web
forms, creating linked data connections in the background, publishing to
eXist and Solr for dissemination, and will eventually integrate operation
Your triplestore and/or the client libraries you use to interface with it might
well be Java too. While it's true that Apache, Java, and Tomcat are no longer
the new hotness, they are solid and proven technologies. You would have to
start breaking my fingers to convince me to ditch Solr. And as
Node is about three years old, which makes it an infant in library
terms. Rails is about eight and still doesn't have a lot of traction.
Perl (25 years) and Java (17 years) seem to be considered proven.
Node.js might wipe the floor (or not) with Java and Perl someday, but
ATM, those tools have
On May 8, 2012, at 10:17 AM, Ethan Gruber wrote:
in. Our data is exclusively XML, so LAMP/Rails aren't really options.
^^ Really? Nobody's going to take the bait with this one?
-Ross.
Ethan
On Tue, May 8, 2012 at 10:03 AM, Nate Vack njv...@wisc.edu wrote:
On Mon, May 7, 2012 at
On Tue, May 8, 2012 at 11:45 AM, Ross Singer rossfsin...@gmail.com wrote:
On May 8, 2012, at 10:17 AM, Ethan Gruber wrote:
in. Our data is exclusively XML, so LAMP/Rails aren't really options.
^^ Really? Nobody's going to take the bait with this one?
I can't see why they would; parsing XML
P͎̘̈̈̈Ä͖̈R̛̳̈̈̈S̡͇̈ͧ̈̽̈̈̈ͨÏ̙̐̈̈N͉̈ͤ̈̌̈͑̈̈͊G͓̈̈͐̈̽̈ ̈ͯ̈̈ͫ̈̌̈͛ͅẌ̿̈M͔̈͆̈̄̈̈̈͢L̙̈͋̈ͮ̈̈ ̠̼̈̈̈͋̈͏̈̉Ï̦̓̈ͦ̈̈̊̈Ṉ̈̈ ̷̈̈R̈̈ͣ̈͜Ü̙̹͖̍̈̈̈̈B̥̯̈̈̈̈̚Ÿ͎̱̈̈ͫ̈ ͖͚̈̈͌̈̈̈ͭ͜Ï̳͇̋̈̈̈́̈̈̄S̰̱͚̈̈̈̈̈ͬ͞ ̈̾̈S̡̝̩̈̈̿̈͊̈̈Ï̛̃̈̈M̴̈̀̈ͣ̈̈̈ͅP̈̾̈̈͗̈̈͝ͅL̈̈́̈̒̈Ÿ̷́̈̈ ̈̈̈N̠̪̈̈̈Ö̵̈̈̔̈͟T̈ͧ̈͗̈ͬ̈
For what it's worth, I have processed XML in PHP, Ruby, and Saxon/XSLT 2,
but I feel like I'm missing some sort of inside joke here.
Thanks for the info. To clarify, I don't develop in java, but deploy
well-established java-based apps in Tomcat, like Solr and eXist (and am
looking into a java
On May 8, 2012, at 2:01 PM, Ethan Gruber wrote:
For what it's worth, I have processed XML in PHP, Ruby, and Saxon/XSLT 2,
So then explain why LAMP/Rails aren't really options.
It's hard to see how anybody can recommend node.js (or any other stack) based
on this statement because without
I once had benchmarks comparing XML processing with Saxon/XSLT2 vs hpricot
and nokogiri, and Saxon is the most efficient XML processor there is. I
don't have that data any more though, but that's why I'm not a proponent of
using PHP/Ruby for delivering and manipulating XML content. Each platform
On May 8, 2012, at 2:30 PM, Ethan Gruber wrote:
I once had benchmarks comparing XML processing with Saxon/XSLT2 vs hpricot
and nokogiri, and Saxon is the most efficient XML processor there is. I
don't have that data any more though, but that's why I'm not a proponent of
using PHP/Ruby for
On May 8, 2012, at 2:18 PM, Ross Singer wrote:
On May 8, 2012, at 2:01 PM, Ethan Gruber wrote:
[trimmed]
Thanks for the info. To clarify, I don't develop in java, but deploy
well-established java-based apps in Tomcat, like Solr and eXist (and am
looking into a java triplestore to run in
I was
told by the project manager that Apache, Java, and Tomcat were showing
signs of age.
-- Taking this statement at face value, and taking it to its logical end
(that you'll have to migrate your application), I'm extremely doubtful
that Apache, Java, and Tomcat are so near their ends of
(and am
looking into a java triplestore to run in Tomcat)
-- I don't know if the parenthetical was simply a statement or a
solicitation - apologies if it was the former.
Take a look at Mulgara. Drops right into Tomcat.
http://mulgara.org/
--Kevin
On 05/08/2012 02:01 PM, Ethan Gruber
The 4-8 week deadline is more self-imposed than anything. The plan is (or
was) to deploy the new version of this project by mid-late summer. It is
already under way, with a working prototype, and I can probably mostly
finish it in 80-120 hours of solid work. I want to deploy it as soon as we
On Mon, May 7, 2012 at 11:17 PM, Ethan Gruber ewg4x...@gmail.com wrote:
It was recently suggested to me that a project I am working on may adopt
node.js for its architecture (well, be completely re-written for node.js).
I don't know anything about node.js, and have only heard of it in some
I've been using NodeJS in a few side projects lately, and have come to
like it quite a bit for certain types of applications: specifically
applications that need to do a lot of I/O in memory constrained
environments. A recent one is Wikitweets [1] which provides a real
time view of tweets on
29 matches
Mail list logo
