Hi,
From: Igor Vaynberg [EMAIL PROTECTED]
even after i turned off drag and drop for the ajax console and drip showed
no memory leaks the memory still leaked. /but/ if you navigate to a
different page the memory is released. so i am inclined to believe this is
not a memory leak but how explorer
i was talking about the leak when the ajax debug console is enabled...is that memory freed for you ralso after a refresh?-IgorOn 4/20/06, Ari Suutari
[EMAIL PROTECTED] wrote:
Hi,From: Igor Vaynberg [EMAIL PROTECTED]even after i turned off drag and drop for the ajax console and drip showedno
[EMAIL PROTECTED]
To: wicket-user@lists.sourceforge.net
Sent: Wednesday, April 12, 2006 9:51 PM
Subject: Re: [Wicket-user] wicket ajax memory leak with IE
Hi, I made some changes, this really helps, at least it works for me:
// AJAX FUNCTIONS
function wicketAjaxCreateTransport() {
var
No problem, I think that remaining leaks is just how IE works
Ari S.
- Original Message -
From: Matej Knopp [EMAIL PROTECTED]
To: wicket-user@lists.sourceforge.net
Sent: Tuesday, April 18, 2006 10:08 AM
Subject: Re: [Wicket-user] wicket ajax memory leak with IE
I see
Hi,
From: Igor Vaynberg [EMAIL PROTECTED]
well, at some point the server calls will start returning right? and so
xmlhttprequest objects will start being reused. it will consume memory to a
certain point and then stop. if you ask me 100ms for an ajax update is
unreasonable anyways,
Well,
]
To: wicket-user@lists.sourceforge.net
Sent: Wednesday, April 12, 2006 9:51 PM
Subject: Re: [Wicket-user] wicket ajax memory leak with IE
Hi, I made some changes, this really helps, at least it works for me:
// AJAX FUNCTIONS
function wicketAjaxCreateTransport() {
var transport = null
Sent: Wednesday, April 12, 2006 9:51 PM
Subject: Re: [Wicket-user] wicket ajax memory leak with IE
Hi, I made some changes, this really helps, at least it works for me:
// AJAX FUNCTIONS
function wicketAjaxCreateTransport() {
var transport = null;
if (window.XMLHttpRequest
Igor,
do you know RIFE/Continuations? It uses continuations for better state
handling and control flow instead of better performance.
There are some examples in this slide (pages 5 to 8):
https://www.dev.java.net/files/documents/204/3120/rife_fosdem_2004.pdf
It really looks like an
I can't speak for Igor - though we have talked about that too - but
for my opion see e.g.
http://www.theserverside.com/news/thread.tss?thread_id=39579#204913
Basically, I think continuations are a smart idea, and they might be
useful for wizard/ flow type applications. That said, I also think
heh, so why post to this thread and not start a new one?-IgorOn 4/14/06, Timo Stamm [EMAIL PROTECTED]
wrote:Igor Vaynberg schrieb: what do rife's continuations have to do with ajax?
Nothing. On 4/14/06, Timo Stamm [EMAIL PROTECTED] wrote: Igor, do you know RIFE/Continuations? It uses
Eelco Hillenius schrieb:
I can't speak for Igor - though we have talked about that too - but
for my opion see e.g.
http://www.theserverside.com/news/thread.tss?thread_id=39579#204913
Thanks for the link.
mind you that Wicket allows for very fancy state optimizations as
well.
Quoting from
the problem with the word continuation is that it has recently aquired multiple meanings.in rife, afaik, the continations are used to drive program flow. that is, the continuation remembers where in the function you are and can resume from that point forward. this is basically an abstraction of a
i dont see how this spreads the logic around. your navigation logic would be isolated in an object that will drive the flow and the steps are reusable panels.i wrote a wizard framework for the company i work for, and we have been using it with great success. it is driven by a general workflow like
I can confirm that it works for me too.
Hopefully this fix will get into next beta/rc of 1.2 !
Ari S.
- Original Message -
From: Matej Knopp [EMAIL PROTECTED]
To: wicket-user@lists.sourceforge.net
Sent: Wednesday, April 12, 2006 9:51 PM
Subject: Re: [Wicket-user] wicket ajax memory
[EMAIL PROTECTED]
To: wicket-user@lists.sourceforge.net
Sent: Wednesday, April 12, 2006 9:51 PM
Subject: Re: [Wicket-user] wicket ajax memory leak with IE
Hi, I made some changes, this really helps, at least it works for me:
// AJAX FUNCTIONS
function wicketAjaxCreateTransport() {
var
in AjaxSelfUpdatingTimerBehavour shouldn't fire
until previous request has completed ?)
Ari S.
- Original Message - From: Matej Knopp [EMAIL PROTECTED]
To: wicket-user@lists.sourceforge.net
Sent: Wednesday, April 12, 2006 9:51 PM
Subject: Re: [Wicket-user] wicket ajax memory leak with IE
Hi, I made
Johan Compagner wrote:
can you send me the wicket-ajax.js file that you use?
So that i have exactly the right version?
johan
On 4/12/06, *Matej Knopp* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Hi, I made some changes, this really helps, at least it works for me:
// AJAX
Hi.
I changed the wicket-ajax.js to create only one instance of
XmlHttpRequest, and the memory leak in IE seemed to vanish.
So the problem is that creating XmlHttpRequest probably causes a memory
leak. Howewer, having only one instance of XmlHttpRequest doesn't seem
to be the best idea
Hi,
Thanks for you response,
I changed the wicket-ajax.js to create only one instance of
XmlHttpRequest, and the memory leak in IE seemed to vanish.
So the problem is that creating XmlHttpRequest probably causes a memory
leak. Howewer, having only one instance of XmlHttpRequest doesn't seem
need several requests at the same time. So maybe pooling of
XmlHttpRequest(s) could work...
Btw, does dojo use pooling (since there was no leak with it) ?
Maybe it would make sense to check how they are getting around
this.
Ari S.
-Matej
Ari Suutari wrote:
Hi,
There is a
Ari Suutari wrote:
Hi,
Thanks for you response,
I changed the wicket-ajax.js to create only one instance of
XmlHttpRequest, and the memory leak in IE seemed to vanish.
So the problem is that creating XmlHttpRequest probably causes a
memory leak. Howewer, having only one instance of
Ari Suutari wrote:
need several requests at the same time. So maybe pooling of
XmlHttpRequest(s) could work...
Btw, does dojo use pooling (since there was no leak with it) ?
Maybe it would make sense to check how they are getting around
this.
Ari S.
Don't know, might be worth
is the leak still there if you turn off the ajax debug mode in IAjaxSettings?-IgorOn 4/12/06, Matej Knopp
[EMAIL PROTECTED] wrote:Ari Suutari wrote: need several requests at the same time. So maybe pooling of
XmlHttpRequest(s) could work...Btw, does dojo use pooling (since there was no leak with
Yeah, it is. However, it's much smaller. But still, 10-15 kb per request.
-Matej
Igor Vaynberg wrote:
is the leak still there if you turn off the ajax debug mode in
IAjaxSettings?
-Igor
On 4/12/06, *Matej Knopp* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Ari Suutari wrote:
i looked through the _javascript_ but nothing jumped out at me. did you notice anything cause im stumped.-IgorOn 4/12/06, Matej Knopp
[EMAIL PROTECTED] wrote:Yeah, it is. However, it's much smaller. But still, 10-15 kb per request.
-MatejIgor Vaynberg wrote: is the leak still there if you turn
AFAIK There's nothing wrong with javascript. The problem is that
creating XMLHttpRequest every time causes memory leak in IE.
People tend to reuse one instance of xmlhttprequest, but that does not
suffice here, i guess, therefore I suggested xmlhttprequests instances
pooling.
I tried to
is there a pooling implementation somewhere i can take a look at and borrow, im not really inerested in becoming a _javascript_ wiz just because ms cant get it right.-IgorOn 4/12/06,
Matej Knopp [EMAIL PROTECTED] wrote:
AFAIK There's nothing wrong with _javascript_. The problem is thatcreating
I guess I have seen one. But it shouldn't be that difficult to get it
done. I guess I might be able to look into it tonight.
-Matej
Igor Vaynberg wrote:
is there a pooling implementation somewhere i can take a look at and
borrow, im not really inerested in becoming a javascript wiz just
Hi, I made some changes, this really helps, at least it works for me:
// AJAX FUNCTIONS
function wicketAjaxCreateTransport() {
var transport = null;
if (window.XMLHttpRequest) {
transport = new XMLHttpRequest();
} else {
if (window.ActiveXObject) {
29 matches
Mail list logo
