|
Have you done some testing with real data
to determine if server paging is warranted? In my experience, data access
is extremely fast. It is the rendering of large datasets that is usually
the bottleneck (though much faster since 8.5). You can speed up data
transfer by compressing the data. I haven’t done this yet, but
others have. I know I would seriously doubt the value
of server paging for a 400 / 25 record situation. 4000 / 250 maybe, 40,000
certainly. That is just based on experience, no rigorous testing. If you do page, clearly you can’t
return a subset of a sorted set without sorting the whole set. That will
have to happen on the server, so any sort is a server hit. One more count
against paging. I am just thinking, perhaps someone with
some direct experience will be more help. From: We have an issue we are trying to resolve. We know
that the datagrid by default has the -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
__,_._,___ |
