| Article: |
The REST of the Web | |
| Subject: | Shouldn't you be creating new URIs? | |
| Date: | 2005-05-06 18:43:09 | |
| From: | jrbriggs | |
|
Response to: Shouldn't you be creating new URIs?
|
||
|
Absolutely. Which is exactly what I *have* done in the past when creating stricter REST web services. But for this simple example I decided not to go into that much detail -- which, on reflection, was obviously a mistake, considering your comments and others. ;-)
|
||
Showing messages 1 through 4 of 4.
-
Shouldn't you be creating new URIs?
2005-05-08 12:32:12 nferrier [View]
-
Shouldn't you be creating new URIs?
2005-05-08 18:23:57 jrbriggs [View]
Ack! You're right. But adding the python servlet as a mapping in web.xml does remove a bit of the flexibility (albeit not much) from the whole system.
I had a play with the source code of PyServlet last night, and it's relatively simple to modify so that it will look for the last reference to a ".py" file in the path and then ignore what comes after. Which would allow you to have a catchall url-pattern and not prespecify py servlets. -
Shouldn't you be creating new URIs?
2005-05-09 02:50:09 nferrier [View]
According to cool-uris-don't-change you shouldn't expose the .py anyway. URIs should be logical and not implementation dependant. -
Shouldn't you be creating new URIs?
2005-05-12 05:48:17 r.p.wilson [View]
Aren't you nitpicking? And I think you've missed the point.



Errr... no. Just make sure the servlet mapping has a pattern that looks like:
<url-pattern>/test5.py/*</url-pattern>