[mythtv] Reducing frontend startup time

[Piotr Oniszczuk]

> 
> Regarding #12229, have you tried this patch:
> [PATCH 273/340] Mythwelcome: Verify BE connection after FE exits
> 
> I also use STR-S3 for my combined FE/BE.  I haven't seen any problems
> since using this patch but I typically don't leave my FE on the EPG
> page...
> 
> -- 
> Lawrence Rust
> 
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org <mailto:mythtv-dev at mythtv.org>
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev <http://lists.mythtv.org/mailman/listinfo/mythtv-dev>
> http://wiki.mythtv.org/Mailing_List_etiquette <http://wiki.mythtv.org/Mailing_List_etiquette>
> MythTV Forums: https://forum.mythtv.org <https://forum.mythtv.org/>
Hmm - I see this patch is for myth welcome.
Unfortunately I’m not using mythwelcome.
What I want is to keep all time running mythfrontend - also during S3 cycle.

I’m guessing myth notify connection is TCP type connection.
How active TCP connections are handled in suspend-to-ram case?
Logic says me long sleep cycles are making TCP connections time-outed. 
So, after resume, TCP session should be reconnected - if it is time-outed. 
I think proper solution should integrate FE with OS in a way that OS resume from sleep should notify FE about resume and FE should check myth notify TCP connection - and reestablish it when time-outed conn. is detected.

Workaround might based on checking notify conn before every usage and quick reconnect when time-outed conn. is detected.
What You think?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20160110/601ce2f1/attachment.html>