ResourceExists in MaestroAPI takes 1 second to execute with LocalNative-Connection

[gBecker]

When using LocalNative-Connection the methode ResourceExists of the ResourceService takes more than 1 second to execute. Sometimes my WebPages needs up to 10 seconds to load because of high usage of this methode. With the old API the site loads very fast.

You can reproduce the problem with the SampleWeb of MaestroSDK_4.0.0. Create a LocalNative-Connection and wrap tracing around the ResourceExists methode in Default.aspx.cs:

Trace.Write("Begin"); if (conn.ResourceService.ResourceExists(mdfId)) {

Trace.Write("End");

Gunter

[jng]

The problem is that the local native implementation of ResourceExists() does a version check (against the SiteVersion property) to determine if the underlying MgResourceService.ResourceExists() is safe to call

SiteVersion is lazy loaded and it is this initial load that takes one second to complete. The property also only lives for the duration of the connection, which would probably explain why it takes 1s on every request as it is a different connection instance each time.

Since for local native connections, the site version is well-known because we're referencing against the official API, which exists in a known set of releases, we can just hard-code the return value, instead of interrogating MgServerAdmin for the actual version number. This will eliminate the 1s delay for ResourceExists() and any other API that needs to do version checks.

[jng]

Fixed r6428