Bob wrote:

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.

"Brian" <tramsmash@yahoo.com> wrote in message
news:3f826d65_1@news.iprimus.com.au...

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

Brian
3.9 years, 4490 units & wondering if I make it to 5000?

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

I got a reply:-
~~~
Bob:
BOINC won't act as a proxy.
Writing a proxy for BOINC will be trickier than for SETI@home,
but if you or Ken wants to start thinking about it that would be great.
I'd be happy to help in any way; the BOINC source code is
available off the web site, which is a good place to start.

Thanks for bringing this up; I added some text to the transition page.

-- David

Bob wrote:

> Firstly apologies for further filling your undoubtedly stuffed inbox...
>
> I have just read your announcement about the transition plan for SETI@Home -> BOINC.  Folowing from this I have a question whic I believe is not answered, and will be relevant for a significant number of people:
>
> SETI Queue is an excellent program, and to many people it's primary function is NOT as a buffer, but as a proxy for a network of machines. For people running networks of computers a single point of monitoring is really useful.
>
> Will BOINC contain such functon in any way, or will someone (whether Ken, myself or someone else) have to write another app to perform this function.
>
>
> Many thanks for your time,
>
> John.