Re: Heartbeat control for CMS

We've used the JavaScript timeout approach, making HTTP requests via an
image object, in several applications where it's important to keep the
session alive even if the user makes no page requests for a while. It works
very well. No big deal - only a couple of lines of code.

Of course, if you need the server to communicate information back to the
browser (for chat etc), then it gets more complicated. In that case, you
might like to take a look at Rob Rohan's Neuromancer -

http://www.rohanclan.com/products/neuromancer/index.cfm

BTW it's not the case that the iframe approach will work in all browsers,
because not all browsers support iframes. Then again, not all browsers
support JavaScript. And there are accessibility issues with all these
methods, unfortunately.

Nick

----- Original Message ----- 
From: "Vlad Alexander (XStandard)" <vlad.alexander-2yTxSKUaU0r2eFz/[email protected]>
To: <[email protected]>
Sent: Thursday, November 04, 2004 10:35 PM
Subject: Re: [CMS] Heartbeat control for CMS


Hi Ben,

RE: setTimeout - interesting idea. Sounds like a possible alternative to
using iframe/meta refresh approach.

FYI, if anyone is interested in beta testing the heartbeat component or
wants to be notified when it is going to be available, please contact me off
the list.

Regards,
-Vlad
http://xstandard.com
XHTML WYSIWYG Editor For IE / Firefox


----- Original Message ----- 
From: "Ben Noblet" <[email protected]>
To: <[email protected]>
Sent: Wednesday, November 03, 2004 5:30 PM
Subject: RE: [CMS] Heartbeat control for CMS


> > A few days ago I mentioned that we received problem reports
> > that could be related to the iframe meta refresh technique
> > you mentioned for implementing a heartbeat in Web browsers.
> > Today we came across this security advisory related the use of iframe:
>
> Hi Vlad,
>
> Thanks for the info ... Our CMS is actually framed using framesets, so
it's
> one of the regular frames (the "status bar") that refreshes.  I suggested
> the iframe as many other systems are probably not framed.
>
> (btw I would never build a web site with framesets, but for an application
> it works very well)
>
> The only issue I have is that if the refresh fails once for any reason,
the
> frame never gets refreshed and can never try again as the refresh code
> doesn't load.
>
> I agree the component sounds like a better idea.  Another approach - how
> about some standard javascript in the page, which hits a URL on the server
> then reshcedules itself using the setTimeout function?
>
> Cheers
> Ben
>
>
> _______________________________________________
> cms mailing list
> [email protected]
> Subscription controls:
> http://lists.cms-forum.org/mailman/listinfo/cms
> Netiquette FAQ and related CMS lists - [cms-forum], [cms-pr],
[contentmanagers], [cmpros]
> http://www.cmsreview.com/NetiquetteFAQ.html
>

_______________________________________________
cms mailing list
[email protected]
Subscription controls:
http://lists.cms-forum.org/mailman/listinfo/cms
Netiquette FAQ and related CMS lists - [cms-forum], [cms-pr],
[contentmanagers], [cmpros]
http://www.cmsreview.com/NetiquetteFAQ.html