<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Restlet, a REST framework for Java</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Sun, 19 May 2013 03:28:52 -0400</pubDate>


    <item>

        <title>Is REST performance worth the hassle of a learning new API?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[Version 0.19 beta has just been released. <br><a href="http://www.restlet.org" target="_blank">http://www.restlet.org</a><br><br>Changes include a sample application detailling the source code of the Restlet and Noelios Consulting Web sites and a new...]]></description>
        

        <pubDate>Tue, 10 Jan 2006 15:51:37 -0500</pubDate>

        

        <jf:creationDate>Tue, 10 Jan 2006 15:51:37 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 10 Jan 2006 15:51:37 -0500</jf:modificationDate>
        <jf:date>Jan 10, 2006</jf:date>
        <jf:author>Jerome Louvel</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>HTTP Sessions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[Eelco,<br><blockquote>Why not just call it the old fashioned way: from object orientation to procedural programming.</blockquote><br>REST-style and what I designated as resource-oriented design means so much more than old procedural programming. First,...]]></description>
        

        <pubDate>Mon, 09 Jan 2006 11:30:55 -0500</pubDate>

        

        <jf:creationDate>Mon, 09 Jan 2006 11:30:55 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 09 Jan 2006 11:30:55 -0500</jf:modificationDate>
        <jf:date>Jan 9, 2006</jf:date>
        <jf:author>Jerome Louvel</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>HTTP Sessions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[<blockquote>I think that designing applications according to the REST style requires a kind of paradigm shift, from object-oriented modeling to resource-oriented modeling if you like.</blockquote><br>Why not just call it the old fashioned way: from...]]></description>
        

        <pubDate>Sun, 08 Jan 2006 05:46:14 -0500</pubDate>

        

        <jf:creationDate>Sun, 08 Jan 2006 05:46:14 -0500</jf:creationDate>
        <jf:modificationDate>Sun, 08 Jan 2006 05:46:14 -0500</jf:modificationDate>
        <jf:date>Jan 8, 2006</jf:date>
        <jf:author>Eelco Hillenius</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>HTTP Sessions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[Apparently the Spring guys are already working on better REST remoting support. I hope that they come up with a nice workable solution (most times they do ;-)) and don't drop this issue. <br><br>Take a look at this <br><a...]]></description>
        

        <pubDate>Thu, 05 Jan 2006 13:39:52 -0500</pubDate>

        

        <jf:creationDate>Thu, 05 Jan 2006 13:39:52 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 05 Jan 2006 13:39:52 -0500</jf:modificationDate>
        <jf:date>Jan 5, 2006</jf:date>
        <jf:author>Michael Mayr</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>HTTP Sessions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[<blockquote>Concerning, the abstraction level I don't think Restlets are at a lower level than Servlets. If you consider not just the Restlet API but also the components shipping with the Restlet Engine (DirectoryRestlet and TemplateRepresentation based...]]></description>
        

        <pubDate>Thu, 05 Jan 2006 13:23:59 -0500</pubDate>

        

        <jf:creationDate>Thu, 05 Jan 2006 13:23:59 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 05 Jan 2006 13:23:59 -0500</jf:modificationDate>
        <jf:date>Jan 5, 2006</jf:date>
        <jf:author>Michael Mayr</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>HTTP Sessions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[I think that designing applications according to the REST style requires a kind of paradigm shift, from object-oriented modeling to resource-oriented modeling if you like. <br><br>For some guidance on REST and sessions in particular, I recommand this...]]></description>
        

        <pubDate>Thu, 05 Jan 2006 11:32:56 -0500</pubDate>

        

        <jf:creationDate>Thu, 05 Jan 2006 11:32:56 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 05 Jan 2006 11:32:56 -0500</jf:modificationDate>
        <jf:date>Jan 5, 2006</jf:date>
        <jf:author>Jerome Louvel</jf:author>
        <jf:replyCount>4</jf:replyCount>
    </item>


    <item>

        <title>Configuration</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[Hi Kit,<br><br>Current there is no XML configuration available but this is definitely a feature that I want to add later. See the following issue: <a href="http://restlet.tigris.org/issues/show_bug.cgi?id=9"...]]></description>
        

        <pubDate>Thu, 05 Jan 2006 09:55:22 -0500</pubDate>

        

        <jf:creationDate>Thu, 05 Jan 2006 09:55:22 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 05 Jan 2006 09:55:22 -0500</jf:modificationDate>
        <jf:date>Jan 5, 2006</jf:date>
        <jf:author>Jerome Louvel</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>HTTP Sessions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[Hi Joe,<br><blockquote>Does the HTTP Session concept violate the statelessness of REST?</blockquote><br>The way I see it: Yes it does, because one central guideline of REST is statelessness and because of that REST systems can be scaled easier than...]]></description>
        

        <pubDate>Thu, 05 Jan 2006 09:10:29 -0500</pubDate>

        

        <jf:creationDate>Thu, 05 Jan 2006 09:10:29 -0500</jf:creationDate>
        <jf:modificationDate>Thu, 05 Jan 2006 09:10:29 -0500</jf:modificationDate>
        <jf:date>Jan 5, 2006</jf:date>
        <jf:author>Michael Mayr</jf:author>
        <jf:replyCount>5</jf:replyCount>
    </item>


    <item>

        <title>HTTP Sessions</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[I'd like to hear some opinions.  Does the HTTP Session concept violate the statelessness of REST?  <br><br>I didn't notice anything session-related in the API, which is justifiable, but I think that support for sessions within the REST API (or an API...]]></description>
        

        <pubDate>Wed, 04 Jan 2006 16:34:56 -0500</pubDate>

        

        <jf:creationDate>Wed, 04 Jan 2006 16:34:56 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 04 Jan 2006 16:34:56 -0500</jf:modificationDate>
        <jf:date>Jan 4, 2006</jf:date>
        <jf:author>Joe Wolf</jf:author>
        <jf:replyCount>6</jf:replyCount>
    </item>


    <item>

        <title>The future ...</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[EJB died because of (its complexity and its price and) Hibernate and Spring.<br>Servlet died because of REST and AJAX :)<br><br>Conclusion:<br>Opensource kills!]]></description>
        

        <pubDate>Wed, 04 Jan 2006 05:16:18 -0500</pubDate>

        

        <jf:creationDate>Wed, 04 Jan 2006 05:16:18 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 04 Jan 2006 05:16:18 -0500</jf:modificationDate>
        <jf:date>Jan 4, 2006</jf:date>
        <jf:author>Olivier Rossel</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Configuration</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[Looking through the tutorial, this looks very nice. I notice that all configuration is done programmatically. Is it possible to configure a restlet server by xml file? Or using Spring?<br><br>Regards<br>Kit]]></description>
        

        <pubDate>Wed, 04 Jan 2006 04:46:32 -0500</pubDate>

        

        <jf:creationDate>Wed, 04 Jan 2006 04:46:32 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 04 Jan 2006 04:46:32 -0500</jf:modificationDate>
        <jf:date>Jan 4, 2006</jf:date>
        <jf:author>Kit Davies</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Is REST performance worth the hassle of a learning new API?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[Michael,<br><br>Thanks for the feed-back. I used a larger definition of performance which includes both scalability and throughput but I'll try to be more precise in the future.<br><br>I agree with your remark on optimization. My current priority is not...]]></description>
        

        <pubDate>Tue, 03 Jan 2006 16:15:42 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Jan 2006 16:15:42 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Jan 2006 16:15:42 -0500</jf:modificationDate>
        <jf:date>Jan 3, 2006</jf:date>
        <jf:author>Jerome Louvel</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>REST/SOAP Pet Store comparison needed</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[Thanks for the compliments! I do hope that Restlets will provide a more practical approach to REST ideas. <br><br>I think that the Pet Store project suggestion is great and would be happy to provide support to anyone willing to perform a complete and...]]></description>
        

        <pubDate>Tue, 03 Jan 2006 16:04:42 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Jan 2006 16:04:42 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Jan 2006 16:04:42 -0500</jf:modificationDate>
        <jf:date>Jan 3, 2006</jf:date>
        <jf:author>Jerome Louvel</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Is REST performance worth the hassle of a learning new API?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[Grizzly, like Jetty 6, have NIO listeners that attempt to improve the performance. Basically, they use NIO to prevent the allocation of one thread per socket necessary with BIO. Then, as the Servlet API is based on the blocking BIO, they need to convert...]]></description>
        

        <pubDate>Tue, 03 Jan 2006 15:21:12 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Jan 2006 15:21:12 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Jan 2006 15:21:12 -0500</jf:modificationDate>
        <jf:date>Jan 3, 2006</jf:date>
        <jf:author>Jerome Louvel</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Is REST performance worth the hassle of a learning new API?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=38290</link>

        

        
            <description><![CDATA[Nice work from skimming over it. But I have a few remarks:<br><br>Please don't confuse performance with scalability. Scalability is a metric of a software system that basically says how good a system can support a growing number of clients by increasing...]]></description>
        

        <pubDate>Tue, 03 Jan 2006 15:15:41 -0500</pubDate>

        

        <jf:creationDate>Tue, 03 Jan 2006 15:15:41 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 03 Jan 2006 15:15:41 -0500</jf:modificationDate>
        <jf:date>Jan 3, 2006</jf:date>
        <jf:author>Michael Mayr</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>



</channel>
</rss>

