Another possibility is scala-asynch which I think can do what we want. ________________________________ From: Beckerle, Mike <mbecke...@tresys.com> Sent: Wednesday, April 22, 2020 4:34 PM To: dev@daffodil.apache.org <dev@daffodil.apache.org> Subject: Re: Daffodil SAX API Proposal
The alternative is probably scala.util.continuations aka "shift and reset". It's much harder to understand and use, but at least its in the standard library so is supported. (I think.) ________________________________ From: Steve Lawrence <slawre...@apache.org> Sent: Wednesday, April 22, 2020 3:40 PM To: dev@daffodil.apache.org <dev@daffodil.apache.org> Subject: Re: Daffodil SAX API Proposal I responded. I checked the license to make sure it's compatible (BSD-3), but I didn't actually check what versions of Scala it works with. Looks like it is only published for 2.11, and the repo hasn't been updated for at least 3 years. There is a 2.12.x branch in their repo, but it too hasn't been updated in a long time. We might have to see how much effort it would take to update that library, or perhaps find another library. On 4/22/20 3:28 PM, Beckerle, Mike wrote: > I reviewed this and added a comment about the only significant issue, which I > think just boils down to trying to keep the coroutining back and forth as > simple as possible. > > Another thought: Is the scala coroutines library supported in 2.11 and 2.12 > (and 2.13 for being future-safe?) > > > ________________________________ > From: Steve Lawrence <slawre...@apache.org> > Sent: Wednesday, April 22, 2020 1:06 PM > To: dev@daffodil.apache.org <dev@daffodil.apache.org> > Subject: Daffodil SAX API Proposal > > I've added a proposal to add a SAX API support to Daffodil. > > https://cwiki.apache.org/confluence/display/DAFFODIL/Proposal%3A+SAX+API > > Many libraries and applications already support SAX, so this should > provide a means for more seamless integration into different toolsuites, > opening up the places where Daffodil could be easily integrated. > > SAX is also generally viewed as having a lower memory overhead, though > this does not attempt to solve the memory issues related to Daffodil and > the internal infoset representation. This essentially just adds a SAX > compatible API around our existing API. Other changes are needed to > reduce our memory overhead and truly support a streaming model. > > - Steve > >
