O'Reilly Community

Possible POE support in Resteasy

December 03 2009

I was thinking about some POE support for Resteasy.  On the client side add a poe() set of methods on ClientRequest and a @POE annotation for the Proxy framework.  I.e. ClienRequest request = ...; request.body("<stuff/>", "appliation/xml"); ClientResponse response = request.poe(); @Path("/") public interface MyService { @POE @Consumes("application/xml") public void poeIt(Data data); } The way… read more

RESTEasy 1.2.1 Released

November 23 2009

Minor bug fix release.  Also, had to remove one of the referenced maven repositories because it was screwing up the build. read more

“rel” name requirement overloaded

November 19 2009

The Atom link element and the Link header name their links using the “rel” attribute.  There is a requirement in the Atom Syndication Format and Link header RFCs that states that if the relationship is not registered with IANA, that you must use a IRI instead of a simple name. … read more

Overview of REST-* Messaging Draft 4

November 19 2009

Just finished draft 4 of REST-* Messaging.  Please check our our discussion group if you want to talk more about it.  Here’s a list of resources and their corresponding relationships for a high level overview.  See the spec for more details.  It relies heavily on Link headers.  The current draft… read more

Etag embedded within a Link

November 12 2009

I wanted to add acknowledgement to the queue consumer pull model in REST-* Messaging.  The way it would work is that consumers do a POST on the queue’s URL.  They receive the message as well as a Link header pointing to an acknowledgement resource.  When the client consumer successfully processes… read more

No Wait in HTTP

November 10 2009

One thing the HTTP specification does not have is a “Server Timeout” response code.  The 408 and 504 response codes are the only thing that comes close.  The idea of a “Server Timeout” code is that the server received the request, but timed out internally trying to process the request. … read more

REST-* Messaging Draft 3

November 06 2009

After prototyping, I’m back to writing another draft. This is a little bit more formal draft. I created a OSS project at: http://sf.net/projects/rest-star A draft of the PDF is at: http://reststar-messaging.googlegroups.com/web/REST-Star-Messaging-draft-3.pdf (You’ll have to click through an additional link that is *very* long). This draft only talks about the Message Publishing Protocol. I… read more

RESTEasy 1.2.GA Released

November 04 2009

After a few months RESTEasy 1.2.GA is finally ready.  This is mostly a cleanup, bug fix, and refactoring release, but here are some features of note: Guice 2.0 support.  Thanks Mike Brackx! Initial OAuth integration. Still a bit of a prototype, but we’re moving forward with this very soon.  Thanks Stef… read more

Parsing Link headers with Javascript and Java

October 15 2009

I wrote a Link header parser in Javascript. Thanks Mark Nottingham for sending me a link to his python equivalent. var linkexp=/<[^>]*>\s*(\s*;\s*[^\(\)<>@,;:"\/\[\]\?={} \t]+=(([^\(\)<>@,;:"\/\[\]\?={} \t]+)|("[^"]*")))*(,|$)/g; var paramexp=/[^\(\)<>@,;:"\/\[\]\?={} \t]+=(([^\(\)<>@,;:"\/\[\]\?={} \t]+)|("[^"]*"))/g; function unquote(value) { if (value.charAt(0) == '"' && value.charAt(value.length - 1) == '"') return value.substring(1, value.length - 1); return value; } function parseLinkHeader(value) { var [...] read more

Link headers vs. Custom headers

October 14 2009

There’s a really nice RFC out that defines the concept of a Link header.  Link headers are like Atom links within documents except they are specified within request or response headers.  For example let’s say we wanted to GET a medical image of an MRI.  This image might have additional… read more

Announcing a new distributed computing paradigm: ULSER

October 07 2009

I’m pleased to announce a new distributed effort named ULSER.  ULSER stands for a set of uncompromisable architectural principles, specifically: Uniform constrained interface. Links as the engine of application state Statelessness for scalability Enterprise applicable Resource and representation oriented Why call it ULSER?  Well, even though these architectural principles are extremely useful to design… read more

Thanks James and Cheyenne

September 30 2009

I just want to publicly thanks James Cobb and Cheyenne Weaver for putting together the branding, skin, look and feel for REST-*.org.  The site is nice to look at and gives a professional look and feel that I could never in my wildest dreams created by myself.  I hope to… read more

RESTEasy 1.2.RC1 Released

September 28 2009

We’re getting ready to release 1.2.GA.  This is a release candidate that fixes a bunch of outstanding bugs and reorganizes the project a little bit as well.  It is strongly suggested you take a look at the migration guide because a few pieces of RESTEasy have been refactored into separate… read more

New REST-* Workflow/BPM Effort

September 24 2009

I’ve put together some preliminary thoughts that have been swimming around in my head for the past few months on workflow and BPM.  Its hosted on our new REST-* work-group on the subject.  While we still have some work to do on defining some of the initial media types and… read more

We screwed up with first REST-* submissions

September 23 2009

We really screwed up with the initial drafts we put up for the initial REST-* specifications on a number of levels.  First the specifications were written 1+ years ago by me for the messaging submission and 8+ years ago by  Mark Little.  Both of us, at the time were still… read more