Hi Roland, No, not really an RPC interface. Some very simple commands and events flow back and forth, like this: Command|GoToFrame|55 Response|MovedToFrame|55 Event|MovedToFrame|67 We needed it to be a dissector to enable us to detect when the user moves within a trace so that we can generate a suitable asynchronous
event. We also needed the functionality now, and it had to work with standard WS releases, so it had to be a plugin of some sort. By the way, we are not planning to submit this to be incorporated into the main stream code. You can see Syncro in action here
http://www.youtube.com/watch?v=anEZGfF4P10&t=5m5s if you are interested. Best regards…Paul From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx]
On Behalf Of Roland Knall So, if I understand it correctly, it is a RPC interface? I still think, implementing this as a dissector is a major overkill, and will also lead to issues further down the line, if dissectory API changes or similar issues. I'd implement
such an interface via a simple plugin architecture, which would have the added benefit, that you do not have the need for an active dissection runnning, to query the instance. A dissection should be mainly about "How to interpret packet data", which is not
the case here. regards Roland On Fri, Aug 5, 2016 at 11:33 AM, Paul Offord <Paul.Offord@xxxxxxxxxxxx> wrote:
______________________________________________________________________ This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ |
- Follow-Ups:
- Re: [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
- From: Roland Knall
- Re: [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
- References:
- [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
- From: Paul Offord
- Re: [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
- From: Graham Bloice
- Re: [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
- From: Roland Knall
- Re: [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
- From: Paul Offord
- Re: [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
- From: Roland Knall
- [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
- Prev by Date: Re: [Wireshark-dev] checklicenses.py
- Next by Date: Re: [Wireshark-dev] checklicenses.py
- Previous by thread: Re: [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
- Next by thread: Re: [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
- Index(es):