Return to Question

replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/

Source Link

edited Apr 12, 2017 at 7:31

Community Bot

edited Apr 12, 2017 at 7:31

Community Bot

I'm looking for a simple definition of the concept of "client-server"

I'd like something similar to this definition of state this definition of state.

... That "thing/information" that you need to remember is called "state".

Edit - This isn't a homework question (nor am I a student). My goal is to come up with a compact way of explaining REST to average developers. I didn't want to prejudice the response though.

I'm looking for a simple definition of the concept of "client-server"

I'd like something similar to this definition of state.

... That "thing/information" that you need to remember is called "state".

Edit - This isn't a homework question (nor am I a student). My goal is to come up with a compact way of explaining REST to average developers. I didn't want to prejudice the response though.

I'm looking for a simple definition of the concept of "client-server"

I'd like something similar to this definition of state.

... That "thing/information" that you need to remember is called "state".

Edit - This isn't a homework question (nor am I a student). My goal is to come up with a compact way of explaining REST to average developers. I didn't want to prejudice the response though.

Post Closed as "exact duplicate" by gnat, Kilian Foth, Ryathal, Martijn Pieters, Walter

What are the differences between server-side and client-side programming?

occurred Feb 27, 2013 at 17:33

added 192 characters in body

Source Link

edited Feb 27, 2013 at 9:20

Rodrick Chapman

edited Feb 27, 2013 at 9:20

Rodrick Chapman

I'm looking for a simple definition of the concept of "client-server"

I'd like something similar to this definition of state.

... That "thing/information" that you need to remember is called "state".

Edit - This isn't a homework question (nor am I a student). My goal is to come up with a compact way of explaining REST to average developers. I didn't want to prejudice the response though.

I'm looking for a simple definition of the concept of "client-server"

I'd like something similar to this definition of state.

... That "thing/information" that you need to remember is called "state".

I'm looking for a simple definition of the concept of "client-server"

I'd like something similar to this definition of state.

... That "thing/information" that you need to remember is called "state".

Edit - This isn't a homework question (nor am I a student). My goal is to come up with a compact way of explaining REST to average developers. I didn't want to prejudice the response though.