As for having a central place to keep track of all my HTTP posts, I’ve set aside http://benramsey.com/http-status-codes just for this purpose, but I also haven’t finished writing about them. I guess I should get on that.

Really, I do need to wrap up this series. I’ll see what I can do to make that happen soon.

Thanks for reading!

Maybe I just haven’t found it yet, but do you have a chart or table somewhere that shows all of the status codes you’ve covered? I can sort of pull them with tags, but there are also a lot of other posts in between; I’d love to be able to reference an easily bookmarkable list if possible.

I noticed a typo in this post though:

“In RESTful Web Services, Richardson and Ruby make this distinction between 204 and 204:”

That should be between 204 and 205

Ajax wird heute in fast jeder modernen Webanwendung genutzt, bietet doch jedes gute Javascript-Framework mittlerweile einfache Möglichkeiten XHR-Anfragen abzusetzen. In diesem Artikel soll es aber nicht um die Client-Seite gehen, sondern darum, wie man…

That being said, I do wish IIS could read .htaccess files and support mod_rewrite rules (I know it didn’t a year ago). I used a commercial solution on the last PHP site I deployed on IIS, so at least there is a way to do it …

Is there objective data out there which points to the most popular development platform?

And even if there is, how relevant is it. PHP developers are perhaps the most diverse group out there. You have basic hackers just getting things working, you have small/medium sized web-design shops and increasingly you’re getting enterprise oriented development. Each group has very different needs and different goals.

For me, as a largely enterprise focussed PHP dev I think the biggest reason I don’t develop (let alone deploy) on windows is tooling. There are so many tools that come with a basic linux or mac osx install that make a developer’s life easier.

Most low level PHP coders read blogs and material written by ideological or enterprise level developers who like the power and convenience of the *nix tool stack. I think as much as focussing on PHP’s performance, Microsoft need to create a tool stack comparable to what you can find on any Linux install or Mac.

As Rob says above, simple, simple things like rsync and SSH are a ‘mare on windows. Heaven help you if you want to do a simple grep to find a source code file.

It’s these little things that in aggregate make developing in Windows a mega pain. And that’s before you even get to the deployment stage.

My requests for MS at the moment revolve around deployment. Essentially, I want native, reliable SSH command line access that doesn’t use remote desktop connections or a VPN. Working, native rsync would be nice too.

A good start would be getting something like DeltaCopy installable via WPI as it’s really hard to get an IT dept to install anything that isn’t either from a big name PLC or installable via WPI.

Regards,

Rob…

A cool thing about POST: “If a resource has been created on the origin server, the response SHOULD be 201 (Created) and contain an entity which describes the status of the request and refers to the new resource, and a Location header. ”

So apparently you can use both for updates and creates, its all about the URL. You just have to check the RFCs…

Maybe the problem with PUT and PHP is: PHP usually gets its input through HTML-forms that don’t support PUT. And most webbroswers only support POST/GET

From what I understand, you’d request the server to create a blog pots by making HTTP POST request to the URI, say for example, http://example.com/article. Or http://example.com/myname/article. In the latter example, the article would be subordinate to the resource ‘myname’.

“according to the spec, a blog post could be created with either a POST or a PUT request”

I agree that both POST and PUT can be used to create the resource. It is more likely, we create resources without specifying the URI at which the resource has to be created. Isn’t this an uncommon request to create a resource – PUT, http://example.com/article/4?