• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Travel agent front end: SWING vs WWW

 
Alexei Antipin
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It seems to me that the usual approach is to have SWING GUI for travel agents and web-based front for the rest of the world. The use case provided with the assignment is absolutely symmetrical, so does anybody consider having common front end for both purposes?

Pros - single client for both - travel agents and external users, that simplifies the architecture.

Contras - additional measurements must be taken to ensure required performance. According to the requirements response time for travel agents must be minimized, but such matters could be easily managed externally - place travel on the same LAN as the servers, limit external network bandwith etc.

Any comments?
 
Theodore Casser
Ranch Hand
Posts: 1902
Hibernate Netbeans IDE PHP
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'd considered that when I originally started with the project - it's how I would probably architect the solution if I were going to have to build it myself. The reason I decided, in the end, against that approach (basically, to have a Swing interface for the travel agents) was deciding that they were going for a solution that showed the ability to have two very different clients accessing the back end. I may not have ended up explaining myself well enough - which would explain some of my grade - but I think that's what the assignment is aiming for.
 
Lokesh Rai
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Also, doesn't Swing also provide a rich GUI, so travel agents may want to do more with their GUI than the WWW guys can..That's what swing components are for..Any thoughts?
 
Alexei Antipin
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There's no extra functionality in the specification, that means that in real life we'll not be paid for it. I still think that using SWING is a kind of overkill.
I'm thinking about noticing this option in the solution description along with notes on how it could be implemented (including additional diagrams, so the evaluator will know that I'm aware of how this works) and reasons why this approach is rejected.
 
Hitry Mitry
Ranch Hand
Posts: 32
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think the reason for considering Swing is three-fold:

1) Assignment explicitly states that the architecture must support both web applications and application clients.

2) Service-level requirements on the solutions for the travel agent and the customer-on-the-web are different

3) people who used it got good grades
 
Tony Thian
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I am considering it from the usage point of view, where web client is more for one time booking, travel agent would has to handle multiple bookings. Think in terms of security and data caching. ***The system might actually push data to travel agent*** That's why I decided to have the Java GUI Client. However I did not shown whether it is swing or awt.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic