Setting up a provider

Feb 8, 2013 at 10:48 AM
Hello,

I know you're currently working on a provider but if it's possible, could you provide some guidance on how to use the SDK to create 'provider code' which will 'listen' for incoming http commands from a consumer?

As the ASP.NET MVC 4 is to assist with the rest commands does this mean that posting and receiving http is outside of the remit of the SDK or will there eventually be an OSLCRestProvider.cs?

Cheers, Ian
Coordinator
Feb 8, 2013 at 11:27 AM
The actual GET/POST/PUT/DELETE functionality for HTTP will be outside of the SDK. See the MVC 4 WebAPI doc and tutorials for some examples of how to get started (http://www.asp.net/web-api). From my limited experience with it so far, it is a nice framework.

The pieces the SDK will bring to the table in the REST services area are:
  • how to register our RDF/XML Serializer/De-Serializer with MVC 4 so that your services will be able to handle the RDF media types transparently
  • a JSON provider - OSLC's serialization of JSON differs from the default serializer in MVC 4
  • some common OSLC resource classes which can be used in the "M"odel part of MVC 4.
Hope this helps clarify some where things are heading. Hoping to have some additional things for folks to look at early next week.
Coordinator
Feb 12, 2013 at 2:33 PM
You may want to subscribe to notifications for http://oslc4net.codeplex.com/workitem/4

I'll be checking in some early code today. I'm breaking this into 3 phases right now:
  1. Basic resource definition and support GET/PUT/POST/DELETE on individual resources (not collections/query)
  2. Add a ServiceProvider and ServiceProviderCatalog to the provider so that proper OSLC service advertisement/discovery can be done
  3. Add ResponseInfo and collection support.
So, the first drop will be a bit light on full provider functionality, but I'd rather get it out there so folks can see the basic structure of these providers.
Coordinator
Feb 19, 2013 at 5:15 PM
The sample provider is fairly complete right now. I updated the documentation page with some instructions on running it. Thanks to Steve P for adding significant new functionality to support creating the provider, especially in the area of collection support.