[racket-dev] new package system status

From: Jay McCarthy (jay.mccarthy at gmail.com)
Date: Thu Nov 21 12:04:08 EST 2013

On Thu, Nov 21, 2013 at 9:39 AM, Greg Hendershott
<greghendershott at gmail.com> wrote:
> I think the interesting point is that you could make a (mostly) static
> web service, in which GET requests have ULRs that hit a static file
> server like Amazon S3, and only the PUT/POST/PATCH requests go to some
> live server.
> What about "dynamic" GETs like search by name or tag?
> 1. One choice is, don't support search. Client has to GET the full
> catalog, or GET a list of _all_ packages with tag X, and filter
> further itself. Not entirely unreasonable when there are hundreds not
> thousands of packages.

This is basically how it works. The /index.html from S3 reads the
/pkgs-all.json which is a JSON dump of the entire database and then
renders it. If you do any "active" stuff, then you send requests to
the dynamic server. /pkgs-all.json isn't the only available file

Jay McCarthy <jay at cs.byu.edu>
Assistant Professor / Brigham Young University

"The glory of God is Intelligence" - D&C 93

Posted on the dev mailing list.