1. fdsgfds
2. Transfer Queue
2.1. Messaging implementation
2.2. Mock implementations
2.2.1. for testing
2.2.2. before MQ era
2.3. Database implementation - do we need it?
3. Database access
3.1. Generic database interface
3.1.1. Generic "schema"
3.1.1.1. Configuration schema
3.1.1.2. We need to identify it
3.1.1.3. Transfer job schema
3.1.1.4. Job queue schema?
3.1.1.5. Objects
3.1.2. Queries
3.1.2.1. Methods
3.2. Oracle plugin
3.2.1. Implement the queries
4. Configuration
4.1. Admin CLI
4.2. Config. data in database
4.3. Config service
4.3.1. Also web service
5. Transfer execution
5.1. Logic is the same like in old FTS
5.2. Transfer-url-copy overlaps with lcg-cp
5.2.1. merge
5.2.2. Use from lcg_util
5.2.3. We have transfer plugins immediately
5.2.3.1. HTTP, xroot: both GFAL and FTS benefits in the same time
5.3. Good task for a student - Adrien?
6. Monitoring, logging
6.1. Same logger for bot GFAL and LCG_Util?
6.2. Monitoring messages in FTS 2.2.8 - same in FTS3.
7. Transfer scheduling
8. Transfer submission
8.1. web service
8.1.1. receives transfer requests
8.1.2. adds it to the transfer queue
8.2. Transfer CLI
8.2.1. Reuse existing one
8.2.1.1. Refactor if needed
8.3. Which technology do we use?
8.3.1. Apache Axis
8.3.1.1. Looks more stable
8.3.1.2. More maintainable
8.3.1.3. More work..
8.3.1.4. Better HTTPS, etc
8.3.2. gsoap
8.3.2.1. We use it now
8.3.2.2. cgsi-gsoap plugin ready
8.3.2.3. Less stable
8.3.2.4. Generated API is ugly