[
https://issues.apache.org/jira/browse/OODT-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001602#comment-13001602
]
Chris A. Mattmann commented on OODT-150:
----------------------------------------
bq. the mime-type is based on the data-file, i need mime-type based on the
checksum file (i sometimes get different checksum files for the same data-type
from the same provider – so attaching a checksum to a data-type mime-type is
not gonna cut it in my case)
I'm sorry I don't get what this means. Can you provide an example?
bq. an xml-rpc connect takes just as long as or longer md5 checksum . . . aside
from waiting for resources and all the other complications this would introduce
Again rather than make claims I'd like to see some true benchmarks.
bq. changing names and paths takes like a few secs of grep replacements (and
the names of the actions are pretty generic – PGPChecksum and MD5Checksum . . .
and they expect the checksum to exist in a file which is created by MD5 or PGP
with a given configurable extension)
Great, if you would have done that back then, we could probably have kept them
around, but it didn't happen.
bq. This would be in another JIRA issue i presume?
Yeah maybe after some more discussion and/or thought on it...
> ToggleAction addition to crawler
> --------------------------------
>
> Key: OODT-150
> URL: https://issues.apache.org/jira/browse/OODT-150
> Project: OODT
> Issue Type: New Feature
> Components: crawler
> Affects Versions: 0.2
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.3
>
> Attachments: crawler.OODT-150.2011-03-01.patch.txt
>
>
> Allows for cases where there are one of two (or more) actions which needs to
> run. For example: sometimes the same file types have different checksum files
> associated with it, this allows for either case.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
