Sitecore.Ship icon indicating copy to clipboard operation
Sitecore.Ship copied to clipboard

Published 20 hours ago • verified publisher icon kevinobee

Support Web API 2.2

Open kevinobee opened this issue 9 years ago • 2 comments

Introduce a ASP.NET Web API implementation of Sitecore.Ship and potentially deprecate the NancyFx and ASP.NET HTTP handler implementations.

kevinobee avatar Aug 11 '15 15:08 kevinobee

@kevinobee I think this would be a great idea. As we always support some services through Web API in all our Sitecore projects these would not cause any unwanted dependencies to us, and we could get rid of Nancy. However, i would like to see a more flexible configuration possibility than currently as today all ship endpoint are more or less hardcoded. Also it should be possible to provide different Web API services beside of Sitecore.Ship, but i guess this is just sort of making the configuration and routing correctly.

ernstjoss avatar Aug 25 '15 09:08 ernstjoss

@kevinobee @ernstjoss Moving to Web.API would also potentially solve issue #36. We could create a configuration file for each of the routes we need. See http://arcware.net/using-configuration-to-define-web-api-routes/

Is this worth a development spike?

DThrasher avatar Jan 13 '16 15:01 DThrasher