[
https://issues.apache.org/jira/browse/DROIDS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974864#action_12974864
]
Otis Gospodnetic commented on DROIDS-110:
-----------------------------------------
The Fix Version/s, etc. for this issue should probably be changed to 0.0.1.
Doesn't seem like a graduation blocker.
> droids-norobots shouldn't have dependency on protocol implementation; it
> should be abstract Rules Engine
> --------------------------------------------------------------------------------------------------------
>
> Key: DROIDS-110
> URL: https://issues.apache.org/jira/browse/DROIDS-110
> Project: Droids
> Issue Type: Sub-task
> Components: core, norobots
> Affects Versions: Graduating from the Incubator
> Reporter: Fuad Efendi
> Fix For: Graduating from the Incubator
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> Naturally enforced by DROIDS-109 requirements.
> 1. Move NoRobotsClient.java from droids-norobots into droids-core
> 2. Move ContentLoader.java from droids-norobots into droids-core
> 3. Refactor ContentLoader, ContentEntity, ManagedContentEntity,
> AdvancedManagedContentEntity
> Having InputStream instead of byte[] doesn't seem right; and we need proper
> metadata.
> Even for FileProtocol.FileContentEntity, why should we expect unlimited
> terabytes of data and use InputStream instead of bytearray and proper
> encoding in case of text? Most "robots" exist because of "search", and most
> simply limit data to 64kb - 128kb (although Amazon.com have 300kb raw web
> pages in average)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
