Providing multiple endpoints on a feature service

Discussion created by jbailey.spatialbridge on Nov 22, 2011
Latest reply on Nov 28, 2011 by jbailey.spatialbridge
I'm trying to design a feature service that will be consumed by multiple clients: some of them will be ArcGIS clients like an Engine application, and others will be non-ArcGIS clients that support open formats like WFS or KML.

My initial thought was to define an ArcGIS Server feature service that provided the various endpoints for the different clients (including providing native support for ArcGIS clients). However, my customer wishes to remain "independent" of ArcGIS Server for the non-ArcGIS clients.

This could be accomplished by providing 2 implementations of the service: one feature service hosted in ArcGIS Server, and another generic web service hosted by IIS or Apache that provides the open end points. However, I would strongly prefer not to provide 2 implementations of the same service just to get the different endpoints.

Are there any good patterns for achieving these design goals? Any suggestions on how to approach this?