Talk:BOINC client–server technology

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by Networking task force (assessed as Mid-importance).

University of California Low‑importance

	This article is within the scope of WikiProject University of California, a collaborative effort to improve the coverage of articles relating to University of California, its history, accomplishments and other topics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.University of CaliforniaWikipedia:WikiProject University of CaliforniaTemplate:WikiProject University of CaliforniaUniversity of California
Low	This article has been rated as Low-importance on the project's importance scale.

BitTorrent

BOINC client still doesn't have a single bit of BitTorrent code on it. There is some work being done on the server side (tracker) but it's still not even half-working. Removing whole "Technological innovation" section. 201.212.126.164 18:53, 20 September 2007 (UTC)[reply]

Server workings

I added quite a bit of info about how the server works, and the daemons that make up the system. I'm not sure if it's appropriate for Wikipedia, or if it needs more work. 200.127.223.79 (talk) 17:38, 26 March 2008 (UTC)[reply]

Server weaknesses

It seems the only real weakness listed is 'does only run on unices'. In my opinion, that's hardly worth noting as a weakness, at least not in two of the four points Rkarlsba (talk) 17:02, 31 October 2011 (UTC)[reply]

Requested move 6 January 2016

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: No move. There's no agreement that the dash should be replaced. Cúchullain ^t/c 17:59, 21 January 2016 (UTC)[reply]

BOINC client–server technology → BOINC client-server technology – please remove the unicode dash from the name – James Michael DuPont (talk) 12:03, 6 January 2016 (UTC)[reply]

I contest this, I think the dash is required per MOS:DASH. I have also reverted your move BOINC client/server technology. Jenks24 (talk) 12:13, 6 January 2016 (UTC)[reply]

@Mdupont and Jenks24: This is a contested technical request (permalink). Anthony Appleyard (talk) 23:14, 6 January 2016 (UTC)[reply]

@Anthony Appleyard: Again, the ping notification function does not work when you use it like that. Jenks24 (talk) 10:30, 7 January 2016 (UTC)[reply]

Oppose – the fact that Client–server model uses a dash seems like evidence that this is the appropriate usage. (There is already a redirect at BOINC client-server technology.) —BarrelProof (talk) 01:58, 7 January 2016 (UTC)[reply]

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.

A few questions about things in "Client platforms"

It's not "Raspbian" that have very few client apps available, it's ANY LINUX RUNNING ON ARM PLATFORMS EXCEPT ANDROID (for example raspbian, armbian, ubuntu mate, etc.).

But I simply don't know how to describe it... maybe just like this will be good enough?

Operating system	Hardware	Examples	Status
Linux	ARM	Raspberry Pi	Very few client applications available

--125.36.118.173 (talk) 09:54, 3 January 2019 (UTC)[reply]