<?xml version="1.0"?>
<rss version="2.0">
<channel>
    <title>Webhaven - Blogging outside the office</title>
    <link>http://webhaven.eu/</link>
    <description></description>
    <language>en_US</language>
    <pubDate>06:43, August the 1st, 2010</pubDate>
    <lastBuildDate>06:43, August the 1st, 2010</lastBuildDate>
    <docs></docs>
    <generator>Editmaster</generator>
    <managingEditor>blogger@webhaven.eu</managingEditor>
    <webMaster></webMaster>
    <ttl></ttl>



<item>
<title>Search Engine Optimization</title>
<link>http://webhaven.eu/webhaven_international_blog.html?viewid=2184</link>
<description>Over the past 10 years the search engine industry has evolved... and we have been paying attention.

What has come out of this process, in our assessment, is not so much a competitive rank system, in that you get to be #1 by magic (buying a self-proclaimed SEO specialist), but by relevancy to your search.

</description>
<pubDate>2010-06-06 00:00:00</pubDate>
<guid>http://webhaven.eu/webhaven_international_blog.html?viewid=2184</guid>
</item>

<item>
<title>I could have used this form verification javascript in 1999</title>
<link>http://webhaven.eu/webhaven_international_blog.html?viewid=1850</link>
<description>For some years I have relied on server-side form verification and returned an error to a would-be form submitter if they had not provided an email address or perhaps a check box declaration, or similar. Recently I have seen that the javascript form verification method is quite handy too (backed up by basic server-side method). It enables faster identification of user input error when completing a form. This is particularly useful in preventing &#39;submission frustration&#39; where a user is forced to re-enter fields, like password or turing-test fields...</description>
<pubDate>2010-05-27 00:00:00</pubDate>
<guid>http://webhaven.eu/webhaven_international_blog.html?viewid=1850</guid>
</item>

</channel>
</rss>