• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

The solution to the thin client argument.

 
Anton Golovin
Ranch Hand
Posts: 527
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, guys. Recently I have been implementing a thin client solution for my assignment. However, I no longer believe it is the correct solution because it is not extensible. But I also do not believe that exposing the methods of the Data class to the client is the correct solution. In my opinion, the correct solution is to keep the data methods on the server, business methods on the server, but record-filtering methods on the client. That way the client is extensible, business logic is hidden from it, and only the filtering methods of the business layer are exposed to the client.
 
Andy Zhu
Ranch Hand
Posts: 145
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey, Anton:

in the client side, you can always do some validation for input. But it usually, IMHO, is not good to manipulate the results from the server.

But, I don't understand you why a thin client won't be extensible? May you give me an example? In this matter, I am using the same strategy.
 
Anton Golovin
Ranch Hand
Posts: 527
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Andy Zhu:
Hey, Anton:

in the client side, you can always do some validation for input. But it usually, IMHO, is not good to manipulate the results from the server.

But, I don't understand you why a thin client won't be extensible? May you give me an example? In this matter, I am using the same strategy.


The thin client works for booking, but it would not work well for deleting expired records, or unbooking booked records, unless the client can get at expired or booked rooms. So to some extent the filtering capability must rest at the client, I think.
 
Andy Zhu
Ranch Hand
Posts: 145
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey, anton:

As I see the two cases you described, they should be some operations residing on the business logic to handle these "complicated" cases, which will still result a thin client. This is so far I can think of, just like the business logic handles dirty read in booking. I am not sure if this is a kind of answer.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic