As you have already seen in
http://issues.apache.org/jira/browse/TAPESTRY-1079 it's all due to memory
shortage. Maybe a bug, maybe not, 1MB per request is much, even while
developing.
Jesse: Using the files attached in the above bug report, some exceptions pop
up after leaving the ajax page some
Ok...I will look into this when I get back from traveling this
weekend...(flattery will get you everywhere ;) )
On 9/7/06, livelock <[EMAIL PROTECTED]> wrote:
Jesse, thanks for your tremendous efforts! Paying rent is always a good
thing
(TM).
You are right of course. Polling is not the way to
Jesse, thanks for your tremendous efforts! Paying rent is always a good thing
(TM).
You are right of course. Polling is not the way to go
(http://docs.codehaus.org/display/JETTY/Continuations), cometd is. Tomcat
will have continuations some day. But we have to start somewhere... at least
me :-) I
There ~will~ be more features like this soon, have been on the tail end of a
"rent paying" project release and haven't had time for anything else...
I'm not sure polling is the perfect answer (at least done this way.) You
might check out cometd.org as well. The dojo + jetty guys have been working
Yay, it works, thanks. It really looks like there should be a more elegant
solution to this, but hey, it works.
Now I am facing a different thing, using AJAX requests I only want to
transfer deltas. For example if there are 11 rows on the screen and on the
next update there is a new one, I don't
The following is contrived, but works. Mainly, I would create a proper
dojo widget and have the event listener bind to that, but this works
because of expando properties...
In your body of a file called Test.html, I have
dojo.require('dojo.lang.*');
dojo.
