• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Questions about TA and Itinerary mgmt

 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
1. The idea (credit to Dave I think) about using SLSB for Search Itinerary functions makes sense while using SFSB to save Itinerary as well as Pay for Itinerary is a requirement. Using a BD and Session Facade, I think both can be handled i.e. BD->Service Locator->SFSB and BD->Service Locator-> SLSB. Any issues with this model?

2. I did not see a whole lot of detail on how the java or web application integrated with the Perl/CGI application. Any thoughts on this aspect? Would it affect the architecture in any way? Is it just a frame with mileage type interface or is there more detail in terms of using a screenscraper?

3. Do we really need to specify details on how the state is cached and restored for Part 1? For e.g. is the state such a big issue with the travel agent?

4. Did you have to consider the travel agent creating profiles for the customer i.e. I understand the travel agents could work over the phone with customers to search for itineraries. I guess they could also be creating profiles and searching to retrieve customer profiles to make changes...Thoughts?

Thanks
RR
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic