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. JulesH 18:55, 9 April 2007 (UTC)[reply]

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)[reply]

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)[reply]