weblog | links

Uncommented

xml:   RSS 2.0
tags: none 0mq 8bit actors age agile ajax akka amazon ampq analytics android ant aop apache api appengine architecture art assembler atmel atom authentication aws backbone.js backup barcode bash bdd bigtable blog book bpel bpm bpmn bugtracking build cache callcc canvas cassandra cep cg cgi chart chat chili ci client clojure cloud cluster cmdb comet cometd compass complexity couchdb cpp css css3 cvs data database date dbi ddd debian demo design device dht diamond dsl dvd dynamo e4x easyb ec2 eclipse ecs eda email enterprisey equinox erlang esb esd esp etl event eventdriven facebook filesystem finger firefox flash flex flickr font food format fun functional funny game gentoo geotagging gis git google gps grails graph graphics graphs graphviz grid groovy gui gzip hadoop hash haskell hibernate history html html5 http hydrogen icfp im irc jabber java javascript javaspace javaspaces jbpm jca jdbc jersey jetty jfreechart jini jira jms jquery jruby jsf json jta junit jython kawa kiva lamp ldap life lift linux lisp lucene mail map mapreduce mashup maven mda mdm memcache memcached merb messages messaging metadata mobile mongodb mono mp3 mq mule music mysql network news nice nio node node.js nodejs nosql ocaml olap olpc ooffice openid opensource orchestration osgi osx owl p2p pdf people performance perl phone photo php pkd programming pubsub push python rabbitmq raid rails rainbow rdf reddit registry rest rfid rhino ria rspec rss ruby rules s3 saas salesforce sbcl scala scalability schemaless scheme science scrum search security semantic server service services shard shazam shell simpldb simpledb sinatra soa soap socialnetwork software space sparql spring sql ssh stax stm storage stream subversion svg svn swing tag tags task tech telephony terracotta test testing tex time tomcat tool travel tv twitter ubuntu uddi ui uml unix vanilla vf360 video visualization vodafone voip vxml wadl wave web web2.0 web20 webservice websocket wicket wii wiki wikipedia wine work workflow worklist wsdl wsif xform xforms xhtml xml xmpp xp xpath xpdl xquery xsd xslt xul zeromq

09.12.2009

# Simple long polling in Scala with Atmosphere ← http://www.innoq.com/blog/st/
09.12.2009 13:02 Uhr |

26.08.2009

# Orchestrating RESTful Services With Mule RESTPack And Groovy
Mule provides a simple, yet extremely powerful way to interact with RESTFul services using Mule RESTPack. | 26.08.2009 15:58 Uhr |

11.05.2009

# InfoQ: Best Practices for RESTful JSON Web Services
Recently Edwin posted an experience-based cookbook on best practices for building JSON-based Web Services. | 11.05.2009 14:44 Uhr |

01.05.2009

# REST worst practices
01.05.2009 13:06 Uhr |

09.03.2009

# Jersey Annotations explained!
09.03.2009 11:48 Uhr |

17.02.2009

# REST API Conventions ← http://www.innoq.com/blog/st/2009/02/restful_netflix.html
The Netflix Web API is a RESTful, resource-oriented architecture that makes an open standards API available to developers. This means that you can use just about any web language to access the API in your web applications. The only requirements for the language you use are that it has the ability to make HTTP requests and can parse XML responses. | 17.02.2009 10:31 Uhr |

22.01.2009

# RESTeasy ← http://www.infoq.com/news/2009/01/resteasy-ga
RESTEasy is a JBoss project that provides various frameworks to help you build RESTful Web Services and RESTful Java applications. It is a fully certified and portable implementation of the JAX-RS specification. JAX-RS is a new JCP specification that provides a Java API for RESTful Web Services over the HTTP protocol. | 22.01.2009 10:26 Uhr |

02.01.2009

# Building Super-Scalable Web Systems with REST
If you do walk the RESTful path, you?ll find that the scalability that was once so distant is now within your grasp. | 02.01.2009 17:25 Uhr |

10.12.2008

# Asynchronous Restful Web Application | Web Builder Zone
This blog annotates the Jetty 7 example web application that uses Jetty asynchronous HTTP client and the proposed suspendable servlets 3.0 API, to call an eBay restful web service. The technique combines the Jetty asynchronous HTTP client with the Jetty servers ability to suspend servlet processing, so that threads are not held while waiting for rest responses. Thus threads can handle many more requests and web applications using this technique should obtain at least ten fold increases in performance. | 10.12.2008 11:59 Uhr |

