Changes between Version 5 and Version 6 of Future/DesktopSdk


Ignore:
Timestamp:
Dec 25, 2009, 7:54:01 AM (14 years ago)
Author:
jng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Future/DesktopSdk

    v5 v6  
    4646
    4747In terms of handling the managed/unmanaged resources divide, a desktop-based MapGuide could use a Sedna/directory combination or just simply a series of directories (one for each alias + one special directory for managed resources)
     48
     49Implementing MgFeatureService should be easy, since most methods in MgFeatureService are 1:1 with the FDO API
    4850
    4951This may sound like a case of NIH, seeing as MapGuideCommmon already provides an implementation of PlatformBase. The problem is that MapGuideCommon's implementation of PlatformBase has all the server/ACE/dbxml dependencies that we don't want or need in a desktop context (obviously because the server is using this library). The reason MapGuideCommon would exist in the desktop SDK is so that a desktop-based MapGuide can interop with a MapGuide Server, as we are currently doing in the Web Tier.