We have a rather restrictive architecture where we have a portal-like Seam application which launches further 'child' Seam applications inside an iFrame.
We have a problem where the portal application's HTTP session times out even though the 'child' applications are still being used. We need to keep the HTTP session timeouts to keep the site secure. We've been chewing at this problem for a while now and found ourselves down a number of dead ends.
So the questions is how can we block HTTP session timeouts in our portal application based on activity in 'child' applications?