That's what I said : "silently". There is a bug with some version of
firebug. You should try with Chrome ;)
Anthony
crusherdestroyer a écrit :
Thank you for the direction. My only concern with that is that it
happens intermittently and I don't get any javascript errors in
firebug.
On Feb 19, 5:22 am, Anthony Catel <[email protected]> wrote:
Hi,
A javascript error can lead to a silent kill of the connection without
any debug. Follow this hint ;)
Anthony
crusherdestroyer a crit :
I probably just have something not configured correctly, but not
sure. What is happening is while i'm running my application in
firefox, I can see in firebug where ape is working. Every 25 seconds
or so, ajax will start up again. It will do this forever if I let
it. This is good. The behavior I'm seeing is when I click on submit
to send data, it will kill the existing ajax process in firebug and
immediately launch another one MOST of the time. Some times, it will
just quit running all together and then after many seconds will start
back up again. This is bad because the application won't work during
this time.
I noticed on some of your demos sites, that when you click on "submit"
on the applications the ape ajax process will continue to run in
firebug the entire 25 seconds before it stars a new one. No matter
how many times I submit data on those demo sites, it will not fail.
It just keeps running the full 25.
Why does mine always die and restart again? Is it suppose to do
that? I'm using inlinepush if that matters.
--
You received this message because you are subscribed to the Google
Groups "APE Project" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/ape-project?hl=en
---
APE Project (Ajax Push Engine)
Official website : http://www.ape-project.org/
Git Hub : http://github.com/APE-Project/
