On 2014-07-09, 16:24, Chris Hecker wrote: > I wonder if I could do a cheesy workaround for my site that would use > javascript to hook the post button on the forum page, and then test for > expired credentials, and then pop up a login box if they are, then > resume the post. It's a hack, but it might work.
We have a certain web application here at U-M that uses Javascript to check back with the web server every 60 seconds to see if there is new content that should be displayed for the user. This has the interesting side effect of disabling the cosign idle (or "soft") timeout (2 hours) and detecting the cosign hard timeout (10, 12, or 24 hours) when as soon as it occurs. It's not nearly as good as your proposed workaround, but I've noticed that people of that particular webapp rarely wind up losing POST data. -- Mark Montague m...@catseye.org ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Cosign-discuss mailing list Cosign-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cosign-discuss
