shreevat wrote:I'm sure each airline has its own. You'd have to ask them. That question has nothing to do with Java.
I was just wondering what is the psuedo logic behind airline reservation system.
All I remember is - we use set of arraylists (for seats)That's implementation details, not "pseudo-logic."
My biggest question now is - if a person requires 4 seats (preferably all adjacent seats, complexity is all 4 seats in a row is also considered to be adjacent, so as 3 in a row and once behind, so as 2 in a row, one behind, one diagonally opposite etc, so many possible combination). I don't recollect these kind of enhancements done when I designed.I doubt anybody here knows what you did either.
I am just curious to know how these systems are designed. Can someone throw your ideas on the reservation system pseudo logic please?Rather than try to get people to do your work for you under the ham-handed guise of "just curious," why not take your best shot, post your thoughts, and ask specific questions about the parts that give you trouble?
Also which technology is generally preferred for such systems (Java, PHP etc)?There is no generally preferred technology for airline reservation systems. I'm sure some use Java and some use PHP and some use C++ and some use COBOL or who knows what and all of them use a combination of technologies.