What is the best practice, vis a vis Restlet's use of URI
Templates, in handling a URI component that itself includes forward
slashes?
Reason for asking: the globally unique identifiers of data items in
Google's GData world - to which we wish to refer in a RESTful service
- are themselves
I'm sure this has come up before... Is there interest doing logging via
the Apache Commons Logging facility? It's such a standard on other
projects that it is likely already installed in most deployments of
restlet. It's a bit frustrating to have a logging facility configured
(like log4j)
Here's a test case to look at...
public class TestClass {
public static void main(String[] args) {
try {
Request request = new Request(Method.GET,
"a");
Client client = new Client(P
On 5/23/07, Adam Taft <[EMAIL PROTECTED]> wrote:
[...]
The result of a successful POST should always and only be a HTTP 201
Created status. Included with this response will be a Location header
to the newly created resource. From there, you perform a GET to the uri
specified in the location hea
Bleh, how unRESTful! ;)
The result of a successful POST should always and only be a HTTP 201
Created status. Included with this response will be a Location header
to the newly created resource. From there, you perform a GET to the uri
specified in the location header (and of course can spe
Same thing. I.e., I want the result of the POST to be given in
various output formats, too.
John
On 5/23/07, Adam Taft <[EMAIL PROTECTED]> wrote:
John D. Mitchell wrote:
> On 5/23/07, Adam Taft <[EMAIL PROTECTED]> wrote:
>> John D. Mitchell wrote:
> [...]
>> > However, I find them useful for
John D. Mitchell wrote:
On 5/23/07, Adam Taft <[EMAIL PROTECTED]> wrote:
John D. Mitchell wrote:
[...]
> However, I find them useful for optional stuff for non-GET requests,
too.
Do you have a use case for this? I'm genuinely curious.
?output={html,xhtml,json,etc.}
It's optional in the
On 5/23/07, Adam Taft <[EMAIL PROTECTED]> wrote:
John D. Mitchell wrote:
[...]
> However, I find them useful for optional stuff for non-GET requests, too.
Do you have a use case for this? I'm genuinely curious.
?output={html,xhtml,json,etc.}
It's optional in the sense that it's identifying
Thanks for the clear explanation. Yes I would like to use Application.
We are using spring and at present our servlet extends the spring
FrameworkServlet
Any other pointers for good approaches here will be much appreciated
Thanks,
Matthew
On 24/05/2007, at 2:41 AM, Thierry Boileau wrote:
John D. Mitchell wrote:
However, I find them useful for optional stuff for non-GET requests, too.
Do you have a use case for this? I'm genuinely curious.
Adam
John D. Mitchell wrote:
IIUC your need, the user ID should be in the URL proper since that's
what is used to identify the specific resource. I.e.,
/users/johnm/...
Right, that's actually a good point. It's possible that the best url
scheme for the original poster is someting like:
/users/
On 5/23/07, Adam Taft <[EMAIL PROTECTED]> wrote:
[...]
I tend to think of query string parameters as "optional" parameters, and
usually only used for GET requests.
I totally agree that they are for optional parameters.
However, I find them useful for optional stuff for non-GET requests, too.
On 5/23/07, Philip Johnson <[EMAIL PROTECTED]> wrote:
Greetings, Restletfarians,
Today I was implementing a handler for a POST method for a Users resource that
takes an email parameter such as:
testapplication/[EMAIL PROTECTED]
I handled this using a router and a URI pattern, as follows:
Hi Philip,
Glups, I get as nervous as you... I think it's not possible, I will
enter an issue for that.
However, I may add something in order to help you. Is the "timezone"
query parameter part of the resource identification?
If not, you can remove it from the routing process (just keep
"testa
I tend to think of query string parameters as "optional" parameters, and
usually only used for GET requests.
For example, in a search for resources (returns a list of objects).
Maybe my default url looks like this:
/app/users/
I've defined this to return the newest 50 users of the system.
Adam Taft adamtaft.com> writes:
> Is there a particular reason why you are using query string parameters
> for your post attributes?
Hmm, I guess there's two issues here:
(1) Is my example appropriate according to REST architectural principles?
(2) How do you do order-independent multiple pa
Is there a particular reason why you are using query string parameters
for your post attributes?
Traditionally, when you POST a resource (in your case, a user) to a
server, you use the message body to store the data. For example, when a
web browser posts a form to a web server, it encodes t
Greetings, Restletfarians,
Today I was implementing a handler for a POST method for a Users resource that
takes an email parameter such as:
testapplication/[EMAIL PROTECTED]
I handled this using a router and a URI pattern, as follows:
router.attach("/users?email={email}", UsersResource.clas
Hi Chuck,
you can find the current binary at this URL:
http://www.restlet.org/downloads/1.1/current.zip
best regards,
Thierry Boileau
I'm going to need this in a day or two. Can I get this in a binary, or
do I have to build from trunk?
--Chuck
-Original Message-
From: Toby Thain [m
I'm going to need this in a day or two. Can I get this in a binary, or
do I have to build from trunk?
--Chuck
-Original Message-
From: Toby Thain [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 22, 2007 6:19 PM
To: discuss@restlet.tigris.org
Subject: Re: 2-way SSL authentication
On 21-M
Hi Matthew,
The TunnelFilter worls correctly only in the context of a Restlet
application. We kindly encourage you to use application wich provides
some built-in services such as filtering.
However, if you don't want to be in such case, you can create your own
filter with the code of the "befo
On 17 May 2007, at 15:23, Jim Alateras wrote:
Jerome, I am getting deadlocks when sharing the Client across
multiple requests. Haven't had time to resolve but it seems like a
look in commons-httpclient. I had to revert back to instantiating a
new instance of Client per request.
I experie
Thanks for all that. It doesn't seem to work using the
ServletConverter though. I can't work out how I am supposed to hook
it up, my servlet init code looks pretty much like this:
// create the converter
this.converter = new ServletConverter(getServletContext()
Hello Matthew,
I suppose you think about this issue [1] and this discussion [2].
So, these web pages [3], [4] wait for you!
>Also does this work with the ServletConverter style of Restlet ?
It should, I think, because this had been implemented at the application
level, in the TunnelFilter class
24 matches
Mail list logo