18.11.2008

# Things Caches Do ← http://www.innoq.com/blog/st/2008/11/things_caches_do.html
There are different kinds of HTTP caches that are useful for different kinds of things. I want to talk about gateway caches ? or, ?reverse proxy caches? ? and consider their effects on modern, dynamic web application design.l | 18.11.2008 10:10 Uhr |

12.11.2008

# I'll push and you pull. The mashup approach to application integration | ITworld ← http://fuzzypanic.blogspot.com/2007/08/pubsub-vs-atom.html
Now here is the kicker. The web - with all its concomitant bits'n'bobs from XML to RSS/Atom to AJAX - is an extremely good platform for pull-centric design. On the Web, if you try to pull some piece of information and something goes wrong, well you just pull again and again until you get it or give up. Nothing fancy. Just brutish repetition. Something machines are extremely good at. If you want to look at information from yesterday, you just go to the URL that contains yesterday's information. Nothing fancy. Just a simple naming convention that includes dates in URLs. | 12.11.2008 10:20 Uhr |

10.11.2008

# REST != HTTP | SOA Zone
Point is, REST is just an architectural style. It is nothing more than another entry alongside such things as client-server, n-tier, distributed objects, service-oriented, and embedded systems. REST is just a tool for thinking about how to build an application, and it's high time we kick it off the pedastal on which we've placed it and let it come back down to earth with the rest of us mortals. | 10.11.2008 11:45 Uhr |

27.10.2008

# Andrzej on Software: REST: Some tips and implementing
One of the examples that is hard/not worth (according to some people) to implement in a RESTful way is Forgot your password functionality. | 27.10.2008 09:38 Uhr |

07.10.2008

# InfoQ: How to GET a Cup of Coffee
In this article, we take a different approach, treating the protocols and document formats that make the Web tick as an application platform, which can be accessed through lightweight middleware. We showcase the role of the Web in application integration scenarios through a simple customer-service interaction scenario. In this article, we use the Web as our primary design philosophy to distil and share some of the thinking in our forthcoming book ?GET /connected - Web-based integration? (working title). | 07.10.2008 14:16 Uhr |

25.09.2008

# Serialising Java Objects to RDF with Jersey ← http://www.innoq.com/blog/st/2008/09/serialising_java_objects_to_rd.html
By combining JAX-RS and the So(m)mer's @rdf annotation one can remove remove the hurdle of having to create yet another format, and do this in a way that should be really easy to understand. | 25.09.2008 09:41 Uhr |

15.09.2008

# Testing REST ← http://www.innoq.com/blog/st/2008/09/tab_sweep.html
I?ve been using RSpec in a way that?s probably inappropriate, but has got me thinking about Test-Driven Development and REST. | 15.09.2008 09:13 Uhr |

04.09.2008

# Paper tigers and hidden dragons ? Untangled ← http://www.innoq.com/blog/st/2008/09/fielding_on_the_beyond_rest_xm.html
Unfortunately, the technical argument was a gigantic paper tiger, which is a shame given that there are plenty of situations in which event-based architectures are a better solution than REST-based architectures. I made a brief comment about notification design and how they seemed to be ignoring a good twenty years of research on Internet-scale event notification systems. People need to understand that general-purpose PubSub is not a solution to scalability problems ? it simply moves the problem somewhere else, and usually to a place that is inversely supported by the economics. | 04.09.2008 09:23 Uhr |

03.09.2008

# Using REST along other architecture styles | SOA Zone
Ok, if everything is so good, why not use REST for the whole system? Well, because like any architecture or architectural style (especially, when incarnated in a technology), REST has things that it does well and things that it doesn't (personally, I don't buy the Only Good Thing(tm) for anything or as Brooks puts it there's no silver bullet). | 03.09.2008 12:52 Uhr |

15.08.2008

# Stuck in the middle : Weblog ← http://www.innoq.com/blog/st/2008/08/rest_rdf_and_qi4j.html
Qi4j: REST EntityStore and SPARQL EntityFinder = rich client web apps! | 15.08.2008 19:51 Uhr |

31.07.2008

