Slashdot Mirror

My primer on distriuted computing includes a shed load of tips for dealing with parasites, spoiler attacks and innocent errors.

A primer on distributed computing

My Primer on building a distributed computing project.

(It still needs updating.)

Bill, shamelessly plugging.

There are various things someone organising a distributed computation project can do to protect against parasites and spoliers.

See http://www.bacchae.co.uk/docs/dist.html , my primer on building a distributed project.

I even touch on a possible distibuted chess player.

If you could check everyone's calculations yourself, you wouldn't need distribution.

The simplest way to perform a check is no get someone else to double check. But... this wastes time, and there still a risk that the "checker" isn't also a cracked client.

For a chess player, a good thing to do would be for the client to perform a side calculation that can only be found be performed by actualy doing the work, but can be quickly checked by the supernode.

To release the cource code to your client or not is a controversial issue. I discuss both sides of the argument in my primer. (Makes cracking difficult vs greater participation)

Just go read the thing, and while you are at it, tell the slashdot editors to mention it on the front page sometime.

Bill, already submitted it once.

There are various things someone organising a distributed computation project can do to protect against parasites and spoliers.

See http://www.bacchae.co.uk/docs/dist.html , my primer on building a distributed project.

I even touch on a possible distibuted chess player.

If you could check everyone's calculations yourself, you wouldn't need distribution.

The simplest way to perform a check is no get someone else to double check. But... this wastes time, and there still a risk that the "checker" isn't also a cracked client.

For a chess player, a good thing to do would be for the client to perform a side calculation that can only be found be performed by actualy doing the work, but can be quickly checked by the supernode.

To release the cource code to your client or not is a controversial issue. I discuss both sides of the argument in my primer. (Makes cracking difficult vs greater participation)

Just go read the thing, and while you are at it, tell the slashdot editors to mention it on the front page sometime.

Bill, already submitted it once.

This one covers issues such as parasite attacks, spoiler attacks, etc.

Slashdot rejected my guide when I submitted it. Whine whine gripe gripe.

Bill, plug.