I seen some,

I don't know if is related , don't know if is for slow connection it
never happened with my connection or because some are using mobile
devices.. since mobile goes to standby when
not in use..

I think never had same issue , you get to the application and then
send you 004 raw in less than 10 seconds or under.. I am using JsonP
options.

As of now I have changed from mootools 1.2.4 to mootools current as of
now 1.4.5 compat and my application feel lighter.

Nothing was broken and the application runs better , could be because
mootools it's not longer extending lots of thing in the DOM as it did
before..
Might be just me who knows..

On Dec 4, 12:02 pm, Nicolas <[email protected]> wrote:
> Did you experience that Utan?
>
> Le mardi 4 décembre 2012 09:33:59 UTC, Nicolas Guibert a écrit :
>
>
>
>
>
>
>
>
>
> > Yes, I use Mootools.
>
> > 2012/12/4 UTAN <[email protected] <javascript:>>
>
> >> Yeah, but is very random , may i ask? are you using Mootools session
> >> or plain javascript?
>
> >> On Dec 3, 6:49 am, Nicolas <[email protected]> wrote:
> >> > Hi,
>
> >> > 004 are meant to arise when the APE session has expired on the server. I
> >> > understand that this typically happens when the client has been
> >> > disconnected from the Internet and tries to contact to APE server again
> >> > when the Internet connection is back. The 004 error then means the APE
> >> > session is dead. So the client needs to initiate another session.
>
> >> > By default, a normal APE session lasts 45 seconds. So, I would expect
> >> that
> >> > once a connection is established, IT IS NOT POSSIBLE TO GET A 004 ERROR
> >> > BEFORE 45 SECONDS.
>
> >> > However, one of my users repeatedly received a 004 error only a few
> >> seconds
> >> > after another commands...
>
> >> > There are 2 possible causes:
>
> >> > 1) APE server lost its session information (bug? memory problem?)
>
> >> > or most likely:
>
> >> > 2) the client erases the APE session info and thus sends garbage to the
> >> APE
> >> > server that has no choice but to say that the session is invalid.
>
> >> > Any clue why this may be happening?
>
> >> > Thanks for your help.
>
> >> > Nicolas.
>
> >> > PS: this particular user is working on a Mac (Safari)
> >> > Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.57.2
> >> (KHTML,
> >> > like Gecko) Version/5.1.7 Safari/534.57.2
>
> >> --
> >> 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]<javascript:>
> >> To unsubscribe from this group, send email to
> >> [email protected] <javascript:>
> >> 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/

-- 
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/

Reply via email to