Dennis Sosnoski wrote:
>
> So as sort of a base case we've got at least three different sets of
> resources involved in a reservation service:
>
> 1. The flight itself, which is under the control of the airline; the
> reservation information here needs to include passenger
> information (name, address, contact information, passport #, date
> of birth, etc.) as well as a reference and identifier for the
> entity that originated the reservation. The reservation may or may
> not include a specific seat, or general seat preference (e.g.,
> window).
> 2. The agency system, which needs to have the reservation associated
> with a particular customer account, and linked with the identifier
> used by the airline for the reservation.
> 3. The passenger's credit card, which needs to be debited for the
> amount of the reservation with funds transferred to the agency.
>
> How would you go about structuring this as a RESTful service?
Or more precisely, as at least three separate RESTful services - one for
the airline, one for the credit card bank, and one for the agency, with
the latter controlling the interactions with the first two.
- Dennis
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
