Hi Ian, I'm not sure I understand. write() can throw an exception. Does that not solve the problem?
-Kenton On Mon, May 22, 2017 at 5:01 PM, Ian Denhardt <i...@zenhack.net> wrote: > Are there established best practices for handling errors that occur with > async/push style interfaces, such as sandstorm's Util.ByteStream[1]? > That interface doesn't seem to supply a way to report e.g. an IO error > that occurs while streaming, and since the call that obtained the > ByteStream has already completed, the error can't be reported via the > rpc protocol's exception mechanism. > > I suppose one could just add a method for reporting the error. But I > wanted to poll to see if there was any standard pattern for this. > > [1]: https://github.com/sandstorm-io/sandstorm/blob/master/src/sa > ndstorm/util.capnp#L69 > > -- > You received this message because you are subscribed to the Google Groups > "Cap'n Proto" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to capnproto+unsubscr...@googlegroups.com. > Visit this group at https://groups.google.com/group/capnproto. > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to capnproto+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/capnproto.
