Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S syncevolution
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 168
    • Issues 168
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SyncEvolution
  • syncevolution
  • Issues
  • #140
Closed
Open
Created Dec 12, 2013 by Bugzilla Migration User@bugzilla-migration

parallel sync sessions

Submitted by Patrick Ohly @pohly

Assigned to SyncEvolution Community

Link to original bug (#72636)

Description

At the moment, syncevo-dbus-server serializes all sessions. This ensures that config changes do not overlap with sync sessions using these configs and that no local database or remote peer get sync with concurrently.

However, this slows down syncing with different peers in cases where these sync configs are truely independent.

syncevo-dbus-server needs to be enhanced to detect "safe" concurrency and allow that. Output handling in syncevolution command line might have to be updated, too. For example, what should --monitor show? All running sessions? The output of everything else should better be just for the initiated session.

Version: 1.4

Assignee
Assign to
Time tracking