#protcol

actually no

you see in regards to the top of outfits the protocol is not strapless, and a halter has strapes right? Also the straps have to be at least an inch wide (to make sure the dress stays up!) so again that would be fine. 

Report: NHL to announce new concussion protcol

by Craig Hagerman 4m ago Sergei Belski-USA TODAY Sports / USA TODAY Sports The NHL is preparing to make some changes to its concussion protocol. Sportsnet’s Elliotte Friedman discussed the expected changes – that will be announced prior to the start of the regular season – during intermission of the World Cup exhibition game between the United States and Canada: They have hired four individuals…

So, then the big question for Bitcoin is, just as it was for the early [credit] card: where’s the beef?  In retrospect, it’s clear that there was a lot of beef in payment cards. They were “more than money” – they were really platforms for providing a lot of services to consumers and merchants. The original charge card inserted an intermediary that gave the merchant their money right away and allowed consumers to manage their finances better by not having to produce cash right away when they bought something. And say what you will about the credit cards, but they made it a lot easier for consumers to get bank loans. And they continue to finance a lot of small businesses.  Supporters of bitcoin – and this includes most of the venture capitalists – say, in my words, not theirs, “it’s the protocol, dummy.” 

Yesterday I did a post on the idea that Redis now needs a binary protocol. Seems like people are listening actively and I was followed up with a reply (which I am not ready to believe) in this post saying:

We actually found at Tumblr that the memcache binary protocol was less performant than the text protocol. I also know a number of other large web properties that use the memcache text protocol. I don’t think the ‘benefits’ of a binary protocol are super clear cut for applications like this.

There is just so much in my head as an argument ranging from lesser number of bytes (imaging reading 4 byte plain integer versus reading string '6599384' and then parsing it to 4 bytes) to really simple jump tables for executing the operation. Then I thought let the evidence speak for itself and wrote some Go code available in this Gist to simply benchmark 100K, and 1M get operations (also tried various numbers various machines). For testing purposes I used Go ; with various reason like saving myself from complex configurations, avoid any VMs, simulate the complete client library written in purely in same language Go in this case (assuming the implementations were decent enough) and get the coding part done really quick.

It's a really simple benchmark always getting same key (to remove any other variables) and simply discarding the results trying to benchmark pure get/parse time. Results were just what I expected; with 100K gets took 6.560225s in ASCII protocol and 5.288102s in binary protocol. As I scaled the number of gets up to 1M the time grew linearly (see gist).