Re: The Wicket Reflex Game Post thoughts?
On Fri, 26 Sep 2008, Nino Saturnino Martinez Vazquez Wael wrote: This is a potential pitfall if you ever will have two Ajax components that can remove the ones behavior, if the user clicks the other while loading then it's gonna complain. On the other hand im not sure what wicket can do besides throw a runtime exception. Actually this happens also in all cases where the components are being replaced, such as doing a continuous ajax search with a DataView. I don't know any better way than veiling things that will be replaced; it would be interesting to see if this can be replaced in the new Ajax implementation of 1.5. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations OyURL: http://www.ri.fi/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Wicket Reflex Game Post thoughts?
sync doesnt help in the area one bit
Because wicket already does that for you
The problem is that just after 1 ajax call that replaces/removes/what ever a
component another 1 is already waiting and want to execute.
in 1.5 we have to have a hash instead of the id i guess and silent failure
when the behavior is gone
But matej is working on that so everything will be great
johan
On Sat, Sep 27, 2008 at 3:16 AM, Adriano dos Santos Fernandes
[EMAIL PROTECTED] wrote:
Nino Saturnino Martinez Vazquez Wael wrote:
Hi Guys
One of the major problems with the game are that if you click a
box(AjaxEventBehavior) while the heartbeat(AbstractAjaxTimerBehavior) are in
process you will get an error, since the box's component has changed and no
longer carries that behavior. I've tried to solve this by adding a
transparent veil to the page once the heartbeat processes, it's simply not
good enough, it's still possible to get errors. So how do I solve this?
I have one idea but im not liking it, all box's could have behaviors even
if you wont get an score, that way we will not get an error.
This is a potential pitfall if you ever will have two Ajax components that
can remove the ones behavior, if the user clicks the other while loading
then it's gonna complain. On the other hand im not sure what wicket can do
besides throw a runtime exception.
Can't you use synchronized (obj) { ... }, to serialize multiple threads
of each ajax call?
Adriano
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Wicket Reflex Game Post thoughts?
I think it's already been taken care of.. IT's because the user clicks
on something that no longer exists..
Adriano dos Santos Fernandes wrote:
Nino Saturnino Martinez Vazquez Wael wrote:
Hi Guys
One of the major problems with the game are that if you click a
box(AjaxEventBehavior) while the heartbeat(AbstractAjaxTimerBehavior)
are in process you will get an error, since the box's component has
changed and no longer carries that behavior. I've tried to solve this
by adding a transparent veil to the page once the heartbeat
processes, it's simply not good enough, it's still possible to get
errors. So how do I solve this?
I have one idea but im not liking it, all box's could have behaviors
even if you wont get an score, that way we will not get an error.
This is a potential pitfall if you ever will have two Ajax components
that can remove the ones behavior, if the user clicks the other while
loading then it's gonna complain. On the other hand im not sure what
wicket can do besides throw a runtime exception.
Can't you use synchronized (obj) { ... }, to serialize multiple
threads of each ajax call?
Adriano
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The Wicket Reflex Game Post thoughts?
Hi Guys One of the major problems with the game are that if you click a box(AjaxEventBehavior) while the heartbeat(AbstractAjaxTimerBehavior) are in process you will get an error, since the box's component has changed and no longer carries that behavior. I've tried to solve this by adding a transparent veil to the page once the heartbeat processes, it's simply not good enough, it's still possible to get errors. So how do I solve this? I have one idea but im not liking it, all box's could have behaviors even if you wont get an score, that way we will not get an error. This is a potential pitfall if you ever will have two Ajax components that can remove the ones behavior, if the user clicks the other while loading then it's gonna complain. On the other hand im not sure what wicket can do besides throw a runtime exception. -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Wicket Reflex Game Post thoughts?
Nino Saturnino Martinez Vazquez Wael wrote:
Hi Guys
One of the major problems with the game are that if you click a
box(AjaxEventBehavior) while the heartbeat(AbstractAjaxTimerBehavior)
are in process you will get an error, since the box's component has
changed and no longer carries that behavior. I've tried to solve this
by adding a transparent veil to the page once the heartbeat processes,
it's simply not good enough, it's still possible to get errors. So how
do I solve this?
I have one idea but im not liking it, all box's could have behaviors
even if you wont get an score, that way we will not get an error.
This is a potential pitfall if you ever will have two Ajax components
that can remove the ones behavior, if the user clicks the other while
loading then it's gonna complain. On the other hand im not sure what
wicket can do besides throw a runtime exception.
Can't you use synchronized (obj) { ... }, to serialize multiple threads
of each ajax call?
Adriano
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
