Rich Hickey (of [Clojure][1] fame) has released a cloud-based database called [Datomic][2] that has some interesting properties.
Datomic is an log of assertions and retractions of "facts", much as a DVCS like [Git][3] is a log of code diffs. The state of the database at any one time is the sum of all the assertions and retractions up to that date.
| <anteaya> just one question | |
| <anteaya> That method will call GETorHEAD which in | |
| <anteaya> do you think it would look better if it was GET or HEAD | |
| <anteaya> rather that GETorHEAD as it is now? GETorHEAD looks like one message rather than two | |
| * lloydde (~lloydde@hq-r.pistoncloud.com) has joined #openstack-101 | |
| * torgomatic (~torgomati@meat.andcheese.org) has joined #openstack-101 | |
| * dolphm (~dolphm@cpe-67-10-140-29.satx.res.rr.com) has joined #openstack-101 | |
| <notmyname> anteaya: ok, pushed those fixes. also, GETorHEAD is correct (https://github.com/openstack/swift/blob/master/swift/proxy/controllers/obj.py#L328) | |
| <notmyname> GETs and HEADs, per the HTTP spec, are the same except for the existence of a response body, so they are implemented in swift as the same function (rather than duplicating the code) | |
| <anteaya> nice |
Step 1: From you logs I have decoded the bucket/key
binary_to_term(<<131,109,0,0,0,9,85,114,108,84,111,83,99,97,110>>).
<<"UrlToScan">>
binary_to_term(<<131,109,0,0,0,61,104,116,116,112,37,51,97,37,50,102,37,50,102,119,119,119,46,97,110,104,114,105,46,110,101,116,37,50,102,37,51,102,102,101,101,100,37,51,100,114,115,115,50,37,50,54,97,109,112,37,51,98,112,37,51,100,55,51,49,49,48>>).
<<"http%3a%2f%2fwww.anhri.net%2f%3ffeed%3drss2%26amp%3bp%3d73110">>
Step 2: Please run the below snippits from riak attach to identify the owning partitions of this bucket/key
#Express - Logging The express.js node.js web application framework comes with a built-in logging module called logger which is the connect.js logger. It is really handy to enable and you can use it just like any other Express module. app.use(express.logger());
Without any configuration, the logger middleware will generate a detailed log using what is called the default format. The logger actually supports four predefined log formats: default, short ,tiny, and dev. Each of these predefined formats show various amounts of detail. You can specify one of them this way:
app.use(express.logger('dev'));
If you prefer, you can customize the precise details to be logged using the the following options to format the output of the logger:
Note: total experiment and hack, looks nasty, could be awesome:
kitchen.local.yml into $HOME/.kitchen/config.ymlbrew install polipo, with Ubuntu: apt-get install polipo)polipo-start and polipo-console somewhere useful (perhaps $HOME/bin?)
This is an unofficial, uncomplete and (pretty sure) wrong documentation of the RESTful service which powers the League of Legends spectator mode.
This documentation is desgined to be community driven and should be extended by everyone. If you find things missing, add them please!
Riot's spectator mode works by requesting replay data via HTTP form a service. The data is split in chunks which usually contain about 30 seconds of gameplay. Additionally there are key frames which seem to contain more information then a single chunk. They seem to be used to support
I have spent quite a bit of time figuring out automounts of NFS shares in OS X...
Somewhere along the line, Apple decided allowing mounts directly into /Volumes should not be possible:
/etc/auto_master (see last line):
#
# Automounter master map
#
+auto_master # Use directory service