Stefan Tilkov @stilkov

CEO/Principal Consultant at INNOQ, he/him, software architect, RESTafarian, conference tourist. Works at innoq.com. Fediverse: @stilkov@innoq.social

 Germany
innoq.com/
Joined April 2007
  • Tweets 35,176
  • Following 785
  • Followers 13,451
403 Photos and videos
Filter
Exclude
Time range
-
Near
Load newest
REST Anti-pattern #10. Breaking self-descriptiveness
REST Anti-pattern #9. Ignoring MIME types
REST Anti-pattern #8. Forgetting hypermedia
REST Anti-pattern #7. Misusing cookies
REST Anti-pattern #6. Ignoring response codes
REST Anti-pattern #5. Hiding context information
REST Anti-pattern #4. Ignoring caching
REST Anti-pattern #3. Using URIs to identify actions instead of resource
REST Anti-pattern #2. Tunneling everything through GET
REST Anti-pattern #1. Tunneling everything through POST
Writing an article on RESTful HTTP anti-patterns … ended up with 10, will post headlines next. Naturally, feedback would be great
as usual, delivering my JS column at the latest possible moment ... "I love deadlines. I like the whooshing sound they make as they fly by"
Replying to @dehora
@dehora PUT + content range != Partial update: only continuous regions, octet-level addressing … beaten to death? http://tinyurl.com/435xrd
purchase of time capsule -> 802.11n instead of g -> upgrade of two airport expresses ... sigh
setup new 1TB Time Capsule
Wondering whether http://tinyurl.com/2fa3kn should not better be two specs, one for the protocol level, one for the participant semantics
looking for a good Mac OS X AtomPub client, ideally one that handles extensions
Live notes from Jonathan Weiss's talk on Rails patterns: http://tinyurl.com/6faj4u
Talk notes from Jens Krämer's JRuby talk: http://tinyurl.com/5ek6ta
Replying to @jweiss
@jweiss @malagant wondering whether a distributed objects store isn't a solution to a problem many people would love to have
Load more