[
https://issues.apache.org/jira/browse/DERBY-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660779#action_12660779
]
Kristian Waagan commented on DERBY-4002:
----------------------------------------
There is also org.apache.derby.iapi.services.io.StreamStorable which deals with
streams.
> Look at merging the interfaces PositionedStream and Resetable into one
> ----------------------------------------------------------------------
>
> Key: DERBY-4002
> URL: https://issues.apache.org/jira/browse/DERBY-4002
> Project: Derby
> Issue Type: Task
> Components: JDBC, Store
> Affects Versions: 10.5.0.0
> Reporter: Kristian Waagan
> Priority: Minor
>
> From DERBY-3935:
> "By the way, would it make sense at some point to merge the PositionedStream
> interface with Resetable? Or perhaps make PositionedStream extend Resetable?
> Resetable.resetStream() is just a special case of
> PositionedStream.reposition(), and it seems like both PositionStoreStream and
> LOBInputStream have methods that match the functionality defined by Resetable
> (PSS actually implements Resetable)."
> and
> "Regarding Resetable and PositionedStream (PS), the former is more tightly
> bound to store.
> For instance, initStream handles locking, which is probably not required for
> data streams outside of store. I don't see any immediate need to add the
> three methods resetStream, initStream and closeStream to LOBInputStream.
> I'm opting for committing what I have now, and look at combining the
> interfaces later if it turns out that is the best thing to do."
> Note that this task may also conclude that the two interfaces shouldn't be
> merged, but if so the rationale should be documented under this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
