When you have one large ArrayCollection on the client which you want to load a page at a time, FDS currently only supports paging from client to server. The fill method currently must return all items from the database. This is something we'd like to address in a future release.
To implement a page at a time ArrayCollection, you can simply pass in the page index as a fill parameter and then code it just to return the number of items asked for. One trick folks sometimes use is to return one more item than they display so that you can tell when you have hit the end of the list. Jeff ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of sid_flex Sent: Thursday, March 08, 2007 9:51 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Pagination using Flex Data Management Service Hello, Pagination using Flex FDS should be simple. Nevertheless i'ts hard finding examples of succesfull implementations using pagination with Flex Data Management Service. Configuring the destination is eaasy. For example: <destination id="product"> <adapter ref="java-dao" /> <properties> <source>flex.testdrive.store.ProductAssembler</source> <scope>application</scope> <metadata> <identity property="productId! "/> </metadata> <network> <session-timeout>11</session-timeout> <paging enabled="true" pageSize="5" /> <throttle-inbound policy="ERROR" max-frequency="500"/> <throttle-outbound policy="REPLACE" max-frequency="500"/> </network> </properties> &! nbsp; </destination> But what's the ! intended way to navigate through the pages returned? (Or is pagination only intended for optimised network trafic and will the result of ds.fill() always return the full result of the fill() method?) I'm looking for the best "next page", "previous page", "last page", "first page" solution using FDS. Thanks in advance for your reply. Best regards, Sieto
