InfoQ Interview Stefan Tilkov, May 31, 2010 At QCon London, Sadek Dobri interviewed me on REST – this was a nice chance for me to voice my current thinking about most, if not all things RESTful. InfoQ has put the video up online. On June 1, 2010 11:19 AM, Sean Kennedy said: Hi Stefan, Very good interview. Very interesting to hear that none of your clients use WS-Security i.e. all use HTTPS. What about other QoS features : - Message Reliability - have any of your clients used the WS-* model? - What about the REST options - Joe Gregorios best practice, POE or HTTPLR ? - Transactions - WS-* model? is RETRO gaining any traction? Thanks, Sean. On June 1, 2010 12:49 PM, Stefan Tilkov said: I haven’t seen WS-RM, POE or HTTPLR used in any project. We’ve built stuff similar to POE in custom scenarios. Nobody ever raises their hands when asked about WS-BusinessActivity or AtomTransactions when I ask for who uses that in any of my talks. Haven’t seen RETRO in practice either. BPEL, including its compensation features, is used quite a bit though. Don’t use this as scientific evidence :-) On June 4, 2010 3:39 PM, Marcel Koch said: Hi Stefan, wow, I appreciate the detailed level of the interview. Altough the interview answered a lot of questions I have to further ones: You said that it would a bad idea to build up a logic in a client application to create the URIs. I would argue there has to be an entry point to the RESTful application. Why not to build the entry URI based on a certain URI format? For example an application which generates mails want to link to another RESTful application and wants to send a hyperlin within the mail body. You talked about frameworks. What do you think about the Struts 2 REST plugin, if you had any contact with it so far (besides that you have to implement a work around to get access to HTTP Accept)? Many thanks Marcel On June 7, 2010 7:51 AM, Stefan Tilkov said: There’s a difference between the very first URI and the ones that follow. Whatever the recipe for URIs (or for building them) is, the client should discover it through the representations that are exchanged. I can’t comment on the Struts 2 REST plugin, I’ve never used it.