Mercurial > hg > blitz_stable
comparison src/org/dancres/blitz/package.html @ 0:3dc0c5604566
Initial checkin of blitz 2.0 fcs - no installer yet.
| author | Dan Creswell <dan.creswell@gmail.com> |
|---|---|
| date | Sat, 21 Mar 2009 11:00:06 +0000 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| -1:000000000000 | 0:3dc0c5604566 |
|---|---|
| 1 <body> | |
| 2 | |
| 3 <P> This package contains the core space implementation. It is only dimly | |
| 4 aware of remoteness which is implemented in package org.dancres.blitz.remote. | |
| 5 </P> | |
| 6 | |
| 7 <p> This all got started one day after I'd been reading an article in Login | |
| 8 magazine (a publication of Usenix) - "One up on LRU" which presented a new | |
| 9 caching algorithm out of IBM research. The properties of this algorithm were, | |
| 10 I thought, well suited to the potential variations in access patterns | |
| 11 JavaSpaces implementations can encounter "in the field". How could I make this | |
| 12 work fit into a JavaSpace implementation? My solution was to adopt an | |
| 13 approach similar to that used in operating systems - virtual memory/paging. | |
| 14 Thus the code-writing began....</p> | |
| 15 | |
| 16 @see org.dancres.blitz.SpaceImpl | |
| 17 | |
| 18 </body> |