but
doesn't change the state of the server, than GET should be used as it
allows for sane client/intermediary caching.
On Sat, Sep 12, 2009 at 12:21 PM, Schley Andrew Kutz
sak...@gmail.com wrote:
I'm faced with a dilemma. I'm trying to be a good RFC consumer and
stick with the true purpose
of that resource - and when you start
needing clients to do custom, non-standard things, you're one step
closer to the old WSDL/SOAP thing.
On Mon, Sep 14, 2009 at 9:44 AM, Schley Andrew Kutz
sak...@gmail.com wrote:
Dave,
Thank you for your input; it is much appreciated. I'm just bothered
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
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
I'm faced with a dilemma. I'm trying to be a good RFC consumer and
stick with the true purpose of GET and POST (see
http://www.cs.tut.fi/~jkorpela/forms/methods.html
for a good discussion on the history of these two HTTP verbs).
Plainly put, GET is for retrieving data and POST is for
I was hoping someone could provide me a little more insight into the
workings of the Restlet security model. I'm currently using M4 and
have created my own Authenticator filter that uses JAAS to do
authentication. I notice that there is also a class called Verifier
(which JaasVerifier appears to
~ Co-founder ~ http://www.noelios.com
-Message d'origine-
De : Schley Andrew Kutz [mailto:sak...@gmail.com]
Envoyé : jeudi 23 juillet 2009 01:07
À : discuss@restlet.tigris.org
Objet : Re: Help! -- Error handler isn't working
Jerome,
Sorry about that (updated). Here is the ViewVC
d'origine-
De : Schley Andrew Kutz [mailto:sak...@gmail.com]
Envoyé : vendredi 10 juillet 2009 20:41
À : discuss@restlet.tigris.org
Objet : Re: bug?
Jerome,
Do you know when this will make it into the Maven snapshot? Thanks!
--
-a
Ideally, a code library must be immediately usable
The StringRepresentation returned by 'public Representation handle()'
is no longer appearing in the browser when I access my server.
Here is an example:
@Override
public Representation handle()
{
if (true) return new StringRepresentation(Hello, world.);
...
That
-founder ~ http://www.noelios.com
-Message d'origine-
De : Schley Andrew Kutz [mailto:sak...@gmail.com]
Envoyé : dimanche 5 juillet 2009 15:45
À : discuss@restlet.tigris.org
Objet : Re: bug?
Great! I'm really looking forward to this and the OnError bit making
it into a release
:20 AM, Jerome Louvel wrote:
Hi Schley,
FYI, this has been fixed in SVN trunk.
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com
Schley Andrew Kutz a écrit :
I want to prevent the use
I want to prevent the use of HTTP VERB annotations in order to force
sub-classes to respond with specific class types via abstract methods
that I prototype in a base class. I marked the isAnnotated() method as
@Override and final and returned false. However, when it returns false
I get the
I have moved my application from sub-classing Restlets to sub-classing
Resources and am now relying on annotations to process incoming
requests (@Get for ex.). However, one of the nice side-effects of
processing requests with the catch-all handle method is that it allows
me to have one
I thought that the entity is what I should be looking at, thanks!
I know that they are different, but some frameworks already provide a
single call to fetch the data, and I have found it useful in the past.
--
-a
Ideally, a code library must be immediately usable by naive
developers,
14 matches
Mail list logo
