Author: jvanzyl
Date: Wed Aug 6 22:19:12 2008
New Revision: 683508
URL: http://svn.apache.org/viewvc?rev=683508&view=rev
Log:
note about geoip and distributing the load
Modified:
maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt
Modified: maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt
URL:
http://svn.apache.org/viewvc/maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt?rev=683508&r1=683507&r2=683508&view=diff
==============================================================================
--- maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt
(original)
+++ maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt Wed
Aug 6 22:19:12 2008
@@ -92,6 +92,7 @@
** Atomic retrieval: we make sure absolutely everything is been safely
transported to disk before we place it in the local Maven repository
** Atomic deployment: in this case we could only support this using a special
filter Greg created which blocks requests for any artifacts being deploy in the
current
set until the entire set land safely to disk. So it becomes impossible to
ask for an artifact that refers to something else in the set before it is
actually available.
+** Starting thinking about a client that can understand GeoIP. Given the
recent spikes in traffic we are going to start needing to distribute the load.
* Find the best solution possible solution for dealing with version
calculations, in particular ranges. For this we called on Daniel Le Berre and
ask for some help in
integrating his SAT4J library. We learned about the SAT4J library from the
P2 project over at Eclipse.org at the last EclipseCon. SAT4J was deemed the
best way forward
