• The buffering of multiple work units is provided by the BOINC client itself - you can specify how much work your computer should get each time it contacts the server.
• Hosts that are not directly connected to the Internet, but share a LAN with one that is, can participate in BOINC using an HTTP 1.0 proxy such as Squid for Unix or FreeProxy for Windows.

Why won't SETIQueue work with BOINC?

Unlike SETI@home Classic, with its 'one size fits all' work units, BOINC allows work units that have extreme requirements (memory, disk, CPU) and makes sure they're sent only to hosts that can handle them. In BOINC, a client communicates directly with the server, telling the server about its hardware (memory size, CPU speed etc.) and the server chooses work for it accordingly. Furthermore, BOINC has separate scheduling and data servers (in SETI@home Classic, a single server played both roles).

So a BOINC proxy would have to replicate much of the functionality of the BOINC core client (so that it can download and upload files) and the BOINC scheduling server (since it would have to implement the work-distribution policy). This is possible but it would be a lot of work. "; page_tail(); ?>