Code review comment for lp:~dandrader/unity-mir/improve_osk_ipc
Revision history for this message
| Michał Sawicz (saviq) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On 11.10.2013 16:16, Daniel d'Andrada wrote:
>> IIUC, this will still bail if the connection isn't available within 50s.
> Right.
>
>> >It might be good enough, but if there's an easy way to get notified on changes to
>> >the socket, maybe we should add it?
> The only thing I can think of is watching (through inotify) the directory where the socket file is expected to appear. But that will wake up unity8 for every file change in this directory and not only the socket one.
>
>> >So that if it shows up after the 50s, we
>> >will try again?
> I think we could simply throttle the retry frequency as time passes (frequent at first and occasionally later on) and finally give up at a much later point in time (say, 30 minutes).
Actually after a fix in upstart jobs, maliit-server will *always* be
running when unity8 is, so we should be good there. Let's leave as is.