My interpretation is that he has a "User" model which is a little different than what is defined in the openSocial Person model.
Like him, we have to "convert" our "User" to a "Person", which actually involves a couple of different tables, so cost is always a concern. What I'd like to hear is a brief outline of filter/fetch optimizations Paul used to translate the "first/max/sort" to queries? Thanks, Ray On Wed, 2008-04-09 at 10:51 -0700, David Primmer wrote: > On Wed, Apr 9, 2008 at 5:08 AM, Paul Lindner <[EMAIL PROTECTED]> wrote: > > Hi, > > > > For the SocialData API stuff we integrated the various calls with our > > existing User/Friends/Activity services. We spent a bit of time > > optimizing the People fetches to only convert users that fall into the > > resultset. The trick is to convert filters into appropriate backend > > calls to reduce the data set size, and then to intelligently select only > > the actual users to convert based on first/max/sort > > Great email Paul. Could you elaborate on what 'convert' means? Are you > saying that you had some data transformation logic that you needed to > put at the right layer and you had to move it closer to the front end? > What do you mean by 'convert filters'. Are these filters in the social > APIs? > > davep > Raymond Augé Software Engineer Liferay, Inc. Enterprise. Open Source. For Life.
