The problem in this particular case is that Fusion unnecessarily
enumerates the full schema of all the layers during initialization,
which for the Oracle provider in particular is very slow. The ajax
viewer takes a different approach and defers schema enumeration until
it is necessary for some other reason. We will be attempting to
implement the same approach in Fusion so that the startup time (to get
the app loaded and the first map drawn) is as short as possible.
Cheers
Paul
On 21-Aug-08, at 10:18 AM, Rock Beans wrote:
To be honest how does the data source type affect one viewer over the
other. I would think you would have the same issues in both. Most of
the API calls are identical. I know there is a JavaScript compression
fix that should be released soon with Fusion that should speed up
initial loads. I am seeing Fusion being faster in every other area
though personally.
The Rock
On Thu, Aug 21, 2008 at 1:59 AM, gingerbbm <[EMAIL PROTECTED]>
wrote:
That all sounds really promising but unfortunately I'm working to an
aggressive deadline, and having paid money for the Autodesk
MapGuide product
I sort of assumed it would operate consistently regardless of my
choice of
viewer.
So what's the best way of keeping track of these new developments?
Do you
announce it here or somewhere else? I'd like to be involved if I
can be.
Cheers
Stuart
--
View this message in context:
http://www.nabble.com/Fusion-%2B-Oracle-datasource-problem-tp17884373p19083167.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
