-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AsyncStageout component #311
Comments
metson: Hassen, is this still valid? I think all these changes went in to #95 or am I wrong? |
metson: ok, cool thanks Hassen! I'll bring my local repo up to sync with your changes and hopefully commit tonight. |
riahi: Perfect!...Thank you Hassen |
metson: This patch series looks good, and has been committed. I have a few questions:
1 & 2 aren't a big deal (but I'd like to clarify before moving on). 3-5 should probably be separate tickets. If you agree can you open them and add the numbers to this ticket? |
metson: in fact getFTServer could use a database in couch... maybe over complicated. |
metson: oh, and one last thing:
|
metson: (In 8920) Change main class name, add defaultProxy parameter to config, implement ftscp machinery, references #311 From: Simon simonmetson@googlemail.com |
riahi: I answer to your questions: 1- Yes, the TransferManager should be removed. Cheers |
metson: Ok, the other tickets are: Closing this one now. |
Agent written in WMAgent component style and implements the main machinery of the AsyncStageout (the implementation of this machninery is described in the Ticket #95). It is needed to merge this agent in the AsyncStageout module.
The text was updated successfully, but these errors were encountered: