You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2019/07/22 17:25:00 UTC

[jira] [Updated] (DAFFODIL-1565) Unparse API Cursor-behavior/streaming enhancements

     [ https://issues.apache.org/jira/browse/DAFFODIL-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Beckerle updated DAFFODIL-1565:
---------------------------------------
    Summary: Unparse API Cursor-behavior/streaming enhancements  (was: Parse/Unparse API Cursor-behavior/streaming enhancements)

> Unparse API Cursor-behavior/streaming enhancements
> --------------------------------------------------
>
>                 Key: DAFFODIL-1565
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1565
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: API, Performance
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>
> See review comment for context.
> A thought. This API wants to eventually be something where we can call it over and over, picking up where the prior unparse left off in the output. That might be a different API that is slightly different, but in general we need to be able to leave the output in a state such that the next unparse call can continue where the previous left off.  Doing this at the bit-position granularity might be too hard, but byte-position ought to be possible. 
> That's not really about this API, which is symmetric with our parse API. It's just an additional requirement. (The parse API also needs this call-over-and-over capability.)



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)