Mailing-List: contact users-help@wicket.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@wicket.apache.org
MIME-Version: 1.0
In-Reply-To: <20130307102013.GF24318@fh-wedel.de>
References: <20130307102013.GF24318@fh-wedel.de>
From: Martin Grigorov <mgrigorov@apache.org>
Date: Thu, 7 Mar 2013 12:36:35 +0200
Message-ID: 
 <CAMomwMpdmXh3RFhmtOLpQuPHT9TqnKzB=D4Yi9j90UCKM8viLQ@mail.gmail.com>
Subject: Re: Timer-based update to various regions in a page - best approach?
To: users@wicket.apache.org,
	Martin Dietze <martin@the-little-red-haired-girl.org>
Content-Type: multipart/alternative; boundary=089e010d861052b63b04d7534afd

--089e010d861052b63b04d7534afd
Content-Type: text/plain; charset=UTF-8

Hi,

You can use wicket-atmosphere instead Socket.io.

Or you can use one Ajax timer that broadcasts an event to all components in
the page and each component can decide whether to add itself to the target
or not.


On Thu, Mar 7, 2013 at 12:20 PM, Martin Dietze <di@fh-wedel.de> wrote:

> My customer wants me to rewrite an existing application in a
> way, that the various regions (drag-and-droppable panels) are
> all updated every xy seconds (most of these panels contain
> things like list views with search results, the user's mailbox
> etc.).
>
> Following a - what I would call - naive approach, one could
> trigger updates via Ajax every xy seconds for each panel
> individually. However I see the risk here of creating too many
> simultaneous network connections.
>
> Since I've never build anything like this before, I'd appreciate
> some opinions / advice, how to approach this problem the "Wicket
> way".
>
> Someone mentioned socket.io (which somewhat softens the client
> side prerequisites of native WebSockets), but is there any
> wrapper / adapter for Wicket yet? Also I feel a bit uneasy here,
> as the application already exists, so that the refactoring
> necessary to get the desired result might grow too high here?
>
> Another idea that has crossed my mind was a "central Ajax
> updater", that collects instances of all components needing an
> update and then triggers a rerender for all of them at the same
> time. I have not tried this, and I wonder if it is a good idea
> at all (would it have a negative effect on user experience?).
>
> I'd love to read your comments :)
>
> M'bert
>
> --
> ----------- / http://herbert.the-little-red-haired-girl.org /
> -------------
> =+=
> This parrot is no more.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>


-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>

--089e010d861052b63b04d7534afd--