Project Codename "Astoria" - Microsoft takes a REST

re: Project Codename "Astoria" - Microsoft takes a REST

restdev — Mon, 06 Apr 2009 21:21:50 GMT

I understand the GET part. how does astoria handle PUT and DELETE?

re: Project Codename "Astoria" - Microsoft takes a REST

Happyrab — Fri, 14 Mar 2008 04:23:38 GMT

If you don't get the point of REST, you might be interested in this:

tomayko.com/.../rest-to-my-wife

Web Application Development with Microsoft Technologies » SOA Security in Enterprise Applications

Thu, 08 Nov 2007 18:20:13 GMT

Pingback from Web Application Development with Microsoft Technologies » SOA Security in Enterprise Applications

Web Application Development with Microsoft Technologies » Monthly AJAX.NET, ASP.NET, Silverlight Links.- October 2007

Sun, 04 Nov 2007 23:03:00 GMT

Pingback from Web Application Development with Microsoft Technologies » Monthly AJAX.NET, ASP.NET, Silverlight Links.- October 2007

re: Project Codename "Astoria" - Microsoft takes a REST

MikeBosch — Thu, 25 Oct 2007 13:32:24 GMT

I don't think it necessarily brings the semantic web, but as Glenn mentioned, it certainly makes it easier to work with. Also, in a "me too" respect, most of what people consider "Web 2.0" apps / services involve a REST protocol. Every entity is uniquely identified by a Uri. Well, that the argument for it anyways...

re: Project Codename "Astoria" - Microsoft takes a REST

Mike Chaliy — Thu, 25 Oct 2007 12:29:52 GMT

Why do you think that Astoria(or REST) brings to us Semantic Web?

re: Project Codename "Astoria" - Microsoft takes a REST

MikeBosch — Wed, 24 Oct 2007 18:07:46 GMT

"is there any reason developers should have to do more than play with a URL to get the data they want?"

I think "get" is the keyword. I can definitely see a benefit there. But when you get into a developer just having to post to a Url to update, create, delete entities is where I think it gets more complicated as far as validation, processes, and business rules that determine the interactions of these entities. Isn't that why we have RPC-style web services.

re: Project Codename "Astoria" - Microsoft takes a REST

Glenn — Wed, 24 Oct 2007 17:45:27 GMT

If you're wondering the problem that REST solves, it's excessive development time. It allows front end JavaScript/HTML programmers to work their Ajax magic without having to worry about the other stuff.

The security of it is still a big question.

But outside that, is there any reason developers should have to do more than play with a URL to get the data they want?

re: Project Codename "Astoria" - Microsoft takes a REST

Renny — Wed, 24 Oct 2007 15:42:17 GMT

500 :)

re: Project Codename "Astoria" - Microsoft takes a REST

MikeBosch — Tue, 23 Oct 2007 18:46:30 GMT

At this point its pretty much wide open and all REST operations are supported by default. The only built in security is verifying if you're authenticated or not. These are the questions I've been wrestling with. I'm not too familiar with the concepts of a REST architecture. I'd love to see how you'd implement a classic funds transfer scenario (transfer funds from Account A to Account B in an atomic transaction) with REST. I guess the scope of applications you would build with this is limited to read-only data (i.e. getting coordinates for a zip code).

The Facebook API uses a REST-based interface as does the Amazon S3 API. There seems to be a trend here, although I might be making the mistake of assuming that Astoria is REST and REST is Astoria. What REST seems to boil down to is being a ROA (resource-oriented architecture) where everything is simplified to implementing four basic operations GET(select)/POST(insert)/PUT(update)/DELETE(delete). A little too simplistic for enterprise applications if you ask me.