I would consider that a design failure.

Ideally, for a fully customized installer, there only needs to be two times the 
volunteer needs to provide input.  Once to kick off the installer and the other 
to confirm they really do want to contribute their CPU/GPU cycles to a given 
project/account manager.

Any additional interactions should be around failure cases, such as needing to 
know the proxy servers name and port number if there is a communication failure 
and the client cannot ping www.google.com.

----- Rom

-----Original Message-----
From: Tristan Olive [mailto:[email protected]] On Behalf Of Tristan 
Olive
Sent: Monday, September 28, 2015 1:31 PM
To: Rom Walton <[email protected]>
Cc: Matthew Blumberg <[email protected]>; BOINC Developers Mailing List 
<[email protected]>; Rytis Slatkevičius <[email protected]>; Hugh 
Wormington <[email protected]>
Subject: Re: [boinc_dev] Proposal: Simple Attach (Cookieless Installs)

On Mon 28 Sep 2015 01:16:35 PM EDT, Rom Walton wrote:
>
> Originally I envisioned this as something interjected between steps 1 
> and 2, when the browser window is closed, it passes the GUID to the 
> lookup account phase and proceeds based on success or failure. What 
> your proposing is to push more of the attach process into the client 
> so the attach process can move between its states without the wizard 
> being stuck displaying the bouncing ball between two computers.
>
> It would require a major overhaul of the client/manager-side attach 
> process to support.
>


What about just pausing the wizard while the browser window is opened, then 
when the user gets the "all clear" message in the browser, they can click to 
continue the wizard. No reason for the wizard itself to have to get any info 
from the browser window at all (as I'd think that would be complicated and 
prone to maintenance issues).

--
Tristan Olive

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to