[jira] Commented: (TS-70) CacheProcessor::open_read etc should take an options/mode word with flags for flexibility and expandability

["John Plevyak (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787000#action_12787000 ] 

John Plevyak commented on TS-70:
--------------------------------

The Cache should probably take a flag CACHE_OPT_READ_FROM_WRITER to enable that feature
for non-HTTP protocols as the feature puts the onus on the writers for the protocol to continue writing
even if their reader aborts the transaction (e.g. for a proxy situation).

> CacheProcessor::open_read etc should take an options/mode word with flags for flexibility and expandability
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: TS-70
>                 URL: https://issues.apache.org/jira/browse/TS-70
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Cache
>            Reporter: John Plevyak
>            Assignee: John Plevyak
>            Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Currently the CacheProcessor uses a number of boolean arguments with open_read open_write etc..
> This set changes as protocols and features change and will change with pluggable, stackable caching.
> In order to be more flexible and allow for expanding these options without changing the interface
> we should probably adopt a clib style options/mode word with bit field flags.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.