[nodejs] express.io = express + socket.io

Hi all, I just released express.io, a realtime-web micro framework for nodejs. Express.io is a superset of express and socket.io, and it aims to unify the two frameworks in a lightweight high performance manner. It is a drop-in replacement for express. Check it out and give some feedback.

[nodejs] Re: express.io = express + socket.io

I plan on keeping up with the latest and greatest of both Express and Socket.io (3.0.4 and 0.9.13 currently). And with the great versioning capabilities of npm, this should be easy. The website is here: http://express-io.org The repo is here: http://github.com/techpines/express.io

[nodejs] Express.io - Live Realtime HTML5 Canvas Demo

I just made a live realtime canvas demo using express.io . It uses a hodge podge of cool nodejs and javascript technologies, and it's got code snippets and an explanation. Check it out! http://express-io.org/live -- Job Board: http://jobs.nodejs.org/ Posting guidelines:

[nodejs] Re: Express.io - Live Realtime HTML5 Canvas Demo

defined > > On Monday, January 14, 2013 1:01:14 AM UTC+1, Brad Carleton wrote: >> >> I just made a live realtime canvas demo using >> express.io<http://express-io.org> >> . >> >> It uses a hodge podge of cool nodejs and javascript technologies, and

[nodejs] Static Web Framework for Nodejs - Asset Rack

Static Web Framework for Node.js. Enjoy! http://asset-rack.org -- -- 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 t

Re: [nodejs] Re: what are the merits / demerits of require.extensions?

As an author of a couple of coffeescript projects in node, I agree the code that goes into npm should NOT be coffeescript. That being said when you are developing an application, adding an explicit build step is not fun. I mean I wouldn't want to see all the assembly or binary files that my j

Re: [nodejs] Re: what are the merits / demerits of require.extensions?

ourse, it's your computer, it's your application, you can do > whatever foolish thing you want. But if you're looking for my > blessing, then don't do foolish things. It would be irresponsible of > me to say this is OK when I know it isn't, since I see the fallo

Re: [nodejs] Re: what are the merits / demerits of require.extensions?

Cool, that makes sense. "require.extensions" = bad whatever userland wants to do = good (maybe) On Sunday, May 12, 2013 5:24:20 PM UTC-5, Mikeal Rogers wrote: > > > On May 12, 2013, at 3:20PM, Brad Carleton > > wrote: > > If I distribute all of my code as java

[nodejs] Re: devil's advocate: why would I choose nodejs over MVC + IIS?

>From a business perspective nodejs is cheaper. If you are building Internet services, you know that you will be paying for infrastructure, servers, storage, etc. You add another bundle of costs for software and licenses with .NET. That puts you at a big disadvantage. The number of major In

[nodejs] Re: Using Express and Less-Middleware in a Cloud Deployment

Shawn, not sure what you are doing wrong. There are some other asset management solutions out there, including connect-assets, it's on github. One thought might be that if it is a platform as a service cloud offering, then they might not let you write to disk. The less middleware might be try

[nodejs] Re: e-Commerce platform

Sorry to jump in with a me too, but I have been doing all of my nodejs and client side code in coffeescript, and I very much prefer it. I understand the pure javascript point of view, because to some degree it puts the burden on the pure javascript devs to learn coffeescript. Whereas, for a co

[nodejs] Re: A beginner looking for an Open Source Project to contribute

I've got one for you, asset-rack: https://github.com/techpines/asset-rack An asset management framework for nodejs. It gets dynamic assets, like coffeescript, less, and jade templates down to the browser without ever writing to disk. There is no build step, and it can also push assets to S3

Re: [nodejs] Re: coffeescript support in child process

@Nathan upfront compilation adds a significant amount of complexity to an app. The guys that work on Java apps sometimes have a team dedicated to the "build", which is just building/compiling the app. Everything should be just-in-time. This makes it an order of magnitude simpler to develop.

[nodejs] Async Error Handling and Domains

Currently, async error handling in node is difficult. I know that you guys are working hard on domains. Do domains solve some of the problems of async error handling and are they similar to an async try/ catch? There is currently not a lot of documentation, and I would love to get a better under

[nodejs] Re: Async Error Handling and Domains

request based concurrent systems like web apps. On Feb 10, 8:05 am, Ben Noordhuis wrote: > On Fri, Feb 10, 2012 at 05:59, Brad Carleton wrote: > > Currently, async error handling in node is difficult.  I know that you > > guys are working hard on domains.  Do domains solve some of t

[nodejs] Re: Async Error Handling and Domains

That sounds great! I really hope this is able to make it into 0.8. On Feb 10, 11:23 am, Ben Noordhuis wrote: > On Fri, Feb 10, 2012 at 16:42, Brad Carleton wrote: > > Very interesting, so could a domain cover an entire request in your > > typical web application.  Basically

[nodejs] Nodjs Performance - Concurrent Connections - Linux

I have been working on a project for a client involving building a nodejs cluster. I am trying to get a handle on what the performance characteristics of nodejs should be. I am running the latest stable node, 0.6.13 on Ubuntu 11.10. I am running tests on Amazon EC2 with an "m1.small" and a "c1.m

[nodejs] Re: Nodjs Performance - Concurrent Connections - Linux

Here's that table again it came out kind of weird in the original post. Request Number Response Time (ms) Server Time (ms) 696818 0 697818 0 698819

[nodejs] Re: Nodjs Performance - Concurrent Connections - Linux

ve if everything is working correctly? On Mar 25, 4:26 pm, mscdex wrote: > On Mar 25, 5:18 pm, Brad Carleton wrote: > > > So here at request number 699, you see the response time jump by about > > 2500ms.  The "response time" is what the load tester reads and the > > &q

[nodejs] Re: Nodjs Performance - Concurrent Connections - Linux

I forgot to throw that into the script, but I have it at 512. Yea, I need to give ab a whirl. I mean do you know any performance numbers that might be reasonable for a single node process. On Mar 25, 8:52 pm, mscdex wrote: > On Mar 25, 8:50 pm, Brad Carleton wrote: > > > Do you kn

[nodejs] Re: Version 0.7.8 (unstable)

Great work! I am excited about the new domains feature. I think domains will help simplify error handling in node. On Apr 18, 12:42 pm, Isaac Schlueter wrote: > 2012.04.18, Version 0.7.8, (unstable) > > * Upgrade V8 to 3.9.24.9 > > * Upgrade OpenSSL to 1.0.0f > > * Upgrade npm to 1.1.18 > > * Sh

[nodejs] unix: fix loop starvation under high network load (what was this?)

I was looking at this on the bullet points for the 0.6.19 release, and was wondering what this was? I have had issues with strange delays when doing large numbers of outbound requests from nodejs. I don't know if this has anything to do it with it or not though. -- Job Board: http://jobs.nodejs

[nodejs] What is Node.js doing to prevent another Heartbleed style bug in Node core or dependent libraries?

It's pretty much luck that most versions of Node seem to be unaffected by heartbleed. But what is being done or what can be done to prevent a similar vulnerability in the future? -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Pos