Ah rats. :sadpanda: On Mon, Oct 2, 2017 at 4:09 PM, William Thurston <[email protected]> wrote:
> I found a pull request at www.github.com/grpc/grpc-java/pull/2545 but > this is per connection and not per message I believe, so may still not work > in your case. > > William Thurston > > On Oct 2, 2017, at 4:05 PM, Thas Himalayaratnam <[email protected]> > wrote: > > Hey William! > > So headers won't work for me in this case because I need to do this per > message in a bidi stream call. And headers are only sent/received at the > start of the call, not on the individual messages from > observer.onNext(request). > > With regards to the proxy related stuff, do you mind pointing me in a > useful direction to get started? > > Thanks again. > > On Mon, Oct 2, 2017 at 3:57 PM, William Thurston <[email protected]> > wrote: > >> I had contributed the server side of this originally, and the intended >> use was for caching purposes where a server could receive and return pure >> bytes from a cache driven by headers or something without needing to pay >> serialization costs. Given that original motivation, I didn't see value in >> doing the same thing client side where a cache query/response would be best >> served as an actual Java object, so I never wrote it :) >> >> Have you considered using headers instead for the case you're looking >> at? I believe there was also recently added support for proxy related >> stuff at the front of a stream that gets handled at the Netty layer. Maybe >> one of those alternatives works? >> >> William Thurston >> >> On Oct 2, 2017, at 3:49 PM, "[email protected]" <[email protected]> >> wrote: >> >> I am using https://github.com/grpc/grpc-java/blob/45085c3ce40f37c >> 39e2fc630f2d06f052064ee93/core/src/main/java/io/grpc/ >> ServerInterceptors.java#L138 on my server, and there doesn't seem to be >> a client-side equivalent to this. >> >> I would like to override the onMessage(RespT resp) in my client-side >> interceptor (SimpleForwardingClientCallListener) to work with an input >> stream rather than the grpc parsed request object. This is because i am >> sending some additional bytes in the input stream from my server and am >> going to do some additional work, before I manually parse the object and >> send to the handler. >> >> Anyone have alternative suggestions to this? >> >> Thanks! >> >> -- >> 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/ms >> gid/grpc-io/e03a3c33-f6bd-4ce1-ab98-65a9609ac455%40googlegroups.com >> <https://groups.google.com/d/msgid/grpc-io/e03a3c33-f6bd-4ce1-ab98-65a9609ac455%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> > > > -- > Regards, > > Thas > > -- Regards, Thas -- 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/CACHfKxbPs5s-eS8zTQCMmbxFSmWRqG_h0mGT%3D-bNUGhMkJ31tg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
