• 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
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Strategy for supporting multiple client types?

 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi I am in the process of deciding the WAF part of the assignment. I am in a dilemma regarding what would be a good approach for the WAF design especially for supporting the two different client types(Customer and Travel Agent). Supporting a Customer should be straight forward and we can base it on Model(via Value Bean) View(JSP) Controller(Servlet). But how do we re-use these classes for supporting Rich client Travel Agents? If we plan to use HTTP Tunneling for supporting Rich client communication, then controller part and model part is fine, but what about the JSP's?? They are just wasted since the view already exists in the travel agent's application? The only thing the rich client would need is the data to populate the existing view. I think we don't need to use the view component at all for supporting Rich Clients, any thoughts on that? Front Controller for rich client can directly use the Helper class which can call the business service and access the data on the business tier via a Value Bean. This seems to be a plausible approach, but how do we represent the two different approaches? Do we have to create two different sequence diagrams(one for rich clients and the other for browser based clients) for each Use Case. In that case even the component digram needs to be created for each client type!!
Any suggestions or recommendations would be highly appreciated.
Thanks in Advance,
Ritu Chawla,
ritu_chawla@hotmail.com
 
Ritu Chawla
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Any Answers please?
 
This tiny ad is suggesting that maybe she should go play in traffic.
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic