Posted by Damien Tournoud on January 16, 2010 at 12:30am
Jump to:
| Project: | API |
| Version: | master |
| Component: | Other |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
It seems that API can support multiple projects now. To use that on drupal.org, we could get the list of projects and their releases from the update XML feed, download the packages from the FTP server and parse the result.
This is how localize.drupal.org currently work, so we will have some sort of consistency, and we might be able to factor out some code (the relevant code is probably in l10n_server_drupalorg in the l10n_server module).
Here is the URL of the update XML feed: http://updates.drupal.org/release-history/project-list/all (caution: this is a big file).
Comments
#1
No, unfortunately localize.drupal.org does not use the update XML files, especially for their enourmous size. I pressed for having a list of projects available, but then it blew up in scope and it became too big to be useful. The localization server now talks to the d.o database directly via a read only user in the d.o database. Pretty bad architecture. If we can come up with something better that would be good. Basically, localize.drupal.org needs the full list of projects, but not much detail about each project (the XML feed for all projects includes **way too much** information for this). Then localize.drupal.org needs information on recent releases (since it last queries for recent releases), so there is no need to send the whole release list over the wire for all projects (which is again lots of info). If you work with the XML files for all projects, you need to continually download 7000+ XML files, parse them and look at their data to tell the new releases available. Not really workable.