Yep, I made it more difficult than it needed to be. Disregard :) On Wednesday, October 25, 2017 at 7:50:29 AM UTC-7, Ryan Lubke wrote: > > Hey Folks, > > Some background first. We have a requirement to support multiple > serialization formats. To this end, we've created a backend in Java, and > are creating clients in multiple languages. So far, we've been successful > with Java, JS, and Python. We're prototyping Go now (as we learn Go) where > we have unary invocations working fine. However, streaming (we're only > interested in server streaming) seems to be a different beast. > > Looking at the docs and the generated code, we need to provide a > StreamDesc which references a StreamHandler. > This StreamHandler requires access to the server interface that was > generated. > > Beyond creating a server interface that the client consumes, is there > anything that needs to back that interface? > > Perhaps there's a simpler approach that I've missed? > > Thanks > -rl >
-- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/b21ec38e-84f2-44cf-870a-e857b64aa605%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
