[mapguide-internals] Re: Please review RFC 73
Christine.Bao at autodesk.com
Mon Jul 13 22:44:46 EDT 2009
Your question about exception handling is pretty good, thank you.
I didn't consider much on this before, and I planned to catch exception once it happened and throw it - "abort method" as it's called. However it seems not a good behavior, is it? Would you please tell me more detail about what's expected? Do you have discussion or ticket about this? Thank you.
Thanks & regards,
From: "Kenneth Skovhede, GEOGRAF A/S" <ks at geograf.dk>
Subject: Re: [mapguide-internals] Re: Please review RFC 73
To: MapGuide Internals Mail List <mapguide-internals at lists.osgeo.org>
Message-ID: <4A5B3739.60007 at geograf.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
OK, I was not considering that MgMap.Create was in another process than the repository. Thanks for clearing that up.
How are permission issues handled if there is a partial error?
Eg. requesting 2 resources, but access is denied to one of them?
An exception could also happen while accessing one of the resources.
Simply returning an error would follow the current "abort" method on runtime map creation failure.
There has been talk about fixing this behavior.
If this RFC would at least consider what implications the change would have for fixing this, I would be happy.
A method could be to return an exception list.
Regards, Kenneth Skovhede, GEOGRAF A/S
More information about the mapguide-internals