From what I can figure out, Auto-Save and Versions are pretty-much built-in. Assuming an application that uses standard Cocoa approaches to document management, it just needs to declare its support for the auto-save functionality, and pretty much everything else will be handled by the system libraries. Fairly trivial.
Resume is more involved, however: the application is responsible for (de)serializing its state. Again, for a document-based application that doesn't stray far from the "recommended" path, it should be fairly simple to implement. It's just a matter of the document and UI being auto-saved on termination, which requires little work from the developer. One very interesting side-effect of the Resume feature is that it removes the need for applications to stay running: the system can silently terminate unused applications, and bring them back if they're needed again. What's really exciting about this, is that it's turning applications into something that is "always there".
I'm not so sure. I tried to get a free Android device to see if Android is an interesting platform to develop for, but couldn't find anyone that could get one for me (and I'm not ready to sign a 2-year contract just for an experiment :)).
Seems a reasonable strategy to me if you have plenty of money but are short on time. Probably the largest barrier to having university students play with the platform is the cost of the hardware.
For what it's worth, I took just one look at the front page and it told me pretty well what the product is. But then, I've spent years working in this exact field, so it might be a case of a blurb aimed at those in the know.
Actually, he only needs a visa to enter the country. The Geneva Convention allows anyone to present at a border post and claim refugee protection (with a few exceptions, but visas aren't included in those).
There are various laws that require careers to prevent people without visas arriving at borders, but those are aimed at making it harder to ask for protection. He managed to work around those; mission accomplished.
You seem to be wording your reply as if you're somehow disagreeing with what I posted, and you've gotten the corresponding upvotes.
-He needs to set foot on actual Canadian soil to claim refugee status
-He can't walk to the border. He needs to make use of a boat or a plane
-Air carriers enforce requirements on behalf of the countries they fly to, like "you need a visa to go to Canada if you're Chinese". This is because countries like Canada like the concept of refugee protections more than the actual practice of them: they want to put barriers up to stop people from actually claiming it.
Bit of a conundrum there, no?
-So he used the ID of someone who wouldn't need a visa/passport, along with the mask, to essentially get past the barrier that the air carrier would not have brought him to Canada otherwise.
The original person claimed, wrongly, that " And he didn't even use it to try and get into Canada, just out of HK.", yet he used the mask to get into Canada by way of getting on an air carrier that wouldn't have let him on otherwise, at which point he was assured entry to Canada and consideration via the refugee program.
You are right. He needed a visa to get on the flight. However, my understanding of the refugee stuff is that one doesn't actually need to enter the country. You're not inside the country till after the border guard has waved you through; but you can still ask for protection while at the border. He's probably still in detention, which doesn't really count as being in the country in my book. He used the mask to try and get protection, not simply enter Canada. Very different motive.
This is descending into analty, so I'll stop now :)
His assertion is actually backed up by MongoDB docs: "Sharding will be production-ready in MongoDB v1.6, estimated to be released in July 2010." Their current sharding alpha is only tested/supported for small clusters (up to 20 nodes). In addition, looking at their sharding mode of operations, only a very limited set of actions are properly sharded; the rest require touching all the shards.
Disclaimer: this was the first look I've had at MongoDB. However, based on this alone, it would be prudent to wait several years before considering using this technology in serious production. It is somewhat reckless to consider a DBMS feature that wasn't locked for awhile "production-ready".
By the way, this article first appeared in a recent Something Awful thread. It is very long but has heaps of information for anyone interested in highway design.
There is a very simple solution: pass a law that automatically absolves customers of any fraud, and places burden of proof on the banks. Transactions reported fraudulent should be automatically reversed, unless the bank can provide proof (satisfying the standards expected in civil courts) that the customer was at fault.
As an example, this was largely the case with transactions not involving PINs (signed-for purchases). Recent introduction of EMV (chip-and-pin cards) was really done to shift responsibility for such transactions back onto the customers and reduce banks' losses.
This is also the case with stolen cards (in the UK and Ireland, at least): losses related to such cases are covered by the bank, even for losses occurring before the card was reported stolen. This is the reason banks implement various pattern-matching techniques to try and detect such transactions as soon as possible.
I've noticed some newer ATMs around these parts started doing that as well. However, is is of absolutely no use without associated customer education. The machines don't even say "here is what the slot should look like, please check it before entering your PIN." There were even reports of people calling the police thinking this security feature was a skimming device, since it looks so out of place and different from what's usually on the machines.
Resume is more involved, however: the application is responsible for (de)serializing its state. Again, for a document-based application that doesn't stray far from the "recommended" path, it should be fairly simple to implement. It's just a matter of the document and UI being auto-saved on termination, which requires little work from the developer. One very interesting side-effect of the Resume feature is that it removes the need for applications to stay running: the system can silently terminate unused applications, and bring them back if they're needed again. What's really exciting about this, is that it's turning applications into something that is "always there".