This project is read-only.

Where's the API/Web Service?

Mar 16, 2008 at 12:50 PM
In order to build a Forums Client, there needs to be some API or web service which will do all the server communication and co-ordination work. Of course, there is the existing NNTP protocol which has many major benefits: iot's well known, it's well understood, it's very stable and reliable and it is very widely used inside and outside of Microsoft.. But given the scope document it would appear that Microsoft will be rejecting this existing "API". Instead, it seems like Microsoft will be creating a new API or a new web serivce for this client to work against.

Until we see the API, commenting on client features is very much harder. We can, for example, ask for features in the client, but such a feature may be impossible unless the underlying API or service provides support.

So where is the definition of this new API or web service?

Mar 25, 2008 at 9:16 PM
As soon as it's publishable we should have a documented spec of the API.

Since the API is going to be ownedby the forums team, who has control over the implementation, if there are client features that we'd like to have, but are not currently available we can request that they be added to the API as needed.

We should keep in mind what the tool needs to do to be effective, not necessarily only what's exposed by the API on day 1.