File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Whizlab Question thick client vs web browser client? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of JavaScript Promises Essentials this week in the JavaScript forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Whizlab Question thick client vs web browser client?" Watch "Whizlab Question thick client vs web browser client?" New topic
Author

Whizlab Question thick client vs web browser client?

Amandeep Singh
Ranch Hand

Joined: Jul 17, 2008
Posts: 844

Which two statements are true only when implementing rich client applications, and NOT when
implementing web browser-based clients that support only HTML? (Choose two.)
A. Information can be sent to the client by the server, without client polling.
B. Information can be encrypted prior to delivering it to the client and decrypted when received
to the client.
C. Information can be compressed prior to delivering it to the client and decompressed when
received to the client.
D. Information can be delivered to the client incrementally, without requiring that the server
deliver all the information to be presented to the client on each update.
Answer: A, D

I think none of the answer is right. As all 4 options are possible with HTML clients. Anybody can explain above answer?


SCJP 1.4, SCWCD 5, SCBCD 5, OCPJWSD 5,SCEA-1, Started Assignment Part 2
My blog- http://rkydesigns.blogspot.com
Sunderam Goplalan
Ranch Hand

Joined: Oct 10, 2011
Posts: 75
"A" is correct because in the case of browser based HTML clients (thin clients), information CANNOT be pushed without client polling i.e. without client making a GET / POST request. Usually browser based client
is PULL System, meaning clients request information from the server. In the other case of thick clients, say applets, server can PUSH data to the Rich Client based on state changes in the model. In the latter case,
applets or rich clients didn't make a request for info, but yet server data gets PUSHED. This is usually done using the technique similar to observer pattern.

model.registerObserver(view) ---- This would cause the view to be updated when the model changes internally.

I think D is correct because in the case of, say AJAX based rich clients, server can send incremental data using JSON to update just a grid in the UI upon client requests without fully reloading the page. Whereas with HTML,
the entire page may need to be reloaded


SCJP 5.0 , SCEA Java EE 5, TOGAF Certified
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Whizlab Question thick client vs web browser client?