Skip to content
Snippets Groups Projects
Select Git revision
  • b2c12cfd4b1cc9925d667cd2b6bc1feaadb064d8
  • main default protected
  • release/1.1
  • encrypt_comments
  • mnemonic_dewif
  • authors_rules
  • 0.14
  • rtd
  • 1.2.1 protected
  • 1.2.0 protected
  • 1.1.1 protected
  • 1.1.0 protected
  • 1.0.0 protected
  • 1.0.0rc1 protected
  • 1.0.0rc0 protected
  • 1.0.0-rc protected
  • 0.62.0 protected
  • 0.61.0 protected
  • 0.60.1 protected
  • 0.58.1 protected
  • 0.60.0 protected
  • 0.58.0 protected
  • 0.57.0 protected
  • 0.56.0 protected
  • 0.55.1 protected
  • 0.55.0 protected
  • 0.54.3 protected
  • 0.54.2 protected
28 results

index.rst

Blame
  • requests.pu 738 B
    @startuml
    
    activate "Core Component"
    "Core Component" -> BmaAccess : Request data
    BmaAccess -> BmaAccess : Request cache
    ref over BmaAccess
        Data is obsolete
        (new block mined
        since last caching)
    end ref
    BmaAccess -> duniterpy : HTTP GET
    alt Rollback
    BmaAccess -> BmaAccess : Find last block number rollbacked
    ref over BmaAccess
        If the request is a bma/blockchain/Block, we check if the hash answered is the same
        as our hash, in which case, we know that the rollback didn't reset blocks before
        this one.
        Blocks from this one to the current block are considered obsolete
    end ref
    end
    BmaAccess -> BmaAccess : Update cache data
    
    "Core Component" <- BmaAccess : Return data data
    deactivate "Core Component"
    
    
    @enduml