« Connecting the Dots
links for 2008-01-23 »
Jan
22nd

links for 2008-01-22

Posted in Daily Reads by del.icio.us at 10:22 am

Happy New Year! Marketing Technology finds and reports on the latest technology that will enable your business to effectively market to your audience, for acquisition or retention strategies. Subscribe now the Marketing Technology Blog RSS feed or to the Marketing Technology Email to have new content sent directly to your inbox. You'll also find my other business blog helpful, Social Media Domination.

RSS feed | Trackback URI

2 Comments »

Comment by Mike Schinkel
2008-01-24 00:08:36

Snipr’s API is cool, until you realize that it violates a principle tenet of web architecture; GETs should be “safe” (have no side effects.) See W3C’s TAG Finding “When to use GET” which states “GET is used for safe interactions and SHOULD NOT have the significance of taking an action other than retrieval.”

Several more references:

– http://www.w3.org/DesignIssues/Axioms#state
– http://www.intertwingly.net/blog/784.html
– http://www.cs.tut.fi/~jkorpela/forms/methods.html
– http://lists.w3.org/Archives/Public/www-tag/2002Apr/0091.html

Reply to this comment
Comment by Mike Schinkel
2008-01-24 00:31:26

Oh, and in case anyone thinks “GET must be safe” is just standardista mumbo-jumbo and it doesn’t really matter, realize that is what a lot of people thought until the Google Web Accellerator fiasco. Here are some links:

– http://blog.moertel.com/articles/2005/10/25/google-web-accelerator-vs-unsafe-linking-round-two
– http://bitworking.org/news/I_m_sorry__I_can_t_kiss_it_and_make_it_better_
– http://37signals.com/svn/archives2/google_web_accelerator_hey_not_so_fast_an_alert_for_web_app_designers.php

Also I’d highly recommend anyone wanting to design an API to discuss the best way to provide a RESTful API on the rest-discuss mailing list:

– http://tech.groups.yahoo.com/group/rest-discuss/

Reply to this comment
 
 
Name (required)
E-mail (required - never shown publicly)
URI
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.

My Comment Policy: I moderate comments. Please be patient:

  • Spam will happily be destroyed.
  • Use your real name, not some keywords. Otherwise it will be destroyed.
  • Mean comments aren't necessary. If I don't post them I will reply personally to let you know why.
  • Lewd comments will be edited, I don't want my readers leaving because of offensive content.
Great debate, criticism and colorful commentary is always appreciated and approved!