The HTTP You Don't Know and the Read/Write Internet.
Why don't you subscribe to my blog while you're here? I'm a freelance web developer and I blog about Ruby, Rails, and business online.
Go ahead and subscribe to my RSS feed. Thanks for visiting!
The HTTP You Don’t Know
After working with the ATOM Publishing Protocol (APP) and paging through the HTTP RFC, it is clear that the full potential of HTTP has not been explored. APP uses request methods of PUT, and DELETE which are rare to see in use right now. But, I came across the if-* header fields a while ago that seem to offer some exciting potential too. Here’s a couple…
If-Match
A client that has one or more entities previously obtained from the resource
<br /> can verify that one of those entities is current by including a list of<br/><br /> their associated entity tags in the If-Match header field.<br/><br /> <br/><br />
If-Modified_since
The If-Modified-Since request-header field is used with a method to
<br /> make it conditional: if the requested variant has not been modified<br/><br /> since the time specified in this field, an entity will not be<br/><br /> returned from the server; instead, a 304 (not modified) response will<br/><br /> be returned without any message-body<strong>.<br/><br /> <br/><br /> </strong>
These headers look like they conflict with OpenSearch in some way. They both have slightly different characteristics. I’m not sure where I stand on this.
The Read/Write Internet
Internet application development needs a paradigm shift. The problem to me is that everything to date has been geared toward the READ based Internet. The READ/WRITE Internet will usher in new paradigms, new tools, and a new era. I don’t believe we are there yet, despite what some people would have you think.
technorati tags:atom, web2.0, http
Blogged with Flock
