In article <bm0bbu$165$3@sparta.btinternet.com>, Bob <none@none.none>
writes

Michael D. Ober wrote:

This doesn't answer the question about the biggest use of SETIQueue -
namely, allowing a single machine on the network to act as a proxy.

Mike.

BOINC Announcement
http://setiathome.ssl.berkeley.edu/boinc_transition_plan.html

Exactly what i was thinking - I think I'll fire off an email...

Also teh following has been added to the BOINC transistion page:
"At this point there is no "proxy" for BOINC, i.e. a mechanism for 
running the client on machines not directly connected to the Internet. 
This is more difficult with BOINC than with SETI@home Classic, but it 
may be possible."

You can see the BOINC transition announcement, specifically on the use
of SETI Queue, now, not only included the above "no-proxy facility"
announcement, but has a pointer to a URL where a download of
FreeProxyV3.5 can be obtained. 

My reading of this is FreeProxy can be considered, by the BOINC people,
to be a network proxy, as we use Queue now with S@H Classic?

Do people agree or disagree?

I have downloaded, and saved it, ready for when we move over to
BOINC/S@H 2. However, I am assuming it will complement the caching
capability given by the BOINC application.

I see we will be running a GUI S@H 2 client first, with the CLI coming
later. Back to shutting down and blanking screen savers!!

-- 
John Clark