Re: [RFC] add a shutdown event

2013-03-27 Thread Hardening
On 22/03/2013 13:42, Pekka Paalanen wrote: > On Mon, 18 Mar 2013 21:43:32 +0100 > Hardening wrote: > >> On 18/03/2013 13:48, Uli Schlachter wrote: >>> Hi, >>> >>> On 18.03.2013 00:30, Hardening wrote: On 17/03/2013 23:59, Sylvain BERTRAND wrote: > On Sun, Mar 17, 2013 at 11:32:21PM +0100

Re: [RFC] add a shutdown event

2013-03-22 Thread Pekka Paalanen
On Mon, 18 Mar 2013 21:43:32 +0100 Hardening wrote: > On 18/03/2013 13:48, Uli Schlachter wrote: > > Hi, > > > > On 18.03.2013 00:30, Hardening wrote: > >> On 17/03/2013 23:59, Sylvain BERTRAND wrote: > >>> On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote: > This patch adds a shutd

Re: [RFC] add a shutdown event

2013-03-18 Thread Gregory Merchan
On Mon, Mar 18, 2013 at 3:43 PM, Hardening wrote: > . . . > I still think it's a good thing for clients to know when the compositor > is shutting down cleanly. In the present situation, we have the > following cases: > * the compositor crashes: from the client point of view the socket > disconnect

Re: [RFC] add a shutdown event

2013-03-18 Thread Hardening
On 18/03/2013 13:48, Uli Schlachter wrote: > Hi, > > On 18.03.2013 00:30, Hardening wrote: >> On 17/03/2013 23:59, Sylvain BERTRAND wrote: >>> On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote: This patch adds a shutdow event so that clients can be notified when the compositor is

Re: [RFC] add a shutdown event

2013-03-18 Thread Daniel Barlow
On 17 March 2013 22:59, Sylvain BERTRAND wrote: > Is the socket disconnect not enough information for the clients? The salient question is: "what would you do differently as a client given a shutdown message than you would do given a SIGPIPE or an EPIPE error?" Whatever it is, it can't involve

Re: [RFC] add a shutdown event

2013-03-18 Thread Uli Schlachter
Hi, On 18.03.2013 00:30, Hardening wrote: > On 17/03/2013 23:59, Sylvain BERTRAND wrote: >> On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote: >>> This patch adds a shutdow event so that clients can be notified >>> when the compositor is about to exit (and potentially kill its >>> child pr

Re: [RFC] add a shutdown event

2013-03-18 Thread FORT David
2013/3/18 Yichao Yu > On Sun, Mar 17, 2013 at 7:30 PM, Hardening wrote: > > On 17/03/2013 23:59, Sylvain BERTRAND wrote: > [...] > > As most of the time the compositor launched all the wayland clients, > > they may be killed before they discover the socket has disconnected. > > > > It can be se

Re: [RFC] add a shutdown event

2013-03-17 Thread Yichao Yu
On Sun, Mar 17, 2013 at 7:30 PM, Hardening wrote: > On 17/03/2013 23:59, Sylvain BERTRAND wrote: >> On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote: >>> This patch adds a shutdow event so that clients can be notified >>> when the compositor is about to exit (and potentially kill its >>>

Re: [RFC] add a shutdown event

2013-03-17 Thread Hardening
On 17/03/2013 23:59, Sylvain BERTRAND wrote: > On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote: >> This patch adds a shutdow event so that clients can be notified >> when the compositor is about to exit (and potentially kill its >> child processes). >> This patch is based on gh next. >

Re: [RFC] add a shutdown event

2013-03-17 Thread Sylvain BERTRAND
On Sun, Mar 17, 2013 at 11:32:21PM +0100, Hardening wrote: > This patch adds a shutdow event so that clients can be notified > when the compositor is about to exit (and potentially kill its > child processes). > This patch is based on gh next. Is the socket disconnect not enough information for t

[RFC] add a shutdown event

2013-03-17 Thread Hardening
This patch adds a shutdow event so that clients can be notified when the compositor is about to exit (and potentially kill its child processes). This patch is based on gh next. --- protocol/wayland.xml |7 +++ src/wayland-client.c | 26 +- src/wayland-client.h |