In article <7b429$42e9f2ee$82a1d3bf$25024@news1.tudelft.nl>,
Patrick Vervoorn  <patrick.vervoorn@NOSPAM.perihelion.demon.nl> wrote:

No delays in sending back results yet, and I'm running BOINC without any 
special command-line switches. But as you yourself commented in your 
email, you were running an older version, so perhaps this is something 
which was changed (fixed? :) in the newer version.

Interesting.  I've done a quick grep of the source and I see a
declaration "bool return_results_immediately", I see it being set in the
command line processing when there is a "-return_results_immediately",
but I don't see it ever being tested :-).  In the previous source it was
tested in the scheduler code.

The changelog says:

  20 May 2005
    - removed "high_priority" and "return_result_immediately" attributes
        from RESULT (no changes like this without discussion!)

I'm not sure what that means.  It looks as though that flag has gone -
but will it come back?

I'll keep an eye on it, but so far, I like it: I have a load of WU's in 
the cache, so even if the netwerk/servers at Berkeley go out again, I'm 
(hopefully) set for a few days...)

I'm also running happily with 4.43, and have returned a result.  However
I haven't had a cache-fill yet - I waiting to see how much it says it's
asking for and how much it fetches.

-- 
John F Hall