Talk:Client (computing)

AJAX
AJAX is a thin client technology? I'm a little confused by this. I'd have placed it firmly in the hybrid category. [[User:18:55, 9 April 2007 (UTC)

BAD DEFINITION
The definition paragraph (the first paragraph ) gives a bad example when it refers to dumb terminals (or even inteligent terminals) as clients. A terminal (dumb or inteligent ) is a simply an IO device. it does not run any programs itself. It does not use services running on a servor computer. Rather it is simply a device for entering and recieving data to and from a computer running a program. If such a system were called Client-Server,the term would not have to have been invented!

client
The seventh word in the definition of "client" is "negate". This word confuses me: surely, a client needs to negotiate (or obtain, or request, or connect with) a service on another network. Is the word negate a typing error?
 * "Negate" was leftovers from an Sept 11th vandalism edit. Most of that edit had been reverted but 'negate' slipt through the cracks. If you see something like that, something that really doesn't make sense and you're still unsure if it should be there, you can check the page history to see where it came from. Feel free to edit things that blatantly make no sense and you know they are wrong. —Preceding unsigned comment added by 68.211.80.47 (talk) 20:47, 14 October 2007 (UTC)

I undid the two edits of 'fat' and 'thin' to make them more readable. The previous editors had somehow enclosed them into a box and turned off word wrap, also removing the initial 'A' to start the sentences. Karanne (talk) 21:36, 19 October 2009 (UTC)

Development environments -- just plain silly.
I think the notion of development environments for client types is just plain silly. You can developer for any type of client using any type of environment. If you need examples, go for protocols (like X11 and VNC). X11 is a hybrid client procol (regardless of the fact that most people run their programs on the machines the run the X server on), VNC is a thin client protocol -- most MMO games use fat client protocols. —Preceding unsigned comment added by FrederikHertzum (talk • contribs) 13:04, 5 October 2007 (UTC)

Multimedia
Multimedia applications do not need a fat client to run - they can also run on hybrid clients in Java. Here is a reference. Stephen B Streater (talk) 20:51, 1 July 2010 (UTC)

What use is the chart?
The chart in section "Types" tells us that all three types of client have both local storage and local processing. Is a chart with all the boxes marked "Yes" really necessary? --Teemu Leisti (talk) 08:53, 29 August 2012 (UTC)

Diablo III?
In the hybrid client section, it mentions Diablo III:
 * "A device running the video game Diablo III is an example of hybrid client."

Is this mention of Diablo III necessary in this article? Diablo III seems to have to relation to a hybrid client. My assumption is this part should just say "A device running a video game is an example of a hybrid client" because it could be related to more games than Diablo. I feel that using Diablo in this example could confuse readers (it confused me, at least) as they might think Diablo is relevant to this topic.

Of course, I may be wrong because Diablo III could be one of the very few games that can be run on a hybrid client, but I highly doubt it. Should this be changed to be less specific?

JollyTurbo1 (talk) —Preceding undated comment added 05:30, 27 November 2015 (UTC)

@≤″ 119.158.172.210 (talk) 20:05, 19 January 2024 (UTC)