buzzwords: client side vs. server side,
Talking to a head hunter today about my work experience, and they ask whether my experience is front end, back end, or both. Thought is was a rather rude personal question at first, then realized they probably meant client side vs. server side.
Still, I've never really understood WTF those buzzwords really mean.
They sound really cool when you say them, but the only true definition I can fathom comes mainly from internet applications. The server side stuff is anything running on the web server, like Appache or IIS and any related databases on that machine mySQL, SQL Server, etc... The client side stuff is the web browser on my PC which is interacting with the server, sending it button clicks, links etc... and the server side processes that and sends back a stream of html for my browser to throw up on the screen. One other possibility, in addition to web server, would be database server, same concept almost (client programs would be any standalone application that connects to the db and sends it sql commands, server side programming would be actually modifying the database code? Who the heck ever does that except a very few Oracle or Microsoft employees?)
So what the heck is client side C++ vs. server side C++ ?? I don't think C++ has 2 standards, one for client side and one for server side? If my browser uses an add-in written in C++, how is that code going to differ from the C++ used in an Appache module which is processing an incoming command and making a call to mySQL?
And isn't the client (Internet Explorer on my PC) actually a server if the human being sitting at the PC is called a client. The web browser is then servicing requests from the human using the browser, human = client and browser = server. It's all a matter of perspective isn't it?
I've head several headhunters and an occasional programmer throw around this client side vs. server side (or front end vs. back end) buzzword so was just wondering what anybody else's take was on it. Seems to me it sounds really cool to say but doesn't mean much. I would imagine 99% of the stuff out there people are working on is client side. How many people actually modify IIS, or Appache, or work for Godaddy.com, or actually change the schemas used by SQL Server? That would be server side programming I think?
Still, I've never really understood WTF those buzzwords really mean.
They sound really cool when you say them, but the only true definition I can fathom comes mainly from internet applications. The server side stuff is anything running on the web server, like Appache or IIS and any related databases on that machine mySQL, SQL Server, etc... The client side stuff is the web browser on my PC which is interacting with the server, sending it button clicks, links etc... and the server side processes that and sends back a stream of html for my browser to throw up on the screen. One other possibility, in addition to web server, would be database server, same concept almost (client programs would be any standalone application that connects to the db and sends it sql commands, server side programming would be actually modifying the database code? Who the heck ever does that except a very few Oracle or Microsoft employees?)
So what the heck is client side C++ vs. server side C++ ?? I don't think C++ has 2 standards, one for client side and one for server side? If my browser uses an add-in written in C++, how is that code going to differ from the C++ used in an Appache module which is processing an incoming command and making a call to mySQL?
And isn't the client (Internet Explorer on my PC) actually a server if the human being sitting at the PC is called a client. The web browser is then servicing requests from the human using the browser, human = client and browser = server. It's all a matter of perspective isn't it?
I've head several headhunters and an occasional programmer throw around this client side vs. server side (or front end vs. back end) buzzword so was just wondering what anybody else's take was on it. Seems to me it sounds really cool to say but doesn't mean much. I would imagine 99% of the stuff out there people are working on is client side. How many people actually modify IIS, or Appache, or work for Godaddy.com, or actually change the schemas used by SQL Server? That would be server side programming I think?
Client-side typically means GUI programming experience. Server-side experience could mean writing network server applications, or it could just mean batch systems. It's all a matter of the technologies you are familiar with and the requirements you are used to dealing with (HCI vs. raw computational efficiency).
Topic archived. No new replies allowed.