Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W Waarp Gateway
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 48
    • Issues 48
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Applications
  • Waarp Gateway
  • Waarp Gateway
  • Issues
  • #194
Closed
Open
Issue created Sep 08, 2020 by Paolo Pantellini@paolo.pantelliniMaintainer

Reorganize the transfer pipeline

Currently, client transfers are handled by the executor package. However, this is a problem. Not only does the existence of the executor package add quite a bit of complexity (when combined with the pipeline package), it also creates inconsistency between client & server transfers (since executor is exclusive to client transfers). The executor should be removed, and its code should be moved inside the transfer pipeline.

TransferStream should also be reworked so that it only handles data operation, while the rest should be handled by TransferPipeline.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking