Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Nevermind session management. The real question is: Why does the publicly accessible booking website have access to the passenger manifest of the aircraft at all?

In what possible way could knowing who the other people on the flight are benefit an individual booking a seat?

This is sloppy, sloppy coding; probably a result of some poor schmuck pulling an all nigher or two because the somebody promised an unrealistic deadline.



Agreed it's sloppy coding.

Here's my guess: it's probably because you can have multiple people on one reservation. Each passenger on the flight gets an ID, and each reservation contains the IDs of the involved parties. Invalid reservation ID? List all the passengers, obviously!


Whatever happened to returning null?


Null means "match all" -- everyone knows that!


Sadly, you're probably pretty close to the actual error there.


Well, you need a list of seats occupied by all other passengers so that you can pick yours. The names probably happened to be in the same data set (and yes, of course it's sloppy coding).


The "seat" object though is not connected to knowing "who" is in that seat, only that it is full.

As in "if seat.isoccupied()"

At no time should the passenger object be visible to perform a new booking. I see where you might need it if you are changing a reservation, but again this shouldn't in any way be linked to the passenger manifest.


Maybe they want to be able to verify, across multiple sessions, that multiple seats aren't occupied by the same person, or to potentially be able to visually indicate that someone has multiple seats.

Obviously you can easily design a schema that does that without including the names of other passengers, but that schema would be idiosyncratic to that one purpose.


Which leads to: why in the hell does your schema allow for a passenger to occupy more than one seat at a time?


It doesn't. You, for instance, accidentally book the same flight twice, or your company's travel person does.


Frequent-flyer perks.

Given a certain level with the airline, United for example blocks the seat right next to you to offer you extra space (this can be overruled if the plane gets too packed). Thus, one passenger may be linked to more than one seat.


Some people don't fit in a single seat?


Wouldn't that be better accomplished with two passengers with the same name? You aren't getting that second seat for free! :-)


What happens if the two seats aren't adjacent? :O


Then at least that passenger wouldn't be much more uncomfortable than he'd be under the present system.


My first thought was that it's not the manifest, it's the list of everyone who is currently logged into the site. That would make more sense to me.


You can also check-in on the website. It's not surprising that the app has access to passenger names.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: