Not wicket related but checkout Google servers - they finally lifted the lid on how they do it.

[credit cnet]
MOUNTAIN VIEW, Calif.–Google is tight-lipped about its computing operations, but the company for the first time on Wednesday revealed the hardware at the core of its Internet might at a conference here about the increasingly prominent issue of data center efficiency.

Most companies buy servers from the likes of Dell, Hewlett-Packard, IBM, or Sun Microsystems. But Google, which has hundreds of thousands of servers and considers running them part of its core expertise, designs and builds its own. Ben Jai, who designed many of Google’s servers, unveiled a modern Google server before the hungry eyes of a technically sophisticated audience.

Google’s big surprise: each server has its own 12-volt battery to supply power if there’s a problem with the main source of electricity. The company also revealed for the first time that since 2005, its data centers have been composed of standard shipping containers–each with 1,160 servers and a power consumption that can reach 250 kilowatts.

read the rest here on CNET

Don’t you love Internet Explorer? Man if this browser didn’t exist just thing of the millions of dollars/euro/etc that would be saved every week from developers not having to graple with Microsofts buggy/hard-to-work-with browser. I will be a happy man the day it dies.

Anyhow the reason for the post: We noticed here that IE handles return key pressed events different when submitting a form. We have a form with a signal TextArea and a AjaxButton. In Firefox when either clicking on the button or hitting return in the text area we would arrive on our AjaxButtons onSubmit method. All good and dandy.
However
In IE when clicking on the button everything worked as expected. But when hitting return we found that the page just refreshed and the onSubmit of the ajaxbutton was not called. It turns out that FF and IE handle this differently. FF will look for the first button in the form and submit that, where as IE simply submits the whole form.
This means we had to implement the onSubmit in the form as well as the AjaxButton onSubmit.

Problem here is you end of duplicating code as you only have the AjaxRequestTarget on the ajaxbutton onSubmit. Jeremy Thomerson came up with a couple fo suggestions one of which we have implemented do get rid of this duplicate code. I’d be interested to know if anyone has come up with a better way of handling this:

= new Form() {

   add(new AjaxButton() {
      void onSubmit() {
           if(!form.isSubmitted()) {
                 onSubmit();
           }
      }

  void onSubmit() {

      IRequestTarget iTarget = RequestCycle.get().getRequestTarget();
      AjaxRequestTarget target= null;
      if (iTarget instanceof AjaxRequestTarget) {
          target = (AjaxRequestTarget) iTarget;
      }

      //logic..

   }
}

This seems to work fine.