Thanks for the explanation. It now makes sense. It is possible to use Hibernate caching with dataservices to cache objects in hibernate in order to speed up large fills?
- Kevin --- In [email protected], "Jeff Vroom" <[EMAIL PROTECTED]> wrote: > > With auto-sync-enabled = false, we no longer cache the resulting fill in > memory. So the second and subsequent page requests go back to the > assembler to refetch the fill just to get the page requested by the > client. > > > > In 2.5.1 when you use auto-sync-enabled = false, you can use the "fill > page" approach... your useFillPage method returns true and then the fill > variant which takes a start and count is called. This can make this > case much more efficient as the client pages data directly from the > database. > > > > Jeff > > > > ________________________________ > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Kevin > Sent: Wednesday, March 12, 2008 9:45 AM > To: [email protected] > Subject: [flexcoders] LCDS fill with AutoSyncEnabled = false, Paging > Takes Twice as Long? > > > > Has anyone encountered this before? I am filling a collection of > about 1500 objects. With autoSyncEnabled = false, the paging from the > server seems to double in time. (The server call returns in about the > same time, as expected.) > > I would actually expect the opposite, but either way, I am wondering > why AutoSyncEnabled would affect the time it takes to create the > objects in Flex? AND why would turning off autoSync affect this so > drastically. > > Thanks, Kevin >
