File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes Turning a thin client into a thin-rich client with two lines of code... Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "Turning a thin client into a thin-rich client with two lines of code..." Watch "Turning a thin client into a thin-rich client with two lines of code..." New topic
Author

Turning a thin client into a thin-rich client with two lines of code...

Anton Golovin
Ranch Hand

Joined: Jul 02, 2004
Posts: 476
Hi, guys. I am currently into some thinking about the nature of the extensibility point in the instructions. It seems to me that not exposing data logic to the client makes the application simpler, but what about the business logic? Here, I think, not exposing it to the client makes the client less extensible. But at the same time, I'd like to be able to easily rob the client of this extensibility for the current purposes. What's the solution? I introduced two variables in my BusinessRules class which turn server side and client side bookability checking and exact search on and off. It's boolean variables, so they turn functionality at client off and the server on, and vice versa. Since the application in each mode has all the classes available to it, I thought I would use the BusinessRules class in both the server and the client code.

Any advice?
[ September 27, 2004: Message edited by: Anton Golovin ]

Anton Golovin (anton.golovin@gmail.com) SCJP, SCJD, SCBCD, SCWCD, OCEJWSD, SCEA/OCMJEA [JEE certs from Sun/Oracle]
 
Consider Paul's rocket mass heater.
 
subject: Turning a thin client into a thin-rich client with two lines of code...
 
Similar Threads
The solution to the thin client argument.
Do I need WeakReferences for Locking?
How to handle Data and RemoteData
N-tier architecture
Is a client that uses PL/SQL considered to be thin or fat?