Michael Terrington <michael <at> terrington.id.au> writes: > > That's ok, but it could be better. It would be better by including the > > unique key in the original POSTed hierarchy. Ie. > > > > ../jobs/en/de/8fc66aca2ae1aa792ea35b8012acb6 > > > > (assuming that the original POST was to ../jobs/en/de/) > > I can't say I see that as any kind of improvement unless .../jobs/en/ > and .../jobs/en/de/ are also resources you might want to address.
Actually, I do see one way I could leverage that. There is an additional resource currently exposed that isn't in the docs. If you hit this URL : http://www.incantations.net:8080/translate/jobs/ it will give you an ATOM 1.0 feed of all the completed jobs. Then naturally jobs/en would give you all the english -> something else jobs, jobs/en/ru could give you feed of the english -> russian jobs, etc. This begs the question though, are these list resources really all that useful? Should it even be exposed? I might certainly want to lockdown those feed urls with some authentication for privacy concerns. If I do that, the only people who could view the feeds would be admins (which is only me) and I don't have much use for that information that I can think of. Somebody else might think of a good reason why, and i do plan to publish the restlet source if someone else wants to run the service on their own hardware for w/e reason. -Jason
