Sponsors

Links

• Domain Names
• Nouveau Riche University
• Online Bingo
• Bingo

Subscribe

Archives by Subject

So a few days ago I posted a question on the BlogCFC blog about whether I should add "crash protection" to the BlogCFC entry editor. What did I mean by that? As much as I love Firefox, it isn't the most stable beast in the world. That wouldn't matter so much except that I tend to get a bit worried when writing a particularly long blog entry. In the past I've used Word to write long entries since I know Word will automatically save my text even if I forget to. While BlogCFC does support XML-RPC clients, none of them have really caught on with my writing style so I haven't been using them.

Over on cf-talk, Jacob Munson mentioned that Blogger (I think that's some other blogware product - anyone heard of it? ;) will automatically save a draft of your blog entry every few seconds. I decided to take a look at how hard this would be to add to BlogCFC. Turns out it wasn't hard at all. I figured other people may benefit from this as a possible feature they could add to their own products.

So first off - let me talk a bit about the technique. The idea is simple: Every N seconds store the contents of the blog entry to a JavaScript cookie. Add code on the server side to check for this cookie when first displaying the form. Also add code to clean up the cookies when an entry has been stored.

For BlogCFC I decided to be lazy and only store two things - the title and body of the blog entry. Here is the JavaScript code I ended up using:

//used to save your form info (title/body) in case your browser crashes
function saveText() {
   var titleField = $("title");
   var bodyField = $("body");
   var expire = new Date();
   expire.setDate(expire.getDate()+7);
         
   //write title to cookie
   var cookieString = 'savedtitle=' + escape(titleField.value)+'; expires=' + expire.toGMTString() + '; path=/';
   document.cookie = cookieString;
   cookieString = 'savedbody=' + escape(bodyField.value) + '; expires=' + expire.toGMTString() + '; path=/';
   document.cookie = cookieString;
   window.setTimeout('saveText()',5000);
}
      
window.setTimeout('saveText()',5000);

The first thing I want to point out are these two lines:

var titleField = $("title");
var bodyField = $("body");

These are Spry (copied from Prototype) shorthands for:

var titleField = document.getElementById("title");
var bodyField = document.getElementById("body");

Outside of that - everything else is vanilla JavaScript. JavaScript lets you add cookies by simply setting the document.cookie value. Also note that document.cookie isn't a simple string. If you run document.cookie = something multiple times, you end up with multiple cookies.

The format for a cookie string is name=value; expires=DATE; path=PATH. In my case I simply used a cookie that expires in 7 days and a path of /.

Lastly I have a window.setTimeout, both outside of the function and inside, that will run this code every 5 seconds. Any duration is fine really.

To restore the values, I used this set of code on the server side:

<cfif not structKeyExists(form, "title") and structKeyExists(cookie, "savedtitle")>
   <cfset form.title = cookie.savedtitle>
</cfif>
<cfif not structKeyExists(form, "body") and structKeyExists(cookie, "savedbody")>
   <cfset form.body = cookie.savedbody>
</cfif>

Basically I simply ensure that I'm not already posting and see if I have anything in the cookie. I clear out the cookies using this code:

<cfcookie name="savedtitle" value="" expires="now">
<cfcookie name="savedbody" value="" expires="now">

As you can see, this is a pretty trivial implementation. Anyone else using something like this in their applications?

Comments (13) Jan 1, 2007 9:42 PM Views: 1742

Comments