Working on creating a paged data collection system where, essentially, the data collection only loads the parts of the data currently being viewed. It is basically a paged data sources where unused pages are thrown away to prevent a continual build up of data on the server.
Started by going out and looking at the latest and greatest examples of database to Flex UI using BlazeDS. The most promising and generic seems to be accessing a database through Hibernate and the JPA API. It maintains an in memory cache of the data and takes care of syncing it with the database (which can by any relational database, HSQLDB, mySql, Oracle, etc.).
I made a simple, non-paged data service that returns a list of fake customers (name, email, phone) and after one day can display a datagrid of 15,000 customers in flex in under 1 second. I’m going to up the number of entries in my database for 100,000 and see what happens on the flex side. I may also trying to add more columns with much more data per row to see how that affects timing and memory.
Once I have an idea of timings and the most efficient way to do things without paging, I’ll try paging the data and see how much of an improvement that is.
Useful Stuff:

You must be logged in to post a comment.