Nearing 1.0 and an upcoming (minor) breaking change

Progress on RestSharp has been steady lately with the addition of handling for file downloads, gzip/deflate compression handling, JSON request bodies and more. We’re down to just two outstanding issues and then I’ll be ready to christen and release RestSharp 1.0. If you have any features or bugs you want to get included in the first official release, now is the time to report them.

One thing I want to make note of for anyone that’s already using RS is a breaking change that will be committed soon. The ‘BaseUrl’ property that currently resides on RestRequest will be moving to RestClient. RestClient is where you want to be handling configuration that is common amongst many requests (like authorization which is typically pretty standard across an API) and the base URL for an API rarely changes between requests. This change will be checked in tonight.

Once the remaining issues are taken care of and the docs are beefed up I’ll release RestSharp 1.0. My goal is to have done by February 24th but it will likely be sooner than that.

Posted February 10th, 5:07 PM
Read more posts about Announcements.

View Comments
Link

  • alanhuffman
    After reading through this, I'm still not 100% sure what RestSharp is. After reading your GITHub information, you're providing a restful API that can be used in CLR (C#/VB.NET) -- cool.

    Is it a client or a REST Client API -- allowing for consumption of restful services?
  • It's a client for consuming RESTful APIs. Check out this video for a
    good overview:
    http://john-sheehan.com/blog/using-web-service-...
  • alanhuffman
    Got it... Nice job. I'm going to use this on our healthcare application to consume PHI from Dossia.org -- You should put your description: "It's a [CLEAN] client for consuming RESTful APIs." as a tag line.

    Thanks, Alan
blog comments powered by Disqus