Re: GET and POST - Semantics vs. Function

Hi Andrew, It might be more useful if you could supply a more detailed example that is causing you headaches. Really the difference between POST and GET is idempotence. GET operations must be idempotent, not having side effects, while POST operations may have side effects as defined by the

RE: Re: Spring Intergation. Spring managed resources

Did this work either way, I tried following the example provided by Irfan Jamadar with Restlet 2 m04. but for some reason it is not working. Can you give a little bit more guideline of how to integrate both. Hi there, Another option is to inject those services into your parent Restlet

Re: GET and POST - Semantics vs. Function

Dave, Thank you for your input; it is much appreciated. I'm just bothered by the fact that GET and POST have a data delivery mechanism tied to them in addition to their semantic purpose of immutable and modifiable actions. It would seem to me that the method by which you send data to the

Re: Spring Integration with Restlet 2.0m4

Is there any way i can get a servlet context in existing Restlet 2 m4 build. Thanks, Rahul On Sun, Sep 13, 2009 at 2:09 PM, Rhett Sutphin rh...@detailedbalance.netwrote: Hi Rahul, There's a known bug with SpringFinder in 2.0M4. It will hopefully be fixed in the next milestone.

spring context - webapplication context in restlet 2

I wanted to get some spring injected beans in my resource file. and i have looked at the integration with spring in other ways but i would not be very interested in that as i want to keep spring separate from restlet. Also i am aware of the concern that this way my application will be tied to

Re: GET and POST - Semantics vs. Function

I see where you are coming from. Thank you for your advice. -- -a Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. --Einstein On Sep 14, 2009, at 9:41 AM, Stephen Groucutt wrote: I'm not sure I get where you're coming from exactly. It

Re: GET and POST - Semantics vs. Function

Quick pragmatic security note on this: I actually disagree with this statement. Using GET to pass login parameters is fine, and in some cases preferable (particularly as it relates to client caching). If you're concerned about security, you should encrypt such requests using SSL (you really

RE: Extracting POST parameters fails sporadically

Hi Stephen, I ran your test plan on my development machine (WinXP SP2) with Tomcat 6.0.20 without any issue. I used the latest code from SVN trunk. I had to reduce the number of concurrent threads from 5 to 4 otherwise as the load was too high (no sleep time between requests) and was

Re: GET and POST - Semantics vs. Function

I concur. -- -a Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. --Einstein On Sep 14, 2009, at 11:41 AM, Rob Heittman wrote: Quick pragmatic security note on this: I actually disagree with this statement. Using GET to pass login

REST and Authentication

Not to start a fire, but I was curious what people thought about my approach to authentication with my RESTful application. I am currently using a Restlet authenticator (was using a Servlet filter) to authenticate incoming requests. Once authenticated the request and response have a cookie

Re: Problem routing using VirtualHosts and differentiating on Port number

Hi, Thierry- Thanks for taking a look at this. I have taken your sample code, and I agree, it seems to work fine. I've been adding features to it to try to get it to fail, but haven't been able to so far. I've also been trying to disable stuff in my real app, to see if I can get it to start