It has an excellent pedigree – one of the main developers is Daniel J. Bernstein, who has a very enviable record of making robust software.
This is akin to memcached, but better (of course)
- data is idempotent/nonmutable – keys always have one specific value for all time
- has cache-filling mechanism so peers cooperate so only one does a load of missing data
- mirroring of popular data to multiple caches
- client library as well as standalone server
Only in Go unless someone ports it.
Google changed dl.google.com to be a Go server.
Visual Studio 2008 included support for
according to http://msdn.microsoft.com/en-us/library/bb982198(v=vs.90).aspx. In 2008 (VC9 compiler), this was in std::tr1, but as of 2010 (VC10 compiler), this moved to std (since it was approved).
XCode 4 has both GCC and LLVM (Clang) toolchains. LLVM uses the libc++ library, which has these in std. GCC uses libstdc++, which has these in std::tr1.
In terms of what’s supported, it seems like there is full TR1 support.
For C++11, there’s this blog post about how to build a libc++ that works on Mac OS X 10.6: http://thejohnfreeman.com/blog/2012/11/07/building-libcxx-on-mac-osx-10.6.html, and also this: http://stackoverflow.com/questions/14494513/how-do-i-get-back-c0x-c11-support-for-mac-os-x-10-6-deployment-using-xcode-4, and this makes it seem unlikely to work in reality: http://clang-developers.42468.n3.nabble.com/clang-libc-libc-ABI-amp-MacOSX-10-6-td4029112.html.
What would be ideal is not statically linking, but including a dylib for libc++ just on Mac OS 10.6 deploys.
GCC 4.2 uses std::tr1. GCC 4.8 uses std.