| 29 | | Present managed wrapper doesn't help much when it comes to accessing MG's resources and repositories - up to the point where developers need to parse XML files manually, since there's no way of managed serialization/deserialization of underlying unmanaged types. Except for that, proposed managed API (dubbed "MgServerExtensions") offers some additional functionaliy not originally found within MG API: tile cache management, creating PDF documents from ready-made templates, samples of exposing and consuming custom web services, etc. |
| | 29 | Present managed wrapper doesn't help much when it comes to accessing MG's resources and repositories - up to the point where developers need to parse XML files manually, since there's no way of managed serialization/deserialization of underlying unmanaged types. Except for that, proposed managed API (dubbed "MgServerExtensions") offers some additional functionaliy not originally found within MG API: tile cache management, creating PDF documents from ready-made templates, samples of exposing and consuming custom web services, etc. |
| | 30 | |
| | 31 | I also need a feedback on usability of proposed API when it comes to .NET developers. |
