Ce site web est une partie intégrante de l’exposition Perspectives de vie à Londres et à Tokyo

Well, most of the work is done by Earthdesk and GeekTool 3.

Earthdesk is set to Natural Color, Equirectangular projection, Natural Color, Real Moonlight, centered on Vienna, Background: Starfield. Zoom 80%, Clouds 80%, Brightness 80%.

In GeekTool, the times and the weathers are all separate Shell "geeklets".

Times are generated by running shell commands like

env TZ=Asia/Tokyo date " %l:%M %p"

every 20 seconds

The weather is the tricky part. The way I am doing it now, if I am not careful, gets me throttled for too many concurrent requests to the wunderground.com API server. It also fails badly if I am disconnected, so I will need to do it differently.

FWIW: I have a PHP script which I run as separate Shell Geeklets. I invoke it with the name of the city I want. It then hits wunderground and gets back an XML stream of the local weather, which I parse, format and echo. (the way I'd change this is run the script from cron, with a 30 second wait between requests, and cache the results locally, which I would then call from the Shell Geeklets)

From there it's just a question of setting fonts, sizes, colors and moving the little Geeklet boxes around as you want them.

K. abasourdie quand je lui dis être allé ainsi à pieds de Nakano à Asagaya, ce qui n’a rien d’un exploit pour qui marcher est aussi important que la lecture, ou la prière. La prière plus que la lecture, mais sans formule. Réciter le présent.

A couple of good things to remember here: #1 resolving 1 bottleneck can open another bottleneck that is much worse. #2 is to understand that not all API’s are created equal. Additionally the configuration and setup that works well on one system may not work well on another. Because of this people often leave lots of performance on the table. Don’t just trust that your current API or config is optimal, test and make sure it fits your application.

What, a performance regression? But we threw more memory at it!! How can that be!

Memcached is not a cure all.

Tokyo Cabinet is a key/value database meant to be the successor of {G,Q}DBM.

introductory talk on Tokyo Cabinet, Tokyo Tyrant, pytc, and PyTyrant

Tokyo Cabinet is a library of routines for managing a database. The database is a simple data file containing records, each is a pair of a key and a value. Every key and value is serial bytes with variable length. Both binary data and character string can be used as a key and a value. There is neither concept of data tables nor data types. Records are organized in hash table, B tree, or fixed-length array.

Commuters in Tokyo are being greeted with the friendliest of welcomes.

In a 2009 survey of 1,154 high school girls, by the Culture Studies Institute in Tokyo, hostessing ranked No. 12 out of the 40 most popular professions, ahead of public servant (18) and nurse (22).

Tokyo Tyrant is a package of network interface to the DBM called Tokyo Cabinet. Though the DBM has high performance, you might bother in case that multiple processes share the same database, or remote processes access the database. Thus, Tokyo Tyrant is provided for concurrent and remote connections to Tokyo Cabinet. It is composed of the server process managing a database and its access library for client applications.

je descend à la station suivante, Nishi-Sugamo, contrée inconnue, et vallonnée, d’autant plus qu’en allant vers l’est à la recherche approximative de la résidence Kyû-Furukawa-Teien et son jardin. Absolument éviter les grandes artères, et ce groupe de marcheurs en tenue de sérieuse randonnée qui fait la tournée des temples visiblement nombreux.