Skip to content

Google Tech Talk – Node.js: JavaScript on the Server

YouTube – Node.js: JavaScript on the Server.


1,250,000,000 Key/Value Pairs in Redis 2.0.0-rc3 on a 32GB Machine « Jeremy Zawodny’s blog

1,250,000,000 Key/Value Pairs in Redis 2.0.0-rc3 on a 32GB Machine « Jeremy Zawodny’s blog.

This is encouraging, my pstore project, which is a haXe/Node.js object store uses  Redis as a backend. No worries about scalability here!

Ajaxian » Dojo 1.5 is Out and it’s Feature Packed!

Ajaxian » Dojo 1.5 is Out and it’s Feature Packed!.

I’m tweaking the haXe API generator now for 1.5.

The new claro theme does indeed look very pleasant

Yahoo Experiments with NodeJS

Multi-Core HTTP Server with NodeJS (Yahoo! Developer Network Blog).

and of course i had to mention haxe-node.js synergy here.

haXe Dojo API – First Stab

If you don’t know Dojo have a look here.

First stab Dojo Api. The current generated api in dojoApi dir. The api.json
file is straight from the Dojo SDK 1.4.3 in the util/docscripts dir.
Disclaimer: I haven’t actually used Dojo, but the api seemed like a nice fit
for haXe, in that it doesn’t use quite as much JS magic, as for example JQuery,
and is easier to write a generator for. What I really like is it’s comprehensive,
full widget set, jquery like selection, the works.

So, with Node.js on the server, and Dojo on the client, I’m saying haXe/JS is
starting to kick arse.

Apart from what’s missing!

I’ve only generated classlike objects. There’s a lot of stuff which is
marked without classlike true. The generator has two lists classLike and
typdefLike which can be added to, to add other stuff that’s required but
not parsed by default. classLike is anything that’s a constructor or used as a
subclass, typedefLike is anything that is already instantiated and you just
need a reference to e.g.

static var dojo:Dojo = untyped __js__(“dojo”);

I’ve only tried a few functions, I’ve still got to see how the whole thing
fits together. There are documentation and api mismatches, e.g. I found
NodeList.foreach has it’s second param optional but it’s listed in api.json as
required. There’s going to be lot’s of special cases, and the only way to find
them is to use it.
I shall be using this myself in the coming days/weeks/months for various management consoles for my game server and stuff like that so it should get a good workout.

I also took the opportunity to write the generator using Node.js as the runtime. So a couple of the new* functions (in bdog-stdhx) got a workout with this.

I reckon I’ll mothball the Google Closure wrappers in preference to this toolkit.

Finally, only for the brave, but there’s only one way to improve it and that’s with input.



tommedema’s NodeSQLiteHaxeWrapper at master – GitHub.

Tom Medema has just pushed haXe type signatures for Node.js.

Node.js Slides by Ryan

Slides (pdf)