Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

question reg seats reserved.

 
Giju George
Ranch Hand
Posts: 333
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have been looking at some of the past threads about where to store the booked seat details.

As far as I understand, flight/equipment/seats are all read-only. It's only the Itinerary and segment that the customer creates. Am I going in the right direction ??

Also, I think the best place to store the seat(id) or details is in the segment. What do u guys think??
 
rottscha rotti
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Why are flight/equipment/seats readonly Where does this info come from? The old database will be replaced by a new one

rottscha rabbit
 
Giju George
Ranch Hand
Posts: 333
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by rottscha rabbit:
The old database will be replaced by a new one
rottscha rabbit


That's fine. I am saying this from a customer's point of view. When the customer searches for seat for a particular flight, it gets it from the flight/equipment/seats. The information in flight/equipment/seats are updated by, say some other process which is beyond the scope of the assignment. And once the customer gets these information (using a fast lane reader pattern for eg), it is reserved for that particular customer in his iteneray/segments (which may be implemented by entity beans). Does this makes some sense, Or am I confusing myself ??? :roll:
 
Dan Drillich
Ranch Hand
Posts: 1183
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Giju,

You explained your point here very well. It makes perfect sense - at least to me

-- Dan
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic