[
https://issues.apache.org/jira/browse/OODT-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Foster updated OODT-178:
------------------------------
Attachment: Pushpull2.pdf
Attached new design proposal for Pushpull... comments welcome... let me know if
there is anything that is unclear... i've put description of components which i
felt need some more information than just a diagram:
DownloadJob - is a file downloader which is responsible for downloading a given
file. However, i may possibly introduce the feature of being able to batch file
downloads together if there is a list of files from the same site which are
scheduled to be downloaded.
CrawlerJob - is a site crawler which finds files which should be downloaded.
HistoryStore - keeps track of file based information such as: has a given file
been downloaded already.
ProtocolManager - responsible to determining a protocol for the a given file on
a given site, so that the protocol can be given to the DownloadJob.
ResourceJobRunner - a JobRunner which ships its jobs out to CAS-Resource
JobScheduler - responsible for sending out scheduled jobs to its JobRunner. It
uses information from its SiteManager for things such as restricting the number
of connections made to a given site at any one moment.
> Distributed-Pushpull -- allow for file downloads be cas-resoure manager jobs
> ----------------------------------------------------------------------------
>
> Key: OODT-178
> URL: https://issues.apache.org/jira/browse/OODT-178
> Project: OODT
> Issue Type: New Feature
> Components: push pull framework
> Affects Versions: 0.2
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.4
>
> Attachments: Pushpull2.pdf
>
>
> This will entail making the FileRetrievalSystem an abstract class or
> introduction of some kinda of Protocol (Design Pattern Protocol -- not
> pushpull Protocol) interface which will allow the execution of a file
> download to be handled by a custom implementation
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
