Archive for the year 2010
Restfulie is almost there: first beta out
Posted on 04. Nov, 2010 by Guilherme Silveira.
Rhaiger and Ricardo Nakamura have contributed with support to formurlencoded (issue 152), now simple form posts are also supported. In parallel, through Respondie one is capable of extending and composing behavior on resource rendering. The following example shows a simple trait that renders an etag whenever the resource responds to etag: Respondie is a Rails [...]
Continue Reading
JAX-RS 2.0 – How to improve it
Posted on 18. Oct, 2010 by Guilherme Silveira.
During Javaone 2010 I was able to meet Paul Sandoz, take a deeper look into Jersey’s code, attend to a session on ideas for the the JAX-RS comittee have for the future and show some of our ideas from Vraptor 3 (server side) and Restfulie (client side). I wish JAX-RS 2 become the easiest and [...]
Continue Reading
Hypermedia and dependency injection: a lesson not to be forgotten
Posted on 01. Oct, 2010 by Guilherme Silveira.
Developers always desire to break their system into components, which typically comes with a tendency to identify those components by names. Well known unique identification is vital, one thinks With the Internet growing fast in the 21th century, distributed systems started to use URIs to identify components on the network instead of simple IDs. That [...]
Continue Reading
JavaEE 6: asynchronous contexts and Ajax push
Posted on 29. Sep, 2010 by Guilherme Silveira.
Backend developers requireing high scalability already know the no blocking IO tricks for a while: selector, poll and epoll in Linux, kqueue in MacOS and BSD, finally I/O Completion Ports in Windows. A Renato Lucindo session at QConSP touched questions and solutions that can be implemented using those ideas. Those standards and implementations are already [...]
Continue Reading
Practice: Avoid guesses, do what is expected to be done
Posted on 11. Aug, 2010 by Guilherme Silveira.
Symptom: faced with two possibilities because the client did not let his desire clear enough, one path is chosen and it is often the wrong one. After delivering a new functionality, the client is the one who is going to test, approve and use it. Because it is difficult for developers to think as their [...]
Continue Reading
Rest in C# with Restfulie
Posted on 12. Jul, 2010 by Guilherme Silveira.
Mauricio Aniche with contributions from Pedro Reys and Felipe Seixas have released the Restfulie’s C# Server 0.5 support on top of Asp.Net Mvc 2. As new versions of Restfulie come up, it becomes more clear which extension points are important and should be easy to be used, the media type and http results are two [...]
Continue Reading
Practice: Favor finishing a story over starting a new one
Posted on 11. Jul, 2010 by Guilherme Silveira.
Symptom: Right before your development cycle finishes, which can be an iteration, a sprint or anything similar, all stories are marked as finished, giving a feeling of complete success. During the review meeting, when the Product Owner verifies what has been done, the number of approvals is extremely low: most of the stories are rejected. [...]
Continue Reading
C# implementation of RESTfulie – The power of dynamic
Posted on 16. Jun, 2010 by sergiojunior.
With the grow of visibility that the Restfulie project achieved, we decided to implement a version for the .net plataform, and the C# language was chosen. To give developer’s the same “easy to use” feeling of the ruby implementation, the Restfulie C# team decided to use the new dynamic characteristcs of C# 4.0, that allows [...]
Continue Reading
How restful results are handled in Restfulie with Rails
Posted on 14. Jun, 2010 by Guilherme Silveira.
Using a backport from a Rails 3, Restfulie responders enhance your response without you even noticing. Creating First, the new 201 support with correct headers in one cute line, supported by the created responder: @item = Item.create(params[:item]) respond_with @item, :status => :created Rendering Rendering a resource using a hypermedia based representation: @item = Item.find(params[:id]) respond_with [...]
Continue Reading
http is not rest. rest is not http
Posted on 07. Jun, 2010 by guilhermesilveira.
Why? Rest is a style derived from other ones, “the REST style draws from many preexisting distributed process paradigms, communication protocols, and software fields“. Http can be used to implement a REST based system, with several limitations, and some key aspects are implemented through http, but not described within it. One example is semantics and [...]
SUBSCRIBE TO OUR RSS