This is a single archived entry from Stefan Tilkov’s blog. For more up-to-date content, check out my author page at INNOQ, which has more information about me and also contains a list of published talks, podcasts, and articles. Or you can check out the full archive.

Jersey Client API

Stefan Tilkov,

Paul Sandoz:

This API was originally being used for Jersey unit testing but i think it is applicable in the larger context of a general RESTful client API.

I find the use of the method name “proxy” slightly unfortunate — other than that, I like this very much.

On February 11, 2008 12:02 PM, Paul Sandoz said:

Hi Stefan,

I am not a great fan of proxy either, too close to CORBA perhaps :-) I fully admit to struggling to come up with something better. Resource on it’s own seems a bit overloaded in Java. ResourceReference feels too long. Perhaps ResourceRef? Do you have any suggestions?

Paul.

On February 11, 2008 12:54 PM, Stefan Tilkov said:

Yeah, criticizing is easy until you’re asked to come up with a better proposal :-) “ResourceRef” doesn’t sound too bad to me. How about HttpResource? Or maybe WebResource?

On February 11, 2008 6:19 PM, Paul Sandoz said:

I think i am sold on WebResource! There is a nice parallel with using an annotation say called @WebResourceRef for an injection target of WebResource instances.

I will hold off renaming just yet so as not to confuse others who may be looking at the API, but i will definitely make the change in the next week or two.

Thanks, Paul.