Re: [Wireshark-dev] Future of extcap "API"

2022-08-21 Thread Tomasz Moń
On Sun, 2022-08-21 at 15:53 +0200, Jirka Novak wrote: > My goal is to prepare library calls (at least for C) which will hide > details for developer and there will be just callback and/or global flag > that extcap should finish its work. Extcap author can use it if graceful > shutdown is require

Re: [Wireshark-dev] Future of extcap "API"

2022-08-21 Thread Jirka Novak
Hi, One of the benefits of the extcap-cli is, that we can and currently do, send an API version to the extcap utility which would allow breaking changes while still enabling a compatibility mode for older versions. Because of that, I think 2 would be an ideal scenario, just define the respons

Re: [Wireshark-dev] Future of extcap "API"

2022-08-21 Thread Roland Knall
One of the benefits of the extcap-cli is, that we can and currently do, send an API version to the extcap utility which would allow breaking changes while still enabling a compatibility mode for older versions. Because of that, I think 2 would be an ideal scenario, just define the response to th

Re: [Wireshark-dev] Future of extcap "API"

2022-08-21 Thread Jirka Novak
Hi, On Sat, Aug 6, 2022 at 1:09 PM Jirka Novak wrote: Extcap API: i) When extcap is started, dumpcap pass name of pipe to it and where it expects captured data. ii) STDOUT/STDERR is used to report messages/errors of extcap to wireshark, but it is shown/evaluated at the end of capture whi