I am slightly confused about retrieving the seat information. When the customer enters the departure city,departure date,departure time,destination city,return time and return date
System responds with a list of departure flight and return Flight. When the customer selects the Departure Flight and Return Flight, I am trying to avoid another Database Call and what is the best possible way of handling this ?
I am also confused about the seat class. When the customer selects seats and if there is a layover and do we have to provide the seat information of both the flights, i mean if a person is traveelling LHR-NY-CHICAGO lhr-ny seat info is different from ny-chicago ,does the customer see both.
Let me try to help you. Please note that I only had passed in phase one.
Your first question was about the possibility of avoiding another database call. Well, When the customer selects the desired segments, I think that it is not necessary to invoke the EIS layer again. You could use a ValueListHander for that purpose.
The only moment you need to access database (inside a transaction) is when the user confirms the itinerary and wants to pay for it.
For the secont part of your question, if the flight has more than one segment I think it is necessary ask him (or her) to choose desired seat for each segment. So, the passenger must choose the seat for each leg of the flight.
Thanks a lot for your reply. I understand the point now. I have one more question. Once user confirms Itinerary, the login use case is executed ,if he is already a registered user, assuming he is registered, if the user enters his user name & password we need to show the Payment.jsp along with the Itinerary Details. Where do we retrieve these Itinerary details from ? Can we retireve from session or DB. If it is session when exactly it needs to be created.
Thanks for your help.
Joined: Nov 11, 2005
Good question !
Well, I have been working on the e-commerce business for a long time. Usually we store a cookie in the user�s browser (a GUID) which has a long expiration period. So, when he (or her) access the site we know his identity even thoug he hasn�t logged on yet. Some sites offer you to change user ("if you are not xxxx, please click here") in order to change the cookie.
So, in the very beggining we have an HTTP Session and we can store a reference to a SFSB (the "Shopping Cart"). In this SFSB we can keep the session data.
"When the customer selects the desired segments, I think that it is not necessary to invoke the EIS layer again. You could use a ValueListHander for that purpose. "
I disagree: Its a good idea to invoke the EIS layer again to get the most updated information. If you work on the ValueListHandler approach for getting seats you may land with cached information and may not be most updated one.... infact if you try it on any existing Flight booknig websites, this is the way they build it. [ August 14, 2006: Message edited by: suekar meredilko ]