I am dealing with a booking engine, and I have an oddball specific request from the client.
Firstly though, there are two domains:
and
http://booking-engines.com/my-client/
There exist 4 overall steps:
- Check availability through a booking console ( specify criteria such as # of adults/kids/dates ). This lives on http://my-client.com/. It posts to http://my-client.com/search/
- Select units and post to booking engine domain. This lives on http://my-client.com/search/ and POSTs to http://booking-engines.com/my-client/guest-information/.
- The guest information page is where the user enters credit card, address, contact information and POSTs to make their reservation. This lives on http://booking-engines.com/my-client/guest-information/ and POSTs to http://booking-engines.com/my-client/book/
- If the booking is successful, user is rerouted to http://booking-engines.com/my-client/success/ where the user may print the information out and it gives the user a confirmation number, etc.
Here's the key dilemma: On http://booking-engines.com/my-client/ which only holds steps 3 and step 4, there's navigation for the first and second steps, which have to link to the original site.
I am now using sessions on separate domains - is there a way to share sessions for two different domains in a semi easy way so that information can be retained without the user having to re-enter stuff?