wsrp message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: [wsrp] On Transient Thingies - Example (1/3)
- From: Eilon Reshef <eilon.reshef@webcollage.com>
- To: wsia@lists.oasis-open.org, wsrp@lists.oasis-open.org
- Date: Tue, 04 Jun 2002 10:11:32 -0400
Title: Message
Hi
All,
Here's an
example for the need for Transient Thingies in the WSIA world, based on the
MapQuest scenario.
If a hotel
chain wants to provide a search capability on their Web site, namely allow the
user to enter a city and display the list of hotels.
And if the
hotel chain wants to display alongside with every hotel found (suppose 7 were
found) also the map of that particular hotel.
And
assuming that the size of that list is variable (could be 1 hotel found or
50).
Then it
would be quite inappropriate to use Persistent Thingies for each one of the 50
list results. (And manage them).
Rather, the
WSIA model in this case should be a single Persistent Thingy, but the Consumer
(in this case the hotel chain) can create multiple occurrences of that
Persistent Thingy, namely: multiple Transient Thingies, and provide the Nth
Transient Thingy with the appropriate location data that corresponds to the Nth
hotel - probably using property values or otherwise using out-of-band
operations.
In this
case, even though the 50 elements come from a single service, might have a
single session (it's all the same user), they would still need a
per-transient-interaction element, what we call the Transient Thingy, to
differentiate between them.
Cheers,
Eilon
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC