4 Matching Annotations
  1. Aug 2022
  2. eprint.iacr.org eprint.iacr.org
    1007.pdf
    1
    1. cranium_arboretum 11 Aug 2022
      Reentrancy

      the fallback mechanism may allow an attacker to re-enter the caller function

      The DAO atomicity sequentiality invocation loops solidity
    Visit annotations in context

    Tags

    Annotators

    URL

    eprint.iacr.org/2016/1007.pdf
  3. Feb 2021
  4. oozou.com oozou.com
    Introducing ActiveForm for Ruby on Rails | OOZOU
    2
    1. TylerRick 16 Feb 2021
      However, sometimes actions can't be rolled back and it is unfortunately unavoidable. For example, consider when we send emails during the call to process. If we send before saving a record and that record fails to save what do we do? We can't unsend that email.
      illustrating problem transactions (in context other than database) atomicity of operations (all or nothing; transaction) irreversible side effects
    2. TylerRick 16 Feb 2021
      I typically save everything I can first, and then call the side-effects afterwards. If the side-effects fail I can handle them elsewhere and retry when necessary.
      atomicity of operations (all or nothing; transaction) good solution side effects irreversible
    Visit annotations in context

    Tags

    Annotators

    URL

    oozou.com/blog/introducing-activeform-for-ruby-on-rails-50
  5. Jun 2020
  6. proandroiddev.com proandroiddev.com
    Working with Firestore: Building a simple database model
    1
    1. kip2 18 Jun 2020
      Cloud Functions working on the server or WriteBatches working on the client
      cloud-functions write-batches atomicity
    Visit annotations in context

    Tags

    Annotators

    URL

    proandroiddev.com/working-with-firestore-building-a-simple-database-model-79a5ce2692cb