Hello,
Sounds good, thanks Tron for the link, i'm reading it right now ;)
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/High-frequency-autorefresh-tp6368192p6376570.html
Sent from the qooxdoo mailing list archive at Nabble.com.
-
On 05/17/2011 05:58 PM, Mustafa Sak wrote:
> Hi Thron,
>
> is there any qooxdoo class who supports websocket like websocket.js with a
> automatic fall back to comet? Or is something like this planed?
I was just asking my colleagues about planned websocket support. The
answer was "not that I kno
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] High frequency autorefresh
> The first things i read about Comet (specificly "Streaming") looks a very
> good long life solution for my needs, as i have to manage a GUI that will
> remain open and autorefreshing for some very
> The first things i read about Comet (specificly "Streaming") looks a very
> good long life solution for my needs, as i have to manage a GUI that will
> remain open and autorefreshing for some very long sessions (more than one
> day in much cases)
To add to your pile of readables, you should al
Hi Daniel,
Thanks a lot for your answer, i was afraid to miss something huge...
About refresh, i'm currently trying to reduce the amount of data, looks a
good lead,
but there are several updates per seconds, and i'm already limiting to 1
request/sec to avoid overload...
The first things i read a
Hi Rudriko,
I can confirm the memory issue. I've opened a report for it:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=5129
The CPU load problem is likely due to the browser having to evaluate and
execute the response of every request as JavaScript since you're using
the Script transport.
If po
Hi everybody,
First of all i'd like to apologize if i'm missunderstanding things or if my
question is not correctly explained.
My need is to manage an array of items, having their own properties that are
frequently refreshed (once/s) by requesting the server for updates using
qx.ui.remote.Request
