<html><body bgcolor="#FFFFFF"><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">On Dec 8, 2009, at 9:43 AM, Tobias Arrskog <<a href="mailto:topfs2@xboxmediacenter.com">topfs2@xboxmediacenter.com</a>> wrote:</span><br></div><div><br></div><div></div><blockquote type="cite"><div>To bring more to the discsussion regarding uses of events at both wakeup and suspends.<div><br></div><div>On suspend apps can close sockets and signal disconnects properly to servers (even if the server in itself probably should handle a wrong disconnect it's nice to support it nicely).</div></div></blockquote><div><br></div><div>Hmmm... I know that my common suspend use case involves closing the lid and putting my laptop in my backpack, so I want suspend to happen as quickly and reliably as possible, and waiting for network connections to cleanly shut down strikes me as creating another set of failure points. I would rather rely on userspace network apps cleaning up after themselves at resume if needed.</div><div><br></div><blockquote type="cite"><div>
<div>On resume sockets could get reopened.</div><div>In XBMC, LIRC comes to mind as a perfect candidate, it tends to need reinitiate and we want suspend to behave transparently as shutdown, so resume needs to look like a startup so we rescan and such.<br>
<br><div class="gmail_quote">On Tue, Dec 8, 2009 at 4:36 PM, Tobias Arrskog <span dir="ltr"><<a href="mailto:topfs2@xboxmediacenter.com"><a href="mailto:topfs2@xboxmediacenter.com">topfs2@xboxmediacenter.com</a></a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Sure I agree, I just made it quick (more as a proof of concept for a patch I was working on).<div><br></div><div>But glad to see that there is more than me that needs it atleast :D<div><div></div><div class="h5"><br><br><div class="gmail_quote">
On Tue, Dec 8, 2009 at 4:34 PM, Richard Hughes <span dir="ltr"><<a href="mailto:hughsient@gmail.com" target="_blank"><a href="mailto:hughsient@gmail.com">hughsient@gmail.com</a></a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">2009/12/8 Tobias Arrskog <<a href="mailto:topfs2@xboxmediacenter.com" target="_blank"><a href="mailto:topfs2@xboxmediacenter.com">topfs2@xboxmediacenter.com</a></a>>:<br>
<div>> I posted a patch a few weeks ago, It might have been overlocked or just<br>
> uggly :)<br>
> Basically it did a dbus-event from pm-utils.<br>
> <a href="http://lists.freedesktop.org/archives/devkit-devel/2009-November/000527.html" target="_blank"><a href="http://lists.freedesktop.org/archives/devkit-devel/2009-November/000527.html">http://lists.freedesktop.org/archives/devkit-devel/2009-November/000527.html</a></a><br>
<br>
</div>No, you need to define the signal in the DeviceKit-power introspection<br>
document and emit the signal from within DKp. I think doing this as<br>
pm-utils level is the wrong layer.<br>
<font color="#888888"><br>
Richard.<br>
</font></blockquote></div><br></div></div></div>
</blockquote></div><br></div>
</div></blockquote></body></html>