You could write it in C and I would start with protocol buffers. 
On some search I found 
these: https://github.com/chrisdew/protobuf-wireshark 
and https://github.com/128technology/protobuf_dissector
May be worth checking if those are any good.


On Monday, January 23, 2017 at 8:21:06 AM UTC-8, [email protected] wrote:
>
> Hi,
>
> Thank you all for your valuable input. So I decided to develop a Wireshark 
> dissector for gRPC.
> I was researching on the development of dissectors and have some questions 
> regarding the
> design and functionality of the gRPC dissector. Maybe you can answer them 
> or know somebody
> who can answer them.
>
>    - Which language should be used to develop it? It is possible to 
>    develop dissectors either in C or Lua.
>    - The dissector wouldn't make sense if the payload couldn't be 
>    decoded. So the IDL file has to be provided somehow to Wireshark. One 
>    approach would be to generate the dissector from the IDL file. A similar 
>    approach was chosen for CORBA dissectors (
>    https://www.wireshark.org/docs/wsdg_html_chunked/ChDissectIdl2wrs.html). 
>    What would be the best approach for the gRPC dissector?
>    - gRPC is very flexible and can also (according to 
>    https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md) 
>    transport data encoded in formats other than protocol buffers. What would 
>    be the best way to handle other formats? However, I think its better to 
>    focus on protocol buffers first.
>
>
>
> Am Dienstag, 10. Januar 2017 19:00:03 UTC+1 schrieb Louis Ryan:
>>
>> +cc piotr who is doing work to support 'upstream' http2 in nginx which 
>> would by implication support GRPC so we're pretty well covered there. If 
>> you're interested in doing something with proxies you should take a look at 
>>
>> https://lyft.github.io/envoy/
>>
>> with whom we're doing some work too. If you want something ambitious, 
>> implementing QUIC support for the client connection in one of these proxies 
>> would be quite meaty.
>>
>> Outside of proxies there's lots of other stuff that can be done for GRPC 
>> - performance, compression, tooling, other serialization formats (e.g. 
>> Thrift), ...
>>
>> On Mon, Jan 9, 2017 at 10:12 AM, 'Carl Mastrangelo' via grpc.io <
>> [email protected]> wrote:
>>
>>> I recall there being some work on that *somewhere* but I don't recall 
>>> the status.  
>>>
>>> +Louis who is more familiar than I am with it.
>>>
>>> On Saturday, January 7, 2017 at 10:27:02 AM UTC-8, 
>>> [email protected] wrote:
>>>>
>>>> Hi,
>>>>
>>>> Thank you for the link to the list. I was also thinking of developing a 
>>>> nginx module which would allow to load balance gRPC traffic. Do you know 
>>>> what would be
>>>> the basic tasks of such a module? As far as I know the current problem 
>>>> with nginx is that it doesn't support HTTP/2 to the backend when proxying 
>>>> traffic.
>>>>
>>>> Am Mittwoch, 4. Januar 2017 01:14:08 UTC+1 schrieb Carl Mastrangelo:
>>>>>
>>>>> Hi, 
>>>>>
>>>>> Yes, we are definitely looking for help!  Did you have something in 
>>>>> mind you were interested in?  We have a (albeit stale) list of GSoC ideas 
>>>>> here: https://github.com/grpc/grpc/blob/master/summerofcode/ideas.md
>>>>>
>>>>> On Tuesday, December 20, 2016 at 4:18:32 AM UTC-8, 
>>>>> [email protected] wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I'm a master student and I would like to work on gRPC within the 
>>>>>> scope of my master thesis.
>>>>>> Are there any areas in gRPC (especially Java or Android related) 
>>>>>> which would need contributions?
>>>>>> Could you give me some hints?
>>>>>>
>>>>>> Thank you in advance
>>>>>>
>>>>> -- 
>>> 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/0b9e5e7a-e196-4855-a395-485b01426d86%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/grpc-io/0b9e5e7a-e196-4855-a395-485b01426d86%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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/0b5ab52a-3af2-40e9-ba4b-8ed56272a7f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to