--- Alexandru Popescu wrote: > On 5/27/07, Don Brown <[EMAIL PROTECTED]> wrote: >> Only you want to serve up different views of the >> action simultaneously: >> http://example.com/book/War+and+Peace.xml >> http://example.com/book/War+and+Peace.html >> http://example.com/book/War+and+Peace.json > Isn't this gonna lead to overprocessing inside the > framework?
That processing has to happen *somewhere* if you want this kind of functionality (I very much do)... If it's not in the framework then you lose the ability for trivial configuration of the behavior and must resort to a less-elegant solution. The other "easy" options for configuring this would be to have the file type as part of the path, like http://example.com/book/json/War+and+Peace or as a request parameter (which seems uglier and a poorer fit for XML or annotation configuration). For my money (or... a beer) processing via extension is a more robust, appropriate mechanism. That said, I suppose the potential overhead might be noticeable--perhaps it would be possible to wedge some of this functionality into an interceptor or...? Thanks, Dave ____________________________________________________________________________________Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
