Example of service portability
Example of service portability
This example is adapted from the above article, in this example: Chip visits his friend Mark
- delivers user specific information (latest news, weather, etc.)
- at a user selected time
- to the user’s “alarm clock” network appliance
- But the service now has to be delivered to the correct “alarm clock”
- Either Chip takes his alarm clock with him or
- Utilizes Mark’s guest alarm clock as his alarm clock
-
REGESTER register@home.net To: [slp:/d=alarmclock, r=bedroom, u=maguire]@ua.chips.home.net From: [slp:/d=alarmclock, r=bedroom, u=maguire]@ua.chips.home.net Contact: *; expires=0
The above cancels the service to Chip’s home alarm clock
-
REGESTER register@home.net To: [slp:/d=alarmclock, r=bedroom, u=maguire]@ua.chips.home.net From: [slp:/d=alarmclock, r=bedroom, u=maguire]@ua.chips.home.net Contact: sip:[slp:/d=alarmclock, r=guest_bedroom, u=maguire]@ua.marks.home.net] Content-type: application/ddp [Device description (including address)]
Transcript
[slide508] The cool thing now is I can move it somewhere else. So if I go and visit my friend Mark, what happens? Yes, his local clock, when I register it, now becomes my alarm clock, and I get all the behaviors that I would want. This is very, very cool, once you start thinking about scaling this up, that your services really can follow you and give you the behaviors that you want.