sergej bogdanoff

Greenhorn
+ Follow
since Oct 19, 2005
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by sergej bogdanoff

When a flight is awarded, the specs don't tell anything about if I have to substract the mileage account with the value of the awarded flight.

Shouldn't the Frequent Flyer database be accessed in read-only mode?

Thanks.
Hi,

I wondered if I had to store data in the my SFSB Session or pass back to the client all the information that will be sent back in the next request.

e.g.:

The client selects the departure and return flight.

Should I put the selected flights in the Session and add the seats selection when he will have chosen them?

Or should I send back the flights he chose to the client?

From my point of view I would prefer keeping the info in the SFSB.

Thank you in advance for you advice.

Sergej.
Actually, Sergej is my first name. I'll add my name if you want.
Yep,

I always wondered if I should merge into one value object every entities that have a 1 to 1 dependency like Segment/Flight and Flight/Equipment.
Thanks a lot for this clarification!
I'm a bit confused with the pricing model.

To price an itin, you need to list the segments and the seats and query the database to retrieve one price for each segment/seat.

But in the requirements, we you select the flight the first time, it states that you must price the flights without having chosen the seats!

So I assume that there are 2 prices, one for the segment (flat price) and one for the seat (first and economic class.)

Does it make sense for you?

Thanks.
Sergej.
I decided to store the session state in the Application tier because I have two different clients (Web, Swing).

I have just basics problems I can't get rid of.

After having shown the flight availability to the client, the client can selects or not flights:

- Should the client send me back the selected flights and then I build the value object that represents this selection before sending it to the application tier.
- Or before sending him the flight list, I keep all of them in the application tier SFSB and I just retrieve them in next requests.

I know that keeping all the flights could consume memory but in case of if the client hasn't selected any flights, I must get all the flights with a departure/return time with +/- 1 hour and price them. In that latter case I must also keep the search values in the session.

So, I'm a bit confused if I weither or not use the Session to store flight availabilities.

Thanks in advance for your help.