Custom DFS Service & Content Transfer. What is the best practice?

aflowers001

Hi,

We're looking into developing custom DFS services. What we want to be able to do is provide a more specific and targeted API for consumers.

Whilst we're pretty happy with most things we're a little stumped as to what is best for content transfer.

The basic options we're considering are

1. Pass content using DataPackage->DataObject->Content
   This would seem to be the best choice, but it has the major downside of requiring consumers to know perhaps a little too much about the core DFS API, and it is open to mis-use if the developers of the consumers decide to 'play' with the DataPackage or DataObject or ...

2. Pass content using one of the Content subclasses
   Not investigated if this actually works as yet, but it has the same issue as above. It requires consumers to know perhaps a little too much about the core DFS API.

3. Pass the content as a byte array in the call
   Whilst it works, passing content as a parameter just doesn't seem right.

4. Leave the service using DataPackage etc and create client wrappers
   In this model we would create the service using DataPackate etc, allow auto generation of the default client and then wrap the client code such that content is passed using a simple byte array model and then passed as a DataPackage etc. Whilst this seems to be the best solution it does seem to create a maintenance overhead in that we get auto generated code that we have to constantly map onto the simpler model.

What is considered to be the best practice for this?