# Beyond REST, or Beyond XMPP? Both? The Q&A
No, my interest in XMPP is not a binary, mutually exlusive REST and/or, but rather a recognition that the technology that is more than instant messaging might be poised for a role in more than just instant messaging. | 31.07.2008 10:01 Uhr |

28.07.2008

# joshua's blog: beyond rest
28.07.2008 11:04 Uhr |

# When REST Doesn't Scale, XMPP to the Rescue?
28.07.2008 11:03 Uhr |

28.05.2008

# InfoQ: Scalability Best Practices: Lessons from eBay
There are many facets to scalability - transactional, operational, development effort. In this article, I will outline several of the key best practices we have learned over time to scale the transactional throughput of a web-based system. Most of these best practices will be familiar to you. Some may not. All come from the collective experience of the people who develop and operate the eBay site. | 28.05.2008 12:56 Uhr |

21.03.2008

# InfoQ: Addressing Doubts about REST
In this article, I will try to address 10 of the most common doubts people have about REST when they start exploring it, especially if they have a strong background in the architectural approach behind SOAP/WSDL-based Web services. | 21.03.2008 15:51 Uhr |

10.03.2008

# Home - Jersey Transport - Mule--Open Source ESB (Enterprise Service Bus) and Integration Platform ← http://www.innoq.com/blog/st/2008/03/jerseyjaxrs_mule_connector.html
This transport adds support for the JSR-311 implementation: Jersey. Jersey makes it possible to build RESTful services via a few simple annotations. | 10.03.2008 11:52 Uhr |

29.02.2008

# RESTful Data ← http://www.innoq.com/blog/st/2008/02/restful_data.html
In my latest column, Demystifying RESTful Data Coupling (PDF), I turn my attention to this claim and explain how RESTful data works, and why it too, like RESTful interfaces, reduces coupling when compared to WS-* and other similar approaches. | 29.02.2008 10:25 Uhr |

09.02.2008

# Jersey Client API ← http://www.innoq.com/blog/st/2008/02/jersey-client-api.html
Yesterday i finished refactoring the Jersey Client API and sprinkling it with some JavaDoc. This API was originally being used for Jersey unit testing but i think it is applicable in the larger context of a general RESTful client API. | 09.02.2008 20:58 Uhr |

18.01.2008

# rufus-verbs rdoc
?rufus-verbs? is an extended HTTP client library (gem). It provides the four main HTTP "verbs" as Ruby methods : get, put, post and delete. It wraps a certain number of techniques that make it a decent tool for manipulating web resourc | 18.01.2008 11:10 Uhr |

13.01.2008

# Inside Architecture : Engineering for Serendipity
Without a uniform interface for the information, integration based on REST will allow the sharing of operations, but not information. In short: If you stop at REST, the stack is incomplete. The missing part is a consistent set of information semantics. A key part of my push for a shared global integration model is precisely this: information identification standards and the semantics around how information can be used.  | 13.01.2008 00:18 Uhr |

30.12.2007

# WSO2 goes all RESTy
Also released just before Christmas is the WSO2 Registry 0.1. This early release demonstrates a completely REST-based approach to storing, searching and managing SOA metadata. The Registry stores any kind of resource in a simple JDBC driven store, and uses AtomPub as a web API to allow publishing and searching. The Registry has been deliberately designed to bring social interaction to the world of SOA metadata by including tagging, comments, rating and a wiki-like approach to SOA registries. | 30.12.2007 14:31 Uhr |

21.12.2007

# A RESTful version of Amazon's SimpleDB - subbu.org
The SimpleDB API is neither resource oriented nor HTTP friendly. Having said that, how should such an API be designed in a resource-oriented manner? Here is my take, a version-0.1 of a RESTful SimpleDB. In the design below, I tried to keep the semantics of this version as close as possible to the oficial SimpleDB API, but please comment in case you see errors or omissions. The design below uses URI templates in a loose manner, and I have made no attempts to formalize the syntax. | 21.12.2007 10:28 Uhr |

20.12.2007

# The Future of Web Services : Rails Envy
If you're just getting into Rails or you're not entirely clear on the whole REST thing, I gave a talk on Thursday, December 13th at the Orlando Ruby Users Group you might want to watch. | 20.12.2007 11:39 Uhr |

14.12.2007

# Sriram Krishnan: Amazon SimpleDB - Technical Overview
Structured storage was one of the missing pieces in Amazon's cloud services jigsaw puzzle (the other has to be the ability to host a site completely on EC2 without using dynamic DNS hacks) and Amazon is plugging that hole today with the launch of SimpleDB. | 14.12.2007 14:39 Uhr |

# Amazon SimpleDB ← http://www.satine.org/archives/2007/12/13/amazon-simpledb/
Amazon SimpleDB is a web service for running queries on structured data in real time. This service works in close conjunction with Amazon Simple Storage Service (Amazon S3) and Amazon Elastic Compute Cloud (Amazon EC2), collectively providing the ability to store, process and query data sets in the cloud.  | 14.12.2007 14:25 Uhr |

27.11.2007

# Testing RDDB: RESTful Ruby Database - igvita.com ← http://www.infoq.com/news/2007/11/the-rdbms-is-not-enough
RDDB is a document-oriented, RESTful database. The codebase is still young, and yet it already provides three different storage engines, support for partitioning, caching, and custom views. I couldn?t resist and decided to take it for a test-drive. | 27.11.2007 16:43 Uhr |

06.10.2007

# The ESB Question :: Steve Vinoskiò019s Blog
In a previous life, I helped develop ESBs. I?ve written about them and I?ve promoted them. But somewhere along the way, I lost the religion. | 06.10.2007 21:14 Uhr |

11.08.2007

# SQS REST Reference
11.08.2007 21:52 Uhr |

# IP Babble: RESTful Myths: Unraveling the Confusion
Before I start I'll summarize by saying this. Perhaps much of the present confusion is that the REST community has changed the semantics of some popular enterprise computing terminology. We shall address these below. | 11.08.2007 21:50 Uhr |

06.08.2007

# Orbeon Forms User Guide - REST and XForms Submission
More and more services are exposed and consumed through REST APIs, in other words APIs that leverage HTTP. In particular, XForms supports REST as of XForms 1.1. The XForms Submission processor exposes the functionality of to XML pipelines and allows you to call REST services from XPL without creating XForms pages. | 06.08.2007 11:32 Uhr |

25.07.2007

# Dare Obasanjo aka Carnage4Life - Google Base Data API vs. Astoria: Two Approaches to SQL-like Queries in a RESTful Protocol ← http://www.infoq.com/news/2007/07/GoogleBase-Astoria
Both Google's Google Base data API and Microsoft's Project Astoria are RESTful protocols for performing sorting, filtering and aggregate operations similar to what you find in SQL over a hierarchical set of resources. What follows is an overview of the approaches taken by both protocols. | 25.07.2007 20:34 Uhr |

18.06.2007

# Joe Gregorio | BitWorking | RESTify DayTrader ← http://www.innoq.com/blog/st/2007/06/16/simple_reliable_posting.html
Why build a RESTful web service for DayTrader? Because I frequently hear that REST can't be applied to complex situations. I also want to use the example as motivation for talking about some of the idioms that are available to handle more extensive requirements. | 18.06.2007 10:36 Uhr |

14.06.2007

# UrlRewriteFilter - Rewrite URL's in Java Web Application Servers
Based on the popular and very useful mod_rewrite for apache, UrlRewriteFilter is a Java Web Filter for any J2EE compliant web application server (such as Resin, Orion or Tomcat), which allows you to rewrite URLs before they get to your code. It is a very powerful tool just like Apache's mod_rewrite. | 14.06.2007 12:20 Uhr |

13.06.2007

# Why REST Matters
I?ve spent a little more time thinking about REST and I think I may have a couple of concrete arguments for REST that go beyond a simple appreciation of its beauty. | 13.06.2007 20:33 Uhr |

12.06.2007

# Excerpt: Ajax and Java Web Services
This chapter from "SOA Using Java Web Services" examines how to build an Ajax front-end to an online shopping application. Through detailed code examples, it walks you through building an Ajax application that consumes RESTful Java Web services endpoints. | 12.06.2007 22:52 Uhr |

09.06.2007

# Connecting RESTful Web Services to an ESB
Need a strategy for connecting RESTful web services to an enterprise service bus (ESB)? Check out three integration tools that will enable you to reliably incorporate RESTful web services into ESB-backed integration solutions.  | 09.06.2007 20:11 Uhr |

