cc'ing sipx-dev list George Niculae wrote: > --- On Tue, 1/26/10, Arjun Nair <[email protected]> wrote: > >> George Niculae wrote: >>> Hi Arjun, >>> >>> I was thinking to take http://track.sipfoundry.org/browse/XX-7365 and to >>> move >> the phonebook paging and filtering in HQLs (or indexing with >> Lucene). Not sure about your current work in thi area - do >> you have other plans with this one or should I go for it? >> Hi George, >> >> Here's what I have got on it so far (see attached patch). I >> shifted the paging + filtering to HQL. It's mostly just >> prototype code, but it looks very promising. Cuts down query >> time from 12-13secs to 100ms, on a 10K user system. You can >> take it over if you'd like. >> >> Now, I don't know if this is applicable for the current >> sprint. Last time I discussed with Paul, we were thinking of >> restricting the phonebook to a 1000 users, and switching it >> over to the non-paged api's for this release. This would >> solve a number of issues, including sort, search, etc., and >> help us in getting it to a stable state. What's your >> opinion? > > Hi Arjun, > > I think that we should give it one more chance to 4.2 and keep the non-paged > client-only datasource as an alternative in case we don't reach to a > reasonable state in time - well, this of course depends on when 4.2 is > targeted so I will need your guidance and opinions on this, guys. > > Having these said, we can make a list / prioritize phonebook issues and see > if we can come close to a resolution in time (of course have to define what > in time means in order to eliminate 4.2 risks) - I will be happy to > contribute with patches in this area. > > What do you think? >
http://track.sipfoundry.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+XX+AND+component+%3D+PhoneBook+AND+resolution+%3D+Unresolved+ORDER+BY+due+ASC%2C+priority+DESC%2C+created+ASC&mode=hide As of now there are 25 open issues (4 of them in Patch Pending), out of which I can see about 9 that we must fix. If we are going to keep the paged phonebook api in this release, then XX-7365 is a must. IMO, with a code complete target for the end of February, we should be able to do it, but it would be at the expense of the other parts of the project. So, I am not sure how much more resources we are willing to dedicate to the phonebook. Advantages of having paged api: - Support for a large number of users (>700) Disadvantages: - Search and Sort has to be implemented on the REST api side (i.e. we cannot use the default GWT one) - We need a fix for XX-7365 Arjun _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
