The biggest problem I can see, as with all proximity devices, is spoofing. How do I know the item listed as "Bus Stop" is actually the bus stop, and not someone's malicious Raspberry Pi hidden in the bush next to it?
545 karma · joined February 6, 2012
The biggest problem I can see, as with all proximity devices, is spoofing. How do I know the item listed as "Bus Stop" is actually the bus stop, and not someone's malicious Raspberry Pi hidden in the bush next to it?
[1] http://www.freebase.com/query?lang=%2Flang%2Fen&q=[{%22id%22...
[1]: https://github.com/rails/rails/blob/master/guides/source/sec... [2]: https://github.com/rails/rails/commit/2a290f7f7cdf775491eda0...
The EU decided to take action by mandating that companies make it visible when this was happening, in the Directive on Privacy and Electronic Communications[1].
Since it's technically impossible to allow the benefits of cookies without opening privacy holes, I don't really know what else privacy campaigners were hoping to achieve.
[1]: http://en.wikipedia.org/wiki/Directive_on_Privacy_and_Electr...
//text()[contains(.,'Dull needles')]EDIT: To clarify, a framework like Rails definitely has a place for including a web server.
Now Ruby has a lightweight web servers in its standard library (but not its core library). Maybe the problem people are seeing with the web server (and it's not a new problem) is the way PHP's core library contains so many things that other languages would leave out as optional includes.
[1]: http://en.wikipedia.org/wiki/Betteridge%27s_law_of_headlines
And any interview technique that involves the candidate actually working on production code it criticised for being exploitative and effectively slavery.
This is exactly what Rails offers by default, actually. Although you (can) declare your code using a `wants.csv { … }` format, it's mapped to both the extension and the corresponding Accepts MIME type. (with the Accepts header taking precedence over the extension, I believe)