On Mon, 09 Jun 2014 16:54:09 +0800
Boyan Ding wrote:
> Hi,
> According to [1], from which the idea of protocol dumper came, the
> purpose of the protocol dumper is to track exactly how a client
> communicate with the server, and to make a difference with how
> WAYLAND_DEBUG=server works.
>
> So
Cc: wayland-devel@lists.freedesktop.org
> Subject: Re: Suggestions on implementing Wayland Protocol Dumper.
>
> On Mon, Jun 09, 2014 at 11:17:20AM +0530, Srivardhan wrote:
> > Hi,
> >
> > The following are the ways in which a Protocol Dumper can be
> implemented
On Mon, Jun 09, 2014 at 11:17:20AM +0530, Srivardhan wrote:
> Hi,
>
> The following are the ways in which a Protocol Dumper can be implemented:
> 1. Just before sending a message or when a message is received, the message
> can be written to a file. This change can be done in libwayland under #ifd
Hi,
According to [1], from which the idea of protocol dumper came, the
purpose of the protocol dumper is to track exactly how a client
communicate with the server, and to make a difference with how
WAYLAND_DEBUG=server works.
So IMHO, the protocol dumper may be implemented as a standalone program,
Hi,
The following are the ways in which a Protocol Dumper can be implemented:
1. Just before sending a message or when a message is received, the message
can be written to a file. This change can be done in libwayland under #ifdef
DEBUG. So when built enabling DEBUG, we should get all the protocol
