Re: How to tackle Ajax Flooding

[Tom Wollert]

Thanks for the replies, so I have to write my own Javascript...  no problem
I guess, was hoping for a cleaner way so to speak.

Any idea about disabling the postponing when the ajax channel is busy?
Specifically I have on my website an area where the user sends multiple
requests in very rapid succession. The way it is now all the requests
simultaneously? Right now the responses come with an awkward delay right
now. Any idea how to solve this elegantly?

2009/8/31 nino martinez wael nino.martinez.w...@gmail.com

 Is it something like this?

 http://www.nabble.com/No-behavior-listener-found-td20325302.html

 2009/8/30 Tom Wollert tom.woll...@googlemail.com:
  Hello there,
 
  I have a problem with my Wicket Application, which is quite Ajax heavy.
  Certain ajax calls take some time as they start an import, however the
  button can still be clicked and sends another ajax call (which is delayed
  for quite some time). Is it possible to disable the button while the
 request
  cycle is not complete? (I mean with wicket, or do I need to use
  Javascript?). Also ajax calls are postponed as long as the channel is
 busy,
  is it possible to deactivate this behaviour? And are there reasons why I
  should not?
 

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org

Re: How to tackle Ajax Flooding

[Tom Wollert]

The only idea I can come up with is to keep state of my model on client
side, but that would require alot of javascript :/

How to tackle Ajax Flooding

[Tom Wollert]

Hello there,

I have a problem with my Wicket Application, which is quite Ajax heavy.
Certain ajax calls take some time as they start an import, however the
button can still be clicked and sends another ajax call (which is delayed
for quite some time). Is it possible to disable the button while the request
cycle is not complete? (I mean with wicket, or do I need to use
Javascript?). Also ajax calls are postponed as long as the channel is busy,
is it possible to deactivate this behaviour? And are there reasons why I
should not?

Re: AbstractAjaxTimerBehavior start

[Tom Wollert]

Hi there,

Couldn't you just add the AbstractAjaxTimerBehavior to the page/component
after you receive the ajax call from the onSubmit event and then update the
component using the ajax request target? (untested, but I don't see a reason
why it wouldn't work. could imagine that this solution might not be as
elegant as hoped)

- Tom

Problem with AbstractAjaxTimerBehavior for periodic content update

[Tom Wollert]

Hello there,

I have a website which needs quite frequent updating. I was using the
AbstractAjaxTimerBehavior for quite some time, with 1 second duration.
Worked fine on my working machine (dual core) but now on my home PC I
realized some problems. Firefox uses up a lot of CPU power apparently,
making other applications unresponsive (the working machine had apparently
only one coreused up, that's why I didnt notice the problem. My home PC only
has one core).

Anyway, I thought the AbstractAjaxTimerBehaviour was a stupid idea anyway,
but I need frequent updates (actually updates might be several seconds or
minutes apart, but if there are updates, they need to be displayed fast.

I had an idea to just answer the response whenever there is actually
something to update and then send the request back (or after a short
timeout, like 10 seconds). However I ran into another problem that ajax
calls from that website will be postponed, due to the ajax channel being
used. In effect, since my timeout is 10 seconds, resulting in a behaviour
similar to an AbstractAjaxTimerBehaviour with 10 seconds duration

Anyone has any ideas how to solve this problem?

- Tom