Hi Jasha, On 14 Oct 2011, at 21:00, Jasha Joachimsthal wrote:
> Hi, > > in order to further develop a way to rate widgets as a way to show > popularity there are a few decisions to make that will probably influence > the implementation (see https://reviews.apache.org/r/2338/): > > 1) Do we want to add the ability to rate widgets from the widget store > (non-detailed page)? > 2) Do we want to add the ability to rate widgets from the widget menu on a > user's page? > 3) Do we want to include totals of the ratings? (e.g. 314 Liked, 2014 > Disliked) > 3) How should we handle the display of the rating for the user? > a) Iterate over object model to determine user's current rating and totals - > This will result in performance issues when a lot of users have provided > ratings for widgets. > b) Create a statistics service to query the database directly and attach > this statistical information to the object model - This will result in a > hard coded SQL query to gather this information and requires attaching more > information to the web model, as well as requiring mapping the various > widget ratings to the widgets on the UI side. > c) Suggest another approach These are some of the questions that were behind the idea discussed a while ago of separating out "app store"-style functionality into a sub-project focussed just on these kinds of concerns. One approach is to use (a) and take the performance hit for the sake of simplicity and so that developers can get started with Rave 'out of the box', but then make sure we support external WidgetRepository implementations (see RAVE-249) that can handle widget-store type requests in a more scalable way as a core concern. > > > Jasha Joachimsthal > > Europe - Amsterdam - Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522 4466 > US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414 4776 (toll free) > > www.onehippo.com
