hey there, there's already been a few informal mentions of this idea going back to before s.d.o was up and available, i figure now is as good of a time as any to try and get something a bit more concrete from it. here's a semi-coherent brain dump i threw together earlier this morning. at the end is a very proposal in very broad strokes regarding how i could see p-t.d.o mooching some yummy stuff from s.d.o. if it sounds reasonable i can follow up with something more specific, otherwise i'd be interested to hear what you have to say about it. okay, with no further ado... currently, with p-t.d.o: - hosted on respighi - based on a local partial mirror, currently only single repository supported - storage is not persistant (i.e. links disappear, i think it should already be pretty obvious why s.d.o + p-t.d.o could be friends here. - relies on uniqueness of srcpkg/version source packages - all files are locally available to the web service - some caching is done, though may be turned off - much of the code is loose wrappers around various diff/filterdiff/diffstat utilities to the local files currently, with s.d.o: - multiple archives supported - possibly breaks p-t srcpkg/version idiom - means p-t will have to become broad-minded - is it unique if we make it a triplet with repo? - if not, examples? - files stored on large fs, different host than p-t - pg backend for mapping data questions aobut using snapshot as backend where makes the most sense to interface to it? db level? - code/schema/modelling duplication - requires pg connection ability - doesn't solve file transfer issues web/api level? - makes querying simpler than talking to the db - could bundle file transfer into requests though it probably wouldn't work well for larger pkgs - burden would be shifted to snapshot (but would probably make re-use of existing code) - would be potentially less flexible from p-t perspective. rough proposal: after having thought about this for a bit, this is the idea i currently have bouncing around in my head. * p-t/respighi gets local r/o nfs mount of pt fs (istr weasel saying this could be possible long ago) * s.d.o provides simple ReST-ful web api - responses json encoded in an agreed manner - api is versioned for easy transition later if needed - implements Last-Modified etc for local caching * basic api needs: - search for packages matching name - versions available for package - mapping from unique identifier to location of srcpkg * extra/maybe stuff: - search on maintainer name/address - cool web 2.0 stuff (jQuery-ish searchbar) - ??? * tbd: - does p-t move entirely to snapshot as backend or use it for extra info? i.e. do we still keep local repo's and add-on to it from snapshot? --
Attachment:
signature.asc
Description: Digital signature