From: Bill B. <bb...@re...> - 2010-02-22 20:36:49
|
FYI I find it easier to refactor after I've implemented a major new feature rather than during. This way, you see the whole picture and you end up with a better design in the end. Just my 2 cents. Solomon Duskis wrote: > I started down this path, and found some interesting correlations > between using InjectorFactory to inject HttpRequest information and what > we need to do to inject ClientResponse information. Things like > ContextInjector and PathParamInjector aren't really relevant on the > client side, but FormInjector, HeaderParamInjector, FormParamInjector > are. It's also interesting that @Body would be a useful thing > server-side @/Form/s as well. > > I'm going to continue down this path, but I won't check it into trunk... > I'll create a branch. > > -Solomon > > 2010/2/19 Solomon Duskis <SD...@ny... <mailto:SD...@ny...>> > > I really like this... I'll take a first stab. It will give me an > excuse to replace some client-side static methods with interfaces > and member methods. > > I don't think that you're going overboard. IMHO, your general > approach is sorely needed to move towards a hypertext constraint > compliant system, with all of the rewards it brings. > > I'll start down the path you suggested, but would like to have some > discussion on long term direction. > > Preferences: > > - I'd prefer to have a "conversation" oriented API rather than > thinking about each request individually. IMHO, the ideal REST API > should be similar to HttpUnit: > http://httpunit.sourceforge.net/doc/cookbook.html > > - I'd prefer to have a concrete class for MyResponse rather than an > interface. > > - Future: I'd prefer to have a body-based handling of links, but > that can be discussed later. > > - Future: I do see that you've used form data for sending data from > client to server :). I'd prefer to have actual <form>s to convey > the server-side requirements for communication than links alone... > but again, we can discuss that later > > -Solomon > > > > -----Original Message----- > From: Bill Burke [mailto:bb...@re... <mailto:bb...@re...>] > Sent: Thursday, February 18, 2010 8:46 PM > To: res...@li... > <mailto:res...@li...> > Subject: [Resteasy-developers] mapping responses on client side > > What do you think? > > http://bill.burkecentral.com/2010/02/19/mapping-response-on-client-side/ > > Please respond here rather than on the blog. Also, more importantly, is > anybody interested in implementing this? If so, let's spec it out more > here. > > Bill > > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Resteasy-developers mailing list > Res...@li... > <mailto:Res...@li...> > https://lists.sourceforge.net/lists/listinfo/resteasy-developers > Please consider the environment before printing this email. > > Visit our website at http://www.nyse.com > > **************************************************** > > Note: The information contained in this message and any attachment > to it is privileged, confidential and protected from disclosure. If > the reader of this message is not the intended recipient, or an > employee or agent responsible for delivering this message to the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly > prohibited. If you have received this communication in error, > please notify the sender immediately by replying to the message, and > please delete it from your system. Thank you. NYSE Euronext. > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Resteasy-developers mailing list > Res...@li... > <mailto:Res...@li...> > https://lists.sourceforge.net/lists/listinfo/resteasy-developers > > -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |