Talk:Client-side

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing (Rated Stub-class)
WikiProject icon 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.
Stub-Class article Stub  This article has been rated as Stub-Class on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
 
WikiProject Software / Computing  (Rated Stub-class)
WikiProject icon This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software 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.
Stub-Class article Stub  This article has been rated as Stub-Class on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computing.
 

Removed text[edit]

Removed:

Types of clients 
* Macintosh machines
* Windows machines
* Unix machines
* Linux machines

Non-comprehensive and doesn't really contribute to the reader's understanding of the concept.

Types of selections
  client-side scripting
  client-side validation
  client-side events

"Selections" isn't clear, and again, I don't think that saying that these things can happen client-side contributes to the reader's understanding of this concept or those. I put a better link to client-side scripting in the "See also" section, and consequently removed HTML scripting from it.

The server "serves" data Client-side. Servers trascieve information and data to 
the Client-side (and vice-versa).  A Client-side operation are done by the local machine, 
pending the user's selections on a client system. When resources that contains operations 
(ex. imagemap) that are to be executed locally, that resources is running "Client-Side", 
as opposed to "Server-Side". Simply, it is operations done on your computer.

It is the basis of the human and machine interface. All interationcs are handeled locally, 
rather than by the server. Client-side scripts usually run quickly because the user's machine 
doesn't have to transcieve information to the server. 

Inaddition, some users ultilize different client "browsers" [ex. Netscape, 
Internet Explorer, Mozilla, Opera].  The different combinations of client adhere to 
client-side code format (klnaone as "mark-up") that internetwork wide standards (see 
W3C). 

This explanation is more appropriate for client-server, and it's also confusing and not entirely accurate. I've tried to rewrite the important parts. Triskaideka 16:36, 22 Jul 2004 (UTC)Removed:

Types of clients 
* Macintosh machines
* Windows machines
* Unix machines
* Linux machines

Non-comprehensive and doesn't really contribute to the reader's understanding of the concept.

Types of selections
  client-side scripting
  client-side validation
  client-side events

"Selections" isn't clear, and again, I don't think that saying that these things can happen client-side contributes to the reader's understanding of this concept or those. I put a better link to client-side scripting in the "See also" section, and consequently removed HTML scripting from it.

The server "serves" data Client-side. Servers trascieve information and data to 
the Client-side (and vice-versa).  A Client-side operation are done by the local machine, 
pending the user's selections on a client system. When resources that contains operations 
(ex. imagemap) that are to be executed locally, that resources is running "Client-Side", 
as opposed to "Server-Side". Simply, it is operations done on your computer.

It is the basis of the human and machine interface. All interationcs are handeled locally, 
rather than by the server. Client-side scripts usually run quickly because the user's machine 
doesn't have to transcieve information to the server. 

Inaddition, some users ultilize different client "browsers" [ex. Netscape, 
Internet Explorer, Mozilla, Opera].  The different combinations of client adhere to 
client-side code format (klnaone as "mark-up") that internetwork wide standards (see 
W3C).   —Preceding unsigned comment added by 82.40.156.252 (talk) 14:54, 6 September 2007 (UTC) 

This explanation is more appropriate for client-server, and it's also confusing and not entirely accurate. I've tried to rewrite the important parts. Triskaideka 16:36, 22 Jul 2004 (UTC)

Merge[edit]

Sugestion: to merge Server-side and Client-side into a "web client-server description", the Web system architectures page (see web template system architectures). --Krauss (talk) 10:55, 14 June 2010 (UTC)

Change article title from adj to noun phrase[edit]

Nouns and noun phrases are preferred over adjectives for article titles, per WP:NOUN. Move to Client side? Similarly for Server-side. Nurg (talk) 23:59, 8 August 2014 (UTC)