php|tek 2009 SlidesAnother php|tek come and gone. I’m saddened by leaving, but, as usually happens, I’m reinvigorated and reenergized to go back to work. It seems I need these events to get together with other developers to raise me up out of periods of burn-out. I’m sure the same goes for others. I gave my talk this morning [...]
|
|
||||||
|
Recent PostsOn Companies Using TwitterAs a Twitter user (@ramsey) with over 700 followers, a good followers-to-following ratio (4 followers for every 1 I’m following), and over 4600 updates, I think I have a valuable perspective on the use of Twitter. I throw these numbers out there not to brag, and I’ll be quick to point out that this is [...]
Web 1.0, 2.0, and 3.0 DefinedA couple of months ago, an e-mail thread went around the company discussing “Web 3.0” technology. Naturally, I felt the need to put in my two cents, and I thought it would make for a good blog post. Let me know what you think. Do you agree? Disagree? Marketing speak aside, I like to think of [...]
Specifying rev=”canonical” With HTTPIt looks like there’s a lot of momentum behind rev=”canonical” now—and all built up within the span of about forty-eight hours. So, while I disagree with the use of “canonical” for semantic reasons and rev for the potential of mass misunderstanding and improper implementation, I think I’ll bite the bullet on this one for now, [...]
Summarizing My rev=”canonical” ArgumentI think my central argument against rev=”canonical” in my previous post was lost due to the fact that my post was so long. So, I’ll try to summarize my points in a very concise way. Let’s get away from the argument about rev not being in HTML 5. That’s not the point. If a case can [...]
A rev=”canonical” RebuttalThere’s a lot being said about rev=”canonical”. Others have already explained what it is and stated the arguments for it, so I won’t go into all of that, but I would like to offer a rebuttal—to play devil’s advocate, so to speak—in hopes that we’ll all slow down and think about what we’re doing before [...]
OAuth IETF Working GroupVia Joe Gregorio, it looks like OAuth is setting up a working group with the IETF. Currently, those on the mailing list are working to draft the IETF working group charter, which states: The Working Group will produce one or more documents suitable for consideration as Proposed Standard, based upon draft-hammer-oauth-00.txt, that will:Improve the terminology used.Embody [...]
HTTP Status: 100 Continue CorrectionsLast year, I wrote about the 100 Continue HTTP status code and the usage of the Expect header with the 100-continue expect value. However, I made a few erroneous statements, and a reader recently corrected me on them. So, I’m writing now to correct those statements so that I’m not misleading anymore readers. The incorrect statements [...]
Book Review: RESTful PHPWhen I was contacted by a representative of Packt Publishing to review RESTful PHP Web Services by Samisa Abeysinghe, I was naturally interested. After all, I’ve written and spoken a lot about representational state transfer (REST). But I was also skeptical because plenty of people these days talk about RESTful web services, but they don’t [...]
HTTP Status: Client ErrorsThe last post in my HTTP status code series was just over six months ago. I’m sorry for taking so long to revive the series, but I’m back with a discussion about the 4xx status codes. I hope you enjoy it! The 4xx series of HTTP status codes is intended for client errors. That is, the [...] |
||||||
Tags: 
