If this is HTML based then a css print profile could be an alternative Jon
William Pietri wrote: > Rob Heittman wrote: >> I find that I've had a hard time implementing complete template-based, >> page-based UIs entirely on the server without making a mess. I think >> this is because I'm just conflating too many UI concerns in one layer. > > I've had that feeling recently, too. > > Would people be willing to share examples of how they've done this > with Restlet? For example, the other day we needed to create a print > view of one of our entities. Sticking with the user example, these > options occurred to us, in rough order of preference: > > 1. /user/1/print > 2. /user/1?view=print > 3. /user/print/1 > 4. /print/user/1 > 5. /user/1 (with a custom media type in the Accept header) > 6. /user/1 (with a POST that requests the print view) > > > The last 4 all strike me as various flavors of wrong. I'm ok with the > first two, but neither seems great to me, in that the URLs suggest > different resources, while we think of the print view as a different > representation of the same resource. > > Since none of the folks on my team feel like we fully get what a > RESTful web app looks like, I'd love to hear how more experienced > people do it. > > William ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2363990
