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
Hi Martin,
we had a similar requirement here and decided against ajax polling,
since this could add to the server load and prevent session expiration.
In Wicket 6 all components are notified of a running Ajax request
(#onEvent() with an ART payload). Our special components keep a
timestamp
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 d...@fh-wedel.de wrote:
My
Martin,
Disregarding the approach you follow to poll (or get pushed) changes I
would advice, if the volume of changes is big, not to repaint the whole
components but to pass some deltas with changes (e.g. in JSON format) and
do the repainting at client: I have used previous approach before and
On Thu, March 07, 2013, Martin Grigorov wrote:
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.
That looks pretty interesting. If I understand you correctly,
they would all add
On Thu, March 07, 2013, Sven Meier wrote:
Our customer can live with the limitations of this solution: As long as the
user doesn't do anything, he won't see any updated data.
Unfortunately, ours won't :/
Cheers,
M'bert
--
--- / http://herbert.the-little-red-haired-girl.org /
On Thu, Mar 7, 2013 at 1:51 PM, Martin Dietze d...@fh-wedel.de wrote:
On Thu, March 07, 2013, Martin Grigorov wrote:
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.
That