06.06.2007

# Joe Gregorio | BitWorking | Do we need WADL? ← http://www.innoq.com/blog/st/2007/06/06/do_we_need_wadl.html
06.06.2007 09:44 Uhr |

04.05.2007

# Stefan Tilkov: ApacheCon EU Wrapup
Dan Diephouse has put up two excellent presentations he did at ApacheCon EU ? Secure, scalable and reliable RESTful services and Navigating WS-(death?)*. Great stuff. | 04.05.2007 23:16 Uhr |

14.03.2007

# mnotò019s Web log: REST Issues, Real and Imagined
I think that most of the debate about REST focuses on the wrong things, leading developers down the garden path at the expense of their productivity and the success of their projects. Time and time again, I?ve seen folks who are new to REST get caught up on small stuff like this | 14.03.2007 23:54 Uhr |

# Pete Laceyò019s Weblog :: ROA Maturity Model
One of the reasons why RESTful applications have made little headway in the enterprise is we don?t have nifty things like maturity models. To remedy this, I have created the ROA Maturity Model. | 14.03.2007 23:52 Uhr |

13.03.2007

# wadl: Web Application Description Language (WADL) - Specification and Tools ← http://furiouspurpose.blogspot.com/2007/03/wadl-description-language-for-rest-of.html
However, if you are building or consuming APIs using XML over HTTP, it may have occurred to you that there's no consistent way of documenting and describing these services. WADL, the Web Application Description Language, attempts to fill that gap, and it seems relatively sensible. | 13.03.2007 20:35 Uhr |

05.03.2007

# 5 Ways to Mix, Rip, and Mash Your Data ← http://www.dzone.com/
Call them pipes, teqlos, dapps, modules, mashups or whatever else but fact is that recently we have seen a good number of new services that allow developers and users to build mini-apps and mashups that mix and re-mix data. Here we run through 5 applications that allow you to mix, rip and mash your data, looking at the data input, output, REST support, suggested use, and required skill level: | 05.03.2007 20:54 Uhr |

27.02.2007

# Design Patterns for Almost-Infinite Scalability .: Manageability :.
Pat Helland has written a very illuminative paper entitled "Life beyond Distributed Transactions: an Apostate's Opinion". Pat Helland's paper reveals some of these patterns in building what he calls 'alsmost-infinite scalability'. | 27.02.2007 20:35 Uhr |

25.02.2007

# Fiat Developmentum : Some REST Resources
25.02.2007 20:21 Uhr |

# Joe Gregorio | BitWorking | How to create a REST Protocol
If you follow web services, then you may have heard of REST. REST is an architectural style that can be used to guide the construction of web services. Recently, there have been attempts to create such services that have met with mixed success. This article outlines a series of steps you can follow in creating your protocol--guidance that will help you get all the benefits that REST has to offer, while avoiding common pitfalls. | 25.02.2007 20:21 Uhr |

# Inspirational Technology: 10 things to change in your thinking when building REST XML Protocols
25.02.2007 20:20 Uhr |

22.02.2007

# Marc Hadley's Blog: JSR 311: Java API for RESTful Web Services
22.02.2007 20:50 Uhr |

21.02.2007

# jra - Home
The Java REST annotations are annotations to help service creators build REST style services. Frameworks which wish to support REST can reuse these annotations just like the JSR181 & JAX-WS annotations are used across implementations. However, the idea with JRA is that many different frameworks (web, XML/SOAP, etc) may want to expose REST style services. | 21.02.2007 20:40 Uhr |

# DamnHandy : Archive » RESTEasy Preview: A RESTful Web Services Framework for Java
For the past few months, I have been mucking around with an idea for a RESTful Web Services framework I call RESTEasy. The project was inspired by the JAX-WS API and some of the work done by the WADL project. My driver for RESTEasy was to make it very transparent to expose a SessionBean or a POJO as a RESTful service and using JAXB annoated Entity Beans as value objects. | 21.02.2007 20:33 Uhr |

01.02.2007

