[mapguide-internals] Server status/Ping API

[Dave Wilson]

I would pre-define a default map image and settings as input values server side in the serverconfig: no point in having to remember this and supplying the path and stuff each time. Include a WithImage flag or something and make the map parameters optional or don't even bother supplying them to keep the signature light and the usability simple. Of course regardless if you supply the parameter or get it from the serverconfig it's possible the ResourceId is invalid and you'd get a rendering exception. Something to ponder.

To clarify a couple of points:

Do we include the Site Name as part of the results?
If we have a load balanced configuration do we return results for all sites and their status? This would be similar to the API we used to have for MG 6.5.

Dave


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Martin Morrison
Sent: Monday, October 26, 2009 8:25 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

Key word being SMALL...<G>  This could even be a single color sample image.  Just something to make the render engine works...



-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Trevor Wekel
Sent: Monday, October 26, 2009 10:08 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

No problem on the performance metrics.

Martin's suggestion of doing a lightweight render is a good idea.  Perhaps we can make this an optional item with the render only occurring if a map definition resource id is supplied as an input parameter.  We could just render a small image at the map extents.  The various pieces - API version, offline/online, and image could be returned as an xml document with the image returned as a base64 blob.  Something like this perhaps:

<Ping>
  <Status>Online</Status>
  <ApiVersion>2.2</ApiVersion>
  <ImageSize>8061</ImageSize>
  <Image>[8061 base64 encoded bytes]</Image>
</Ping>

Thanks,
Trevor

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Bruce Dechant
Sent: October 26, 2009 7:55 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Server status/Ping API

The API version would be nice to have.

I have to agree that performance metrics without credentials I'm not sure I like.

Bruce

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Sunday, October 25, 2009 11:00 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Server status/Ping API

I think it would be cool to return API version (2.1, 2.2, etc) as part
of this, but not rev/build.

Would be hesitant to return performance metrics through a non-authenticated api.

Jason

On 2009-10-22, Bruce Dechant <bruce.dechant at autodesk.com> wrote:
> Hi All,
>
> The existing Server Admin service has the following APIs that are not
> officially published but are available to use:
>
> GetSiteVersion() - returns the exact MapGuide server version
> GetSiteInfo() - returns MapGuide server information and OS information
>
> Both of these require authentication credentials because of the information
> returned.
>
> I was wondering about adding a new API that would not require authentication
> credentials.
>
> Example: GetSiteStatus()
>
> I would like it to return the server status as either "Offline" or "Online"
> as some of the information.
>
> This API could be used as a sort of "ping" if needed.
>
> What other non sensitive information do you think we could include with this
> API?
>
> Thanks,
> Bruce
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals


_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals