Re: Long response page to hide page component generation time

2015-01-08 Thread Paul Hoadley
On 9 Jan 2015, at 5:29 am, Chuck Hill ch...@gevityinc.com wrote: The one problem you will run into is that the session and related ECs are not locked. You could refactor the page to take the user etc from other thread locals, pass them in and use localInstance EOs in an EC unique to the

Re: Long response page to hide page component generation time

2015-01-08 Thread Chuck Hill
The one problem you will run into is that the session and related ECs are not locked. You could refactor the page to take the user etc from other thread locals, pass them in and use localInstance EOs in an EC unique to the background thread. If you do that and don't touch session stuff in the

Re: Long response page to hide page component generation time

2015-01-07 Thread Paul Hoadley
On 8 Jan 2015, at 4:49 pm, Paul Hoadley pa...@logicsquad.net wrote: Calling generateResponse() and appendToResponse() on the report page both work in as far as they clearly spend the rendering time I'm expecting before returning from call(), but then my IERXPerformWOActionForResult

Re: Long response page to hide page component generation time

2015-01-07 Thread Paul Hoadley
On 8 Jan 2015, at 5:12 pm, Paul Hoadley pa...@logicsquad.net wrote: On 8 Jan 2015, at 4:49 pm, Paul Hoadley pa...@logicsquad.net wrote: Calling generateResponse() and appendToResponse() on the report page both work in as far as they clearly spend the rendering time I'm expecting before

Long response page to hide page component generation time

2015-01-07 Thread Paul Hoadley
Hello, I have what we'll call a legacy application that generates a single page report based on a large bunch of EOs. There's also some hairy nested subcomponents, and (simple GET) calls to a third party chart API. In short, the page takes a long time to render, but it doesn't appear to be