In the BOINC on JXTA document they talk about the issue of the project upload and download servers not being able to be duplicated.

How about a work queuing program aka Boinc Queue? Something along the lines of Seti Queue. Now before you all jump up and down and tell me its not feasable, I am looking for constructive discussion on the idea.

Advantages:
1. Reduced load on project up/download servers, effectively duplicating some of their function in a sense
2. Corporates could use them to do particular projects and control internet access (one reason why they don't currently use boinc)
3. Lesser machines can be used, leaving newer ones available for crunching

Disadvantages:
1. Extra program(s) for Boinc team to write/maintain
2. Potential large loss of w/u if machine dies
3. Difficult to work out amount of work to store
4. More complex to setup - ie more 'advanced' user

---

BOINC blog

If you mean something like a cache, this is already built into BOINC. If you mean like a central machine to act as a WU cache for an entire network of machines, this is already in the works. This idea is tentatively called a Super Host. It may take a while before it is put into actual use as there are larger issues at hand at the moment.

---

If you mean something like a cache, this is already built into BOINC. If you mean like a central machine to act as a WU cache for an entire network of machines, this is already in the works. This idea is tentatively called a Super Host. It may take a while before it is put into actual use as there are larger issues at hand at the moment.

Hi OzzFan,

I am aware boinc caches work units (in my case the quaddies have around 140 to 180 w/u or 3 days of additional cache).

The Super Host sounds more like what I was after, do you have some more details available?

Thanks

---

BOINC blog

The Super Host sounds more like what I was after, do you have some more details available?

Jord (Ageless) would have more information about it than me. All I know is that they're working on something that will allow a single machine to act as a cache point for an entire network, and this concept is currently being called a Super Host.

Sorry, I know no more than that.

---

As Ozzfan said, the [trac]wiki:SuperHost[/trac] is an idea at this stage, it's not implemented yet. When it will be is anyone's guess, but probably after BOINC 6 has been introduced.

---