Comments on: What kind of talk about REST/RestSharp would you like to see? http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/ Sun, 05 Sep 2010 17:46:43 +0000 hourly 1 http://wordpress.org/?v=3.0 By: ugg boots http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/comment-page-1/#comment-14973 ugg boots Mon, 05 Jul 2010 12:50:53 +0000 http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/#comment-14973 Mark S. is definitely on the right track. If you want to get a professional looking email address, Id recommend buying your name domain name, like or <br><a href="http://www.discount-air-jordan.com/Jordan-Pro-Classic.html" rel="nofollow">Jordan Pro Classic</a><br> If its common it might be difficult to get, however, be creative and you can usually find something. Mark S. is definitely on the right track. If you want to get a professional looking email address, Id recommend buying your name domain name, like or
Jordan Pro Classic
If its common it might be difficult to get, however, be creative and you can usually find something.

]]> By: pos monitoring http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/comment-page-1/#comment-14925 pos monitoring Mon, 01 Mar 2010 05:58:30 +0000 http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/#comment-14925 why would you want this? whats the benefit? why would you want this? whats the benefit?

]]> By: Jason Goecke http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/comment-page-1/#comment-14924 Jason Goecke Sat, 27 Feb 2010 02:43:19 +0000 http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/#comment-14924 Looks great, in fact we just had someone ask the other day about a .Net library for the Tropo WebAPI (<a href="http://tropo.com" rel="nofollow">http://tropo.com</a>), which is REST/JSON. Looks great, in fact we just had someone ask the other day about a .Net library for the Tropo WebAPI (http://tropo.com), which is REST/JSON.

]]> By: serialseb http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/comment-page-1/#comment-14914 serialseb Thu, 28 Jan 2010 16:30:57 +0000 http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/#comment-14914 Anything with OpenRasta in it gets my vote :) Anything with OpenRasta in it gets my vote :)

]]> By: John Sheehan http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/comment-page-1/#comment-14912 John Sheehan Wed, 27 Jan 2010 21:17:35 +0000 http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/#comment-14912 Thanks for your feedback Josh. My original post format wasn't very clear. Can you clarify your answer based on the updated post? Thanks for your feedback Josh. My original post format wasn't very clear. Can you clarify your answer based on the updated post?

]]> By: josh http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/comment-page-1/#comment-14911 josh Wed, 27 Jan 2010 21:08:39 +0000 http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/#comment-14911 Well I won't be able to make it, but I've been wondering about REST in .Net. What I've learned about REST has been in the rails world. So I'd be curious how it fits in .Net. Obviously I'm not gonna be calling Map.Resources in web.config, so I'd wonder how one goes about using REST in .Net whether it be with MVC or not.<br><br>Of those topics, I think #2 would be most interesting to me. But again, I wont be there so my vote doesn't really count. Well I won't be able to make it, but I've been wondering about REST in .Net. What I've learned about REST has been in the rails world. So I'd be curious how it fits in .Net. Obviously I'm not gonna be calling Map.Resources in web.config, so I'd wonder how one goes about using REST in .Net whether it be with MVC or not.

Of those topics, I think #2 would be most interesting to me. But again, I wont be there so my vote doesn't really count.

]]> By: Donn Felker http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/comment-page-1/#comment-14910 Donn Felker Wed, 27 Jan 2010 20:48:47 +0000 http://john-sheehan.com/blog/what-kind-of-talk-about-restrestsharp-would-you-like-to-see/#comment-14910 I think that this talk would be good, but I wonder how many people would benefit from it? Do a lot of companies consume RESTful content? Most LOB applications I build never interact with third party REST apis, however this is biased given the fact that I work for a lot of very large corporations which are purely LOB applications. Many start-ups would definitely consume a lot of REST apis (I know I personally do). <br><br>I believe that most people "THINK" they understand REST but actually have no idea what REST really is. Just because their URL's are pretty <a href="http://example.org/Customer/123/" rel="nofollow">http://example.org/Customer/123/</a> doesn't mean its RESTful. After I explain the HTTP stack and then re-explain REST given a MVC or OpenRasta example, they get it. Given that, I think #2 would be very beneficial. I would rename it to something more appealing though, such as something that helps relate the developer to the real world use. Such as "Creating the next big app with REST" or "Expose your business API with REST". Just a thought. <br><br>But again, #2 is where I'd place my vote. If you do go #2, you could include #4 inside of #2. I think that this talk would be good, but I wonder how many people would benefit from it? Do a lot of companies consume RESTful content? Most LOB applications I build never interact with third party REST apis, however this is biased given the fact that I work for a lot of very large corporations which are purely LOB applications. Many start-ups would definitely consume a lot of REST apis (I know I personally do).

I believe that most people “THINK” they understand REST but actually have no idea what REST really is. Just because their URL's are pretty http://example.org/Customer/123/ doesn't mean its RESTful. After I explain the HTTP stack and then re-explain REST given a MVC or OpenRasta example, they get it. Given that, I think #2 would be very beneficial. I would rename it to something more appealing though, such as something that helps relate the developer to the real world use. Such as “Creating the next big app with REST” or “Expose your business API with REST”. Just a thought.

But again, #2 is where I'd place my vote. If you do go #2, you could include #4 inside of #2.

]]>