yeah, and I will use that
Once I’ve finished dicking around, I’ll defo blog about the various bits I used and if I feel enthused I’ll write a node client properly
Not that you need much of a client for this
also i bet it uses hard drive to cache urls 
actually doing a native tcp client could be very interesting and would fit well with node (fully async)
That would have more value than doing the http one which is basically a wrapper around the ‘http’ library
Implementing a native TCP client as a native nodejs stream would be nice
the protocol is just protobufs & async tcp… ill look at it next week
Btw, my little Github dashboard is looking quite snazzy, should be a good few blog entries coming out of this
link??
Not published anywhere, I need to build mono onto my AWS box
I guess a preferred way of sticking projections etc in source control will be to have a script that simple does a load of POSTS from a directory
yep curl works for this…
Thanks for the informative series of posts. It’s really filling in some holes in the docs. Looking forward to some blog posts. 
more docs coming next week as well. also common domain (jo) hookups…
The order of atom feed pages is correct. There are some issues, however, with how next page link is generated.