Thanks eggie, I agree w/ this standpoint. I will go w/ this unless there are others that have a compelling argument against it.
-Tom On Jan 29, 7:21 am, eggie5 <[EMAIL PROTECTED]> wrote: > /user/:id would be the html profile view with all the stats etc. > /user/:id.xml|json would be simple json/xml serialization of the row > from the users table. > > I wouldn't user profile, cause there is no profile object being saved. > > Does this work? > > On Jan 28, 8:25 pm, tom hartwell <[EMAIL PROTECTED]> wrote: > > > Hey all, I'm working on a project for a friend. A pretty simple Rails > > app, but I wanted your opinions on a best practice for the following > > example. > > > A user can submit, tag, and rate postings that are made on the site. > > I would like to have a profile like page that displays to the user all > > this info: what they've submitted, what they've tagged, rated etc. > > RESTfully, there doesn't seem to be a best practice for this. Options > > that I'm considering > > > 1) user/show for :html would display all this data but user/show for > > xml would only send the appropriate? xml > > 2) user/:id/profile would do the heavy lifting, but profile would not > > have the standard actions associated w/ it. This would scope the data > > effectively at least, but would not be a RESTful controller > > 3) map.profile to a non-RESTful controller to do the heavy lifting > > > Let me know what you think, thanks in advance, > > Tom --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
