dev@jersey.java.net

URI Best Practice?

From: Adam Retter <adam.retter_at_googlemail.com>
Date: Tue, 29 Dec 2009 16:40:25 +0000

Hi there folks, I am very new to using Jersey and I just wanted to get
some feedback on the URI's I am using and whether I am following best
practice or if people have any suggestions for improvement?

The main resource that we are interested in is called a "Lodgement".
Lodgements are an XML document with an embedded PDF (base64).
Lodgements are always referenced by a key. For our site some access
has to be public and some has to be secure (client certificates). The
following two URI's I am using as my roots for my REST services -

Public - http://www.company.com/rest/

Client Certificates - https://www.company.com/rest/secure/


We have the need for two services currently -

1) A service for the public to retrieve the PDF aspect of a Lodgement,
for which I have used the following URI scheme -

http://www.company.com/rest/lodgement/{key}/pdf


2) A service for authenticated users to retrieve the entire Lodgement,
for which I have used the following URI scheme -

https://www.compay.com/rest/secure/lodgement/{key}


Does my approach meet the known best practices of RESTful URI's or
could it be improved in someway?


Thanks Adam.

-- 
Adam Retter
skype :adam.retter
http://www.adamretter.org.uk