> An interesting thought for future optimization... an XML-RPC catalog
> server designed for this use case could in fact do all the computation
> server-side, resolving dependencies and evaluating version constraints.
> Heck, in theory, it could cache packages' external links, and simply
> hand back to the caller a complete list of candidate URLs to choose for
> downloading.
You mean something like
select f.filename from release_files f,releases r where
f.name='setuptools' and f.name=r.name and f.version=r.version and not
r._pypi_hidden;
This gives
filename
----------------------------------
setuptools-0.6c5.win32-py2.3.exe
setuptools-0.6c5-py2.3.egg
setuptools-0.6c5.win32-py2.4.exe
setuptools-0.6c5-1.src.rpm
setuptools-0.6c5.win32-py2.5.exe
setuptools-0.6c5.tar.gz
setuptools-0.6c5-py2.5.egg
setuptools-0.6c5-py2.4.egg
That would be very easy to add to the RPC server, and
would be quite efficient also.
> That way, most activities would take only one server
> round-trip to complete, if the client sent a list of everything it
> expects to need, and the server includes everything that the server
> expects the client to want due to those things' dependencies.
>
> The main obstacle to implementing such a service today, is that it would
> have no way of knowing what dependencies to look for, without sniffing
> the contents of .egg files.
For that, I would definitely need code contributions.
Regards,
Martin
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG@python.org
http://mail.python.org/mailman/listinfo/catalog-sig
