Re: [REST] making list-upgrades faster

David Coallier wrote: > I think it'd be pretty easy to speed-up list-all using a REST > webservice as well but having all the results cached. This way we > could just parse an xml file. I mean, it's not very expensive to parse > an xml file of 800 packages.. list-all could perhaps retrieve the REST > result and store it on localhost, then parse the data from there. > That'd be pretty effective imho (unless one has a 56k connection of > course) > > However, I mentionned this but I have no clue currently how the pear > installer is actually retrieving this, perhaps this could be something > greg could tell us more about. > > If I see no answers by tomorow, I'll start giving a look and propose a > solution before friday. Hi, I just spent about 5 hours fixing subtle but potentially serious problems/BC breaks in another bugfix for PEAR that was related to package installation, could we please put any discussion of changes to the REST/installer infrastructure off until PEAR 1.6.0, and most definitely until after the elections are over (May 1)? I would really appreciate this, things are just too crazy right now, and I don't think I can handle (mentally) a broken installer + revamping the entire political structure of PEAR at the same time. :) Thanks, Greg