Maybe we could have a Technical Discussion Forum where people who believe they have a generic server/client problem that they have a fix for might want to mention it? E.g. duplicate "Content-type:" HTTP headers sent by the CGI script, database downtime, etc.

Or it could be announcement only (e.g. server status updates).

What do you think?

---

I'd second that idea, Michael. The structure of Questions and problems and Message boards is the same across all BOINC projects, and I imagine it would have to be a global change.

People have been asking for a server status page almost since day 1, but there's been no movement on that front. The other place for technical discussions is the phpBB forum, which has the advantage of having stickies and announcements built in and should hopefully be back up again soon (should have been back on Friday, but we're still waiting).

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Hi, Michael,

Welcome to the Boards.

That function was included in the Classic BB, which should be online again any day now. Meanwhile, there is an interim/backup forum <a href="http://cpdnforum.info/cpdn/index.php"> here. </a>

HTH.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

Hopefully no one will bash me for replying to my own question.

astroWX, thank you very much for that response, I was actually unable to access those forums because they were indeed offline. I was unaware of the backup server before now, so thank you for that reply.

Thyme Lawn, I can see how that makes sense. In that case, maybe there should be a BOINC forum? Since it is the actual BOINC client I am referring to (although project-specific board would be a good idea to add in case one particular server is acting up a bit oddly - CPDN was acting up under 4.19 when I ran it, but it was the only working version I had until I realized I could upgrade to the "unstable" 4.26 version). As for a server status page, there are many implications of that design. You could have a dynamic one that always called the script and returned (e.g.) an image, but that would have enormous performance issues. Another option is a semi-static status page that (e.g. via a cron job) updates every half hour, (a) main server (s) will contact the various project (server(s)) and cache the result, then statically serve that back to the world wide web. Of course, then you have to worry about security exploits... although IIRC server status pages should be very easy to make. Albeit they'd be lesser priority until the BOINC base is done, at least in the eyes of most programmers. (Just like how in the Windows client they sacrificed graphic frills for portability, for the time being.)

---