Thanks Mark, It's already got quite a complex indexing algorithm based on a 4-ary b-tree - check MapLayerModel.getShapes() for an idea how it works. My ideal solution (hopefully in place by MXDU) would be to keep the full 10,000,000:1 dataset on the server and move most of MapLayerModel up into a cfc, with a local shared object cache of downloaded shape data. I've got a start on the server piece - the data swf actionscript is generated by a ColdFusion script that parses the original MAPINFO export files and creates the index.
Robin "Mark M" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Without looking at it Robin, sounds to me like you want to do something clever like only keep > a 10x10 square around what you are currently looking at through your camera in memory, and > then dump out the rest when it's past it's useful point. > > Make it alot more memory friendly. > > If you pick your numbers right, should be no reason why you can't load up images while the > user is browsing around - and they shouldn't notice a thing. > > Just some ideas. > > Mark --- You are currently subscribed to fugli as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
