Skip to content
Snippets Groups Projects
Select Git revision
  • 673d7fa0c37e929eeef9a9411a556865468819ec
  • master default
  • replace_gradle_witness
  • fix_nonlocalized_timestamp
  • fileStorage
  • implement-chunking
  • upgrade_roboletric_to_401
  • implement-mailbox-contact-sessions
  • 541-faster-retransmission-eta
  • add_special_purpose_contacts
  • mailbox-b
  • mailbox
  • mailbox-jd
  • implement_mailbox_connection_manager
  • 1343-vanniktech-emoji
  • 541-allow-retransmission-if-faster
  • asp-temp
  • fix_performance_test_db
  • 514-allow-retransmissions-using-lower-latency-transports
  • implement-SyncSession-writer-error-handling
  • add_special_purpose_contacts_refactored
  • beta-0.16.16
  • beta-0.16.10
  • beta-0.16.11
  • beta-0.16.12
  • beta-0.16.13
  • beta-0.16.14
  • beta-0.16.15
  • beta-0.16.9
  • beta-0.16.1
  • beta-0.16.2
  • beta-0.16.3
  • beta-0.16.4
  • beta-0.16.5
  • beta-0.16.6
  • beta-0.16.7
  • beta-0.16.8
37 results

briar-core

  • Clone with SSH
  • Clone with HTTPS
  • Forked from briar / briar
    6518 commits behind the upstream repository.
    user avatar
    akwizgran authored
    CryptoExecutor and DatabaseExecutor now use bounded thread pools with
    unbounded queues, since running too many tasks in parallel is likely to
    harm performance; IncomingConnectionExecutor, PluginExecutor and
    ReliabilityExecutor use unbounded thread pools with direct handoff,
    since their tasks may run indefinitely. There are no longer any bounded
    executors, and all executors discard tasks when shutting down, which
    fixes issue #3612189.
    
    Responsibility for starting and stopping services has been moved from
    BriarService in briar-android to LifecycleManagerImpl in briar-core.
    However, BriarService is still responsible for stopping the
    Android-specific executors, which is ugly. It would be better if
    executors registered themselves with LifecycleManager.
    673d7fa0
    History