[mapguide-internals] Session-MapName-Map

[Jason Birch]

I like that, if the second part is implemented.  It gets away from the
runtime map name being associated with the source map altogether.

Am I right that it would still breaking the existing code (because
you're returning a string rather than a void), but it doesn't affect the
MapAgent at all because the name is automatically set to the UUID?

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Trevor
Wekel
Sent: Friday, August 31, 2007 13:11
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Session-MapName-Map


Auto generating a UUID for the map name would be less of an API impact.
If you are willing to generate the UUID yourself, you can use the
existing API.

$uuid = uniqid("map",true);  // not really a GUID, just a unique ID
$map1 = new MgMap($siteConnection);
$map1->Create($resourceId, $uuid);
$map1->Save();

$map2 = new MgMap($siteConnection);
$map2->Open($uuid);


We may also be able to generate a unique id internally on the Save() if
a map name is not passed into the Create()

$map1 = new MgMap($siteConnection);
$map1->Create($resourceId);
$mapid = $map1->Save();  // generates a UUID internally


Much less API change this way...

Thanks,
Trevor