Win a copy of Escape Velocity: Better Metrics for Agile Teams this week in the Agile and Other Processes forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

Common Architectures mock question?

 
Ranch Hand
Posts: 856
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Internal users of your new application are complaining that the new web front end does not perform the same as the thick client version they where using before. You are going to re-design the application to use readily available JavaScript libraries including AJAX to enhance the user experience. This will require large library downloads to the client and introduce volumes of JavaScript.


What are three drawbacks of this implementation? (Choose three.)

A. Portability to all browsers with minimal re-work for cross browser compatibility.
B. Readily available development tool kits to support automated testing, debugging, re-factoring.
C. Reduction of page refreshes to enhance user experience.
D. Simulating client state on the browser and reducing the number of views.
E. Maintainability will be decreased by removing flow from Java source to JavaScript.

I selected B,C,D.

The correct answers are-
Options A, B, E are correct.
Option C is incorrect because using AJAX and JavaScript libraries will allow you to design a client that can mock state and minimize page refresh to simulate thick clients.
Option D is incorrect because simulating the client state is a way to address the thick client.

I get it C, D are wrong answers.
B I can agree somehow, for javascript there are not that many tool kits compared to java code.

But how can you say that A,E are drawbacks of this implementation. In reality they look as advantages. Can any expert clear my confusion on this?
 
author & internet detective
Posts: 41262
849
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Where did this question come from? We ask people to post their sources.
 
Amandeep Singh
Ranch Hand
Posts: 856
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This is from Sun's Epractice.
 
Amandeep Singh
Ranch Hand
Posts: 856
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Any SCEA expert?
 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
A) Each browser(chrome , firefox , ie) might react different to javascript. Therefore, a slight rework might be needed.

E) Ajax might be acting like a controller which control the flow. Therefore you will have controller in java and javascript.
 
Amandeep Singh
Ranch Hand
Posts: 856
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks it clears me kind of. But the question and answers seem to be confusing at the first instant read.
 
Stinging nettles are edible. But I really want to see you try to eat this tiny ad:
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic