The BrainPort Vision Device
science.howstuffworks.com2 pointsby calambrac1 comments
try:
remote_resource.start_transaction()
#dostuff
remote_resource.commit()
except e:
remote_resource.rollback()
How do you do the same thing when modifying a local variable? You might try making a copy, modifying that, and then assigning back, but that's boilerplate, and it's easy to get wrong. Worlds are a more primitive mechanism that would be baked into a language, such that building a generic transaction api for local actions on top of worlds would be trivial. The fact that it could look exactly like the transaction api that you currently know and love for remote resources is a feature.
Where in my comment did I describe Worlds in a limited way? I just gave one small example of one possible application of them, in reply to a comment specifically about their relationship to transactions.