Mailing-List: contact users-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@flex.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAMfyhm5GEdE2t+epi_RSR0fTm3NW8+2vm_f1ecBYRdjbmnw=LA@mail.gmail.com>
References: 
 <CAKNADY2MVxDCWShXEvsNUi9CGOBdRe1+vcvi33Cu0JDDgqf93A@mail.gmail.com>
 <CAMfyhm5GEdE2t+epi_RSR0fTm3NW8+2vm_f1ecBYRdjbmnw=LA@mail.gmail.com>
From: =?UTF-8?Q?Javier_Guerrero_Garc=C3=ADa?= <javi.gg@gmail.com>
Date: Thu, 25 Jun 2015 18:33:45 +0200
Message-ID: 
 <CAMfyhm5bWeqv9m1RCTNrgU+jgevfo36CKA6jqzGta9ivZXPPoA@mail.gmail.com>
Subject: Re: A script has executed for longer than ....
To: users <users@flex.apache.org>
Content-Type: multipart/alternative; boundary=001a1134c6e61d545605195a31ea

--001a1134c6e61d545605195a31ea
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

More on that:
http://www.jamesward.com/2008/11/21/drunk-on-software-episode-3-performance=
-pitfalls-of-flexs-arraycollection/

On Thu, Jun 25, 2015 at 6:29 PM, Javier Guerrero Garc=C3=ADa <javi.gg@gmail=
.com>
wrote:

> Hi Mark:
>
> A long shot here: are you sure that, while you are processing the XML,
> you're NOT triggering constant UI updates on each operation? For instance=
:
> if after processing each XML item, you are adding the final result to an
> ArrayCollection, and you have some rendering component bound to that
> ArrayCollection, that could cause a total repaint of the item renderers F=
OR
> EACH XML ITEM processed, hence causing the timeout. Something similar
> happened to me a while ago, and after noticing and solving it, I can say
> that 60 seconds are more than enough to process a few hundreds of thousan=
d
> XML items, and unless your XML is REALLY huge that should be enough :)
>
> If that applies, the obvious workaround is:
>
> 1. Do all your updates and additions on a new ArrayCollection (not on the
> one bound to the component's dataProvider), and then just swap the
> dataProvider of the component to point to the newly populated
> ArrayCollection instead
> 2. Or call "thefunctionthatdisabledautoupdates" in advance (don't remembe=
r
> the exact name right now) on the bound arraycollection before starting
> processing your XML, modify/update your arraycollection items, and then
> enabling it afterwards.
>
> P.S. "myCollection.disableAutoUpdate(); ", that was it :)
> http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf668=
d2-7fe7.html
>
> P.P.S. If none of that applies.... would some kind of "pagination" on the
> UI solve it?
>
> On Thu, Jun 25, 2015 at 3:52 PM, mark goldin <markzolotoy@gmail.com>
> wrote:
>
>> I have a large xml data that UI needs to process. I am getting the above
>> message about timing out. Not sure I can break my function into smaller
>> pieces. Any other idea?
>>
>> Thanks
>>
>
>

--001a1134c6e61d545605195a31ea--