Browse by Tags

Tagged Content List
  • Blog Post: Implementing only certain aspects of OData

    While we focus on keeping things simple, the whole OData protocol does have a bunch of functionality in it, and you don't always need the whole thing. If you're implementing a client or a server, how much of OData do you need to handle? OData is designed to be modular and grow as you need more...
  • Blog Post: Every SharePoint 2010 server is a Data Services server

    I haven't been writing much here, mostly because I've been way too busy but also because I couldn't discuss publicly many of the things I'm doing. Now that SharePoint 2010 has been announced and its feature set published everywhere, I can finally discuss one of the coolest things we've been up to lately...
  • Blog Post: PHP toolkit for ADO.NET Data Services

    Folks in the interoperability team at Microsoft just announced something they've been cooking for a while, developed Persistent Systems : a client PHP toolkit for Astoria services. It follows more or less the model of the .NET client where you can run a tool during development to get code-gen based on...
  • Blog Post: Adding support for JSONP and URL-controlled format to ADO.NET Data Services

    JSONP is a common way of making data accessible in client-side mashups even when the requests need to be cross-domain. While the current version of the ADO.NET Data Services framework does not support this, it’s possible to build it on top. There are a couple of ways of doing this. Here is what’s probably...
  • Blog Post: REST and Concurrency Control

    As part of the Astoria design process we scanned through many topics, some of them are straightforward, some are hard but mostly mechanical, but there are some that become interesting, fundamental aspects to address. I found the problem of concurrency control over REST interfaces very interesting...
Page 1 of 1 (5 items)