Support connections via LocalNativeConnection

[jbirch]

In some cases it would be useful to be able to connect to a server directly via TCP rather than through the MapAgent, even if that meant limited functionality for previews, etc.

[ksgeograf]

The problem with the native API is that it requires binaries for the specific version, so you would have to know in advance what binaries to use.

Secondly, the way the MapGuideDotNetApi.dll is tied to the binaries, means that you would have to make an override in the app.config file to load the correct dll.

Neither of those changes are trivial, and only apeals to the most hardcore users.

You would also need a webconfig.ini file.

The only benefit I can think of is that it does not require the WebServer to function.

Do you have specific use cases?

[jbirch]

That really does sound like a lot of work for the benefit.

The use case that I'm considering is where the web server is not configured for authoring, or is on a different server than the mapguide service. This would avoid having to configure authoring from a different web app or, in the latter case, having to install a web server on the mapguide server machine or another interal server.

Given how much difficulty Haris is having getting GeoREST to talk to different MapGuide versions, I don't think this is worth considering until some kind of native API versioning is in place, even if it is deemed important enough to consider.

[jng]

I think this is a really useful feature to have. I test MG builds from source more often now and being able to use Maestro against this server without needing to set up a web tier is incredibly useful.

Preview functionality will def. have to be disabled in this mode, but it's a small price to pay.

[jng]

Fixed in r4826

[jng]

Milestone Maestro-2.1 deleted