# SD Times - Give It a REST ← http://www.innoq.com/blog/st/2007/02/01/give_it_a_rest.html
The very point of a service-oriented architecture is that you?re cleaving a very complex domain into a set of subdomains with different responsibilities; the complexity of negotiating what travels across the borders between those domains is an essential, not accidental, characteristic. In the face of such complexity, the best architectural choice is the one that provides the most visibility, so that problems and ambiguities can be quickly identified and addressed. | 01.02.2007 09:15 Uhr |

31.01.2007

# InfoQ: Interview: Arjen Poutsma on Spring Web Services
The Spring framework is very popular among Java developers as a more lightweight alternative to "enterprise" frameworks. One of the newest additions is the Spring Web Services subproject, which according to the Web site "is focused on creating document-driven Web services [and] aims to facilitate contract-first SOAP service development, allowing for the creation of flexible web services using one of the many ways to manipulate XML payloads." InfoQ's Stefan Tilkov had a chance to talk to Spring web services creator Arjen Poutsma about Web services in general and the Spring support in particular.  | 31.01.2007 09:25 Uhr |

22.11.2006

# XINS - XML Interface for Network Services
XINS is an open-source Web Services technology, supporting SOAP, XML-RPC and REST. It consists mainly of an XML-based specification format and a Java-based implementation framework. From its specifications, XINS can generate HTML, WSDL, client-side code, server-side code and test forms. Users do not require knowledge of any complex formats, such as XML Schema. | 22.11.2006 21:39 Uhr |

19.11.2006

# Nelson's Weblog: tech / good / flickrClient
I love how simple and Pythonic this is. Data is loosely typed. API calls are built dynamically. Everything is so abstract that the library code doesn't even have to be updated when new API methods or datatypes are added to Flickr. Clean, simple, perfect for scripting. It's about the exact opposite of SOAP and WSDL where you typically use thousands of lines of generated code to call the service.  | 19.11.2006 10:32 Uhr |

07.11.2006

# Stefan Tilkov's Random Stuff: SOAP vs. POX vs. REST
In my opinion, REST + standard XML formats, wrapped in SOAP where you need it, makes the most sense. | 07.11.2006 20:19 Uhr |

04.11.2006

# REST Web Services ← http://www.innoq.com/blog/st/2006/11/04/rest_web_services.html
If all goes well, REST Web Services will be published by O'Reilly in May 2007. We want this to be the definitive work on the real-world use of REST. | 04.11.2006 13:21 Uhr |

28.10.2006

# netzooid » CXF REST Support ← http://www.innoq.com/blog/st/2006/10/27/rest_and_celtixfire.html
Since the cat is out of the bag, I figured I?d blog about the CXF (incubating) REST support ... | 28.10.2006 11:27 Uhr |

18.10.2006

# Ryan Tomayko - How I Explained REST to My Wife
18.10.2006 20:30 Uhr |

11.05.2006

# The Cafes » REST vs. WS-*: A Parable ← http://www.innoq.com/blog/st/2006/05/10/rest_vs_ws.html
Hi there. My name?s Rusty, and I?m an air conditioning tech.  | 11.05.2006 09:28 Uhr |

10.04.2006

# [rest-discuss] RESTful representation of side effects? ← http://www.innoq.com/blog/st/2006/04/10/restful_differences.html
REST is better than object-orientation for the same reason as we have web browsers instead of CORBA-browsers. Uniformity is key. Simplicity at the network level is key.  | 10.04.2006 19:55 Uhr |

16.02.2006

# Playing Together Nicely: Getting REST and SOAP to Share Each Other's Toys
16.02.2006 14:45 Uhr |

19.12.2005

# Restlet
Bring the simplicity and efficiency of the REST architectural style to Java developers. | 19.12.2005 08:50 Uhr |

20.11.2005

# ONJava.com: The REST of the Web
In this article, I will present an alternative to basic web development taking into account some of these ideals: a RESTafarian adherence to the HTTP protocol, and using the flexibility proferred by Jython and Velocity in order to simplify servlet development. | 20.11.2005 13:50 Uhr |

# Building Web Services the REST Way
20.11.2005 13:37 Uhr |

30.08.2005

# XML.com: Dispatching in a REST Protocol Application
In my last column I covered how to dispatch based on mime type. That's only part of the dispatching story. The other two major pieces of information to use when dispatching are the HTTP method and the URI. Let's look at the HTTP method first. | 30.08.2005 09:25 Uhr |


© 2001-2004 holgerarendt.de