If only it could be enough to set onreadystatechange to null :( Anyway, just a note to let you all know the polling is syndicated between all requests in the ajax rewriting (ie: only one timer no matter how many requests are being made concurrently).
2009/12/30 jblebrun <jbleb...@gmail.com> > On Nov 13, 3:12 pm, John Resig <jere...@gmail.com> wrote: > > It's because Internet Explorer has serious memoryleakissues with > > using the traditional model. Perhaps we could use conditional comments > > in this case, since it's not something that we can feature detect. > > Is there a reason that the repeatedly (in other venues) solution of > setting the onreadystatechange property to an empty function upon > completion is not sufficient for plugging this leak? The aggressive > polling is an awfully heavy-handed solution, punishing the majority of > platforms for the shortcomings of one. > > Cheers, > > jbl > > -- > > You received this message because you are subscribed to the Google Groups > "jQuery Development" group. > To post to this group, send email to jquery-...@googlegroups.com. > To unsubscribe from this group, send email to > jquery-dev+unsubscr...@googlegroups.com<jquery-dev%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/jquery-dev?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
