Anne Thomas Manes wrote: > One major distinction, here, is that you can manage multiple lightbulbs > through this one service. The service has a unique URL. You identify the > lightbulb(s) that you want to query or set as part of the content of the > message. > > If you want to make it a RESTful service (e.g., apply the REST > implementation pattern to this service), then the lightbulb identifier > should be a URL, and once you have located a service, you should be able to > GET and SET the lightbulb state using GET and PUT in addition to using the > service API.
With REST, when we have 1,000 light bulbs, we'd have 1,000 URLs which would be resolved to some kind of underlying software. We'd have some backend systems that would store and manage the meta data for these 1,000 resources. One of the issues with managing 1,000s of items is how you allow the user to pick one or some to deal with, and how you make them aware of the possible choices. One of the more interesting things for me is how service registration meta data can augment this process. I know that when I register large number of Jini services, that I augment the registration with Entry objects that contain things such as Lat/Lon, instance names, serviceUIs and other bits. In the lightbulb case, you'd probably be interested in all of the things about manufacturer, date of install etc. With the Jini service model and the Lookup Service's API, I can administrate all of this at runtime, and it can be persisted with the services other data so that when the service is restarted, all of these things are in place and consistant. What do others do to make all of the meta data managable and consistantly managed to be an integral part of the service's environment? Gregg Wonderly ------------------------ Yahoo! Groups Sponsor --------------------~--> Check out the new improvements in Yahoo! Groups email. http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> 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/
