What endpoints do we support?

[IreneKnapp]

What endpoints do we support? That is, what URIs?

See http://hackage.haskell.org/trac/hackage/wiki/HackageDB/2.0/URIs for the Hackage 2 ones, and http://hackage.haskell.org/trac/hackage/wiki/HackageDB for the Hackage 1 ones.

[IreneKnapp]

The existing Hackage 1 endpoints are:

• packages/
  • 00-index.tar.gz
  • pkg-list.html
  • log
  • pkg/
  • version/
    • pkg.cabal
    • pkgid.tar.gz
    • doc/
    • html/
    • logs/
    • failure
    • success
  • latest

Note that the "front end" stuff is somewhat inside this structure - pkg-list.html is the "main page", and the docs are in each package's doc/html/ subdirectory - but somewhat not - the package "index and status" pages are generated dynamically, it appears.

I think we should actually abolish the main page in favor of an AJAXy thing. I am wary of feature creep, but it's not hard these days to have a tree that loads its parts as they're expanded, and it would save substantially on server load. I actually maintain, for some friends, a thing in Perl that has a similar front-page list, and even with caching to a static file, YES, loading that big front page is a huge hit!

[IreneKnapp]

Do we need 100% compatibility with this layout? I didn't realize drop-in hackage compatibility was a target feature. That does constrain the implementation a bit.

[cartazio]

we don't need to do drop in hackage. just something that provides an interface cabal-install can get stuff from