PUBLIC MARKS with search finally

# A scalable threaded asynchronous state machine model. On a typical setup, 2 or 3 threads per core is enough to drive a large amount of traffic.

# Feature-rich HTTP/1.0 and HTTP/1.1 support. We fair well in various tests like CoAdvisor.

# Plugin architecture, making it easy (well, easier) to extend and customize your server.

# Well documented.

you said: “Especially given the by-now-clichéd recognition that we’ve decisively become an urban species”

It is indeed very interesting to think about urban systems design given there was a major move toward cities. That said I have the feeling that this move comes with, at least, three issues:

1. access to the “thought” urban environment,

2. the space left where 50% of the population is still living,

3. the space of this growth

There are many areas in the world where the growth of the cities is made by people without access or a limited access to the thought urban environment. Poor people living in slums or just in a space which is not part of the work of urban planner per say. In a recent exhibition about slums I went, it was very interesting to see that the organic structure of the slums was making possible for the individuals to create a rich and meaningful space, driving sometimes to less criminality than more traditional areas of the city. The slum is a forced collective creative space for survival.

The rest of the population, the 50% living in deserted areas are the forgotten of this story. It’s indeed more “fun”, interesting for researchers, sociologists to observe and think about the density in urban space (richness of interactions) more than the low level of activities in the “countryside”. Though there are equal challenges there in terms of design and space organization, access to services, etc.

Finally, is it really cities which are growing? What we call urban space often relates to the city center, but I have the feeling that the growth is happening in the in-between space (suburbs), which is again a complete disaster in terms of design, even more so in rich countries. The private space is becoming a space of non-creativity, dead areas of non activities. Someone, who wants to start a small business in between two buildings on the grass of a random suburb of a rich city, will not last for very long. Complete different dynamic than the slum where unregulated areas give the opportunity of creative solutions for surviving or living.

In this book, we'll be using the freely available IBuySpy Portal as a starting point for our intranet development. We'll look at both why we are modifying an existing intranet application rather than creating our own, and why we choose the IBuySpy Portal in particular. Once we have covered the basics, we'll take a tour of its features, looking at the files and types it consists of, how they function and fit together, and general principles behind the site. Finally, we'll take a brief look at how security is handled.

Presentation is everything in Japan. Go to any department store and buy even a small sack of tea, and the time and effort put into packing up your purchase is enough to astound any n00b Westerner. This tradition goes way back, of course. First published in 1967 and long out of print, this picture-heavy book of classic Japanese packaging has finally been reprinted in paperback. The title is misleading. There are no step-by-step directions, only black and white images up front with annotations in the back, detailing the materials used, region, specific use/occasion/tradition surrounding each item.

In an effort to make the code useful to as many people as possible, we've split it into several packages:

* The main package (probably the thing you're looking for) is the publishing system, known as ebpub.

* Second, the packages ebdata and ebgeo contain Python modules for processing data and making maps.

* Third, the packages ebinternal and everyblock round out the code that powers EveryBlock.com. They're internal tools and are likely not of general use, but we're including them to be complete.

* Finally, ebblog and ebwiki are our blog and wiki software, respectively. Because, dammit, the world needs another Django-powered blogging tool.

I've been experimenting with some javascript classes that mimic the structure of mapnik's Layer/Style/Rule classes and render OSM data (via GeoJSON) to a <canvas> element. I've also finally taken a look at how github works, so I've decided to share the initial code there in case people are interested. If you don't want to check the code out for yourself there's a demo page here (tested in Firefox and Safari only, so far).

people rarely held on to money in the form of cash for any length of time, for the most part due to lack of access to banks and/or the high cost of maintaining an account proportionate to their incomes. Cash was rapidly converted to goods based on priorities and these 'goods' acted as insurance (silver), savings (buying building materials on a piecemeal basis as cashflow allowed until the house could be built), a cushion aka insurance (selling a pig for an emergency or eaten for food) and finally investment (milk bearing cow, young piglets to rear to maturity, etc).