877 karma · joined July 2, 2008
---
[ my public key: https://keybase.io/kevburnsjr; my proof: https://keybase.io/kevburnsjr/sigs/Auz3fOc8DmsCkYsNlqr-jtplnjhLyIdJZxjMEJufkOQ ]
Do you have just 1 varnish instance or two?
I never did fully solve the ban propagation problem when running multiple redundant varnish instances.
Also there are a number of framework features you can't use with HPHP, like autoloaders.
http://programming.com/static/img/bg.jpg
This website can go fuck itself.
You will probably not be offered this position any way except through the recruiter.
My advice is to continue your search, and only work with embedded recruiters who are paid hourly or salary for their services. These recruiters will have corporate email addresses matching the companies they represent.
I think you may have misunderstood your source. Subjective truth is only half of the equation. The other half is testing rational models against experience. If you understand the constraints of REST, you understand that it has implications not met by the API in question and thus claims to be something which it clearly is not.
Just because I tell you I'm a duck doesn't mean I'm a duck.
I would add that you must first have a deep understanding of the constraints and their associated benefits in order to make those types of informed decisions about your system's architecture. In my experience, the constraints are so orthogonal that a great number of the benefits of a system created using the REST architectural style only become evident in the overlap as the constraints empower each other.
Combining these constraints can elicit new benefits.
http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...
You do know that PHP has built-in min and max functions, right?
And array_map.
And array_walk.
And array_filter.
And array_reduce.
And array_slice.
And array_unique.
And array_search.
And range.
And empty.
And is_object.
And is_array. 0 domain specific media types (application/json)
1 domain specific media type (application/vnd.github+json)
many domain specific media types (application/vnd.github-issue.text+json, ...)
GitHub's v3 API uses the latter.See chapter 1 http://www.ics.uci.edu/~fielding/pubs/dissertation/software_...
Let's do some math.
Say your machine draws 250 Watts (~2 Amps). That's 6 KilowattHours(kwh) per day.
The US. national average for electricity is $0.112/kwh (as high as $0.31 in Hawaii) http://www.eia.gov/cneaf/electricity/epm/table5_6_a.html
Electricity for your machine will cost 6 * $0.112 = $0.67/day (on average)
That's $245.28/yr
These days you can get integrated Atom boards with up to 8 SATA ports.
Less power, less heat, less space. http://www.mini-itx.com/store/?c=2
/buckets/loot/index/category_bin,armor/price_int,300,500
Looks a lot like link walk syntax, don't it?1) If you want to be pedantic about HTTP, RFC 2616 states with respect to responses from URIs containing query strings that "caches MUST NOT treat responses to such URIs as fresh unless the server provides an explicit expiration time." Although this clause is broadly ignored by the vast majority of middleware, it could be argued that slashes are more correct. http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13...
2) Middleware like Squid comes with strip_query_terms on by default so if you put Squid in front of a Riak cluster and you wanted to see what was actually being run you'd have to make changes to the config file. Otherwise the request uri in the logs just reads "/buckets/loot/index?"
Add Education (None,HighS,BS,MS,PhD) as a research statistic and compare it to the national average. I would bet that your sample is greater than 2 Standard Deviations from the mean.
Enclosed is the invoice for our audit of your security systems [...]
4 hours of man power: $40.00
Network auditing: $35.00
Web-app auditing: $35.00
Network infiltration*: $0.00
Password and SQL dumping**: $200.00
Decryption of data***: $0.00
Media and press****: $0.00
Total bill: $310.00In fact dynamic resources can be served as well using the stale-if-error Cache-Control header. http://tools.ietf.org/html/rfc5861#section